can associate with master, but cannot ping or anything else

Frederik Dannemare admin at sentinel.dk
Sat Jan 17 16:49:29 EST 2004


Gunter Burchardt wrote:
> Hello,
> i think your wlan0 interface has no ip-adress

Both the interface on the master and the managed node were set up correctly. 
It turns out enabling WEP was the source of the problem, but I have yet to 
figure out why. Non-WEP works without any problems, I just discovered. Stupid 
me for not trying non-WEP first.

> try: ifconfig wlan0 192.168.1.1 broadcast 192.168.1.255 netmask 255.255.255.0
> 
> why you use the hostroute 
> 192.168.1.2 192.168.1.1 255.255.255.255 UGH 0 0 0 wlan0 

Well, it works (but I'm no routing expert, that's for sure), and I thought 
that was the correct way to set up a static route from 192.168.1.1 to 192.168.1.2.

> a better routing entry is
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0

I don't see why this is more correct, since it then points to defgw (0.0.0.0) 
which is currently meant for my external (eth0) interface, right?. My routing 
table would then look like this:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
62.107.64.0     0.0.0.0         255.255.224.0   U     0      0        0 eth0
0.0.0.0         62.107.95.254   0.0.0.0         UG    0      0        0 eth0

But will this not potentially confuse the routing? I mean, it works (just 
tested it), but if I initiate a request to 192.168.1.2, it will be routed to 
62.107.95.254, right? But why does it actually work then? I'm a bit confused :)

Any further feedback appreciated.
--
Frederik Dannemare




More information about the HostAP mailing list