Blocking unresponsive APs

steve70638 · 04-25-2002

I am running MiniStumbler on my IPAQ 3870 just fine with one exception. In a certain area of town there are a number (5 or 6)of non-WEP enabled APs shown as available on Ministumbler (MS). The problem is that the one with the strongest signal and the one that MS grabs hold of has a weirdness associated with it that doesn't allow me to jump on to its particular network.

The weirdness is this: When my IPAQ does its DHCP request it gets back a normal looking IP, normal looking subnet and a normal looking DNS. The problem is that it gets back a gateway IP address of 0.0.0.0. Needless to say, I can't ping out through a gateway of 0.0.0.0. I figure that they have some funky DHCP thing going on that requires that manual setting of the gateway in order to access the AP. So, I guess that means they don't want any random Stumblers like my jumping on their network and that they give legit users of the network the gateway IP address for them to manually put into their stack.

The problem is that even though there are other AP's available, I can't find anyway to have MS block the AP with the weird gateway and try a different one.

My question is this: Is there any way to have MS skip over this offending AP or have my device specify a specific AP to try? Or, is there something that I don't understand in the way MS works that makes this an unreasonable request?

Thanks!
Steve

04-25-2002	#1 (permalink)
steve70638 Registered Member Join Date: Apr 2002 Posts: 3	Blocking unresponsive APs I am running MiniStumbler on my IPAQ 3870 just fine with one exception. In a certain area of town there are a number (5 or 6)of non-WEP enabled APs shown as available on Ministumbler (MS). The problem is that the one with the strongest signal and the one that MS grabs hold of has a weirdness associated with it that doesn't allow me to jump on to its particular network. The weirdness is this: When my IPAQ does its DHCP request it gets back a normal looking IP, normal looking subnet and a normal looking DNS. The problem is that it gets back a gateway IP address of 0.0.0.0. Needless to say, I can't ping out through a gateway of 0.0.0.0. I figure that they have some funky DHCP thing going on that requires that manual setting of the gateway in order to access the AP. So, I guess that means they don't want any random Stumblers like my jumping on their network and that they give legit users of the network the gateway IP address for them to manually put into their stack. The problem is that even though there are other AP's available, I can't find anyway to have MS block the AP with the weird gateway and try a different one. My question is this: Is there any way to have MS skip over this offending AP or have my device specify a specific AP to try? Or, is there something that I don't understand in the way MS works that makes this an unreasonable request? Thanks! Steve

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode