question about scanning in 3.5 GHz

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 ?


[Index of Archives]     [Linux Kernel]     [Linux Wireless]     [Linux Bluetooth]     [Linux Netdev]     [Linux Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux