Leonardo, ? I may be mistaken, but I believe the Intel cards only work in the 2.5GHz range. -Brandon ________________________________ From: Leonardo Antoniazzi <acerone at infinito.it> To: wimax at linuxwimax.org Sent: Tue, May 25, 2010 5:53:05 AM Subject: question about scanning in 3.5 GHz Hello I have tried this: - removed any entry between the <Operator> tags and between the <WideScanParameters> tags in the default /var/lib/wimax/WimaxDB.bin file. - added the follow entry in the <WideScanParameters> field: <ChannelPlan> ? ? <Entries> ? ? ? ? <x0> ? ? ? ? ? ? <Id>AB</Id> ? ? ? ? ? ? ? ? <FirstFreq>3437000</FirstFreq> ? ? ? ? ? ? ? ? <LastFreq>3600000</LastFreq> ? ? ? ? ? ? ? ? <NextFreqStep>500</NextFreqStep> ? ? ? ? ? ? ? ? <Preambles>ffffffffffffffffffffffffffffff</Preambles> ? ? ? ? ? ? ? ? <BW>10000</BW> ? ? ? ? ? ? ? ? <FFTSize>1024</FFTSize> ? ? ? ? ? ? ? ? <DuplexMode>1</DuplexMode> ? ? ? ? ? ? ? ? <TTL>0</TTL> ? ? ? </x0> ? </Entries> ? ? ? ? ? ? ? ? <BW>-1</BW> ? ? ? ? ? ? ? ? <FFTSize>-1</FFTSize> ? ? ? ? ? ? ? ? <DuplexMode>-1</DuplexMode> </ChannelPlan> - enabled any trace message by setting: ? ? <Modules>4294967295</Modules> ? ? <Severities>255</Severities> ? ? <DumpEnable>1</DumpEnable> in /etc/wimax/config.xml the wide scan took about 5 minutes, but no trace of discovery naps in the wimaxd.log file I should be able to detect a nap with these settings ? _______________________________________________ wimax mailing list wimax at linuxwimax.org http://lists.linuxwimax.org/listinfo/wimax -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxwimax.org/pipermail/wimax/attachments/20100525/a287aa77/attachment.html>
