Channelvelocity thoughts
Posted: Sun Apr 23, 2006 9:09 am
I've been rereading this thread on a more efficient Kismet channel hopping idea and was wondering/considering in light of that thread what's the best velocity setting to use and why. The default is 5 channels per second. I use 7 with a sourcechannel scheme of 6,6,1,1,11,3,4,6,11,10,6,1,5,7,11,6,1,8,6,11,9,6,2,6,6. I've played with the velocity number but have not been able to see much difference in results whereas changing to the custom sourcechannel does make a difference in my area. Just wondering what velocity setting you use and if you have strong feelings about that setting.
I'm using a 1 watt pre amp so I'm usually able to see the signal for a longer period of time and therefore have increased the velocity setting based on that. CPU is 1.7 GHz and card is Senao 2511-CD PLUS EXT2 with a 5.5 dB omni.
PS, I've been running Netstumbler side by side with Kismet and it's interesting to see that Netstumbler still finds stuff that Kismet doesn't have time to get. I know multiple cards, etc would help but I'm trying to optimize what I have. Netstumbler finds from 2 to 18 additional networks that Kismet missed per 2 hour run so it's not a huge number. That's with Kismet finding 2,500 to Netstumbler's 900 networks on that same run.
I'm using a 1 watt pre amp so I'm usually able to see the signal for a longer period of time and therefore have increased the velocity setting based on that. CPU is 1.7 GHz and card is Senao 2511-CD PLUS EXT2 with a 5.5 dB omni.
PS, I've been running Netstumbler side by side with Kismet and it's interesting to see that Netstumbler still finds stuff that Kismet doesn't have time to get. I know multiple cards, etc would help but I'm trying to optimize what I have. Netstumbler finds from 2 to 18 additional networks that Kismet missed per 2 hour run so it's not a huge number. That's with Kismet finding 2,500 to Netstumbler's 900 networks on that same run.