Wireless Woes

onebuck · 10-05-2008, 11:08 PM

Hi,

If you are going to use the 'wlan0' device then your kernel route table is not correct. As root from the cli;

Code:

~#route del default gw eth0 192.168.1.1
~#route add default gw wlan0 192.168.1.1
~# route -n
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
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    1      0        0 wlan0

The route table should look like the sample above. Now try an ping as I suggested before.

forum1793 · 10-06-2008, 07:38 PM

I've not used static IP with wireless before. Probably not issue but maybe the assigning of the IP in dhcp verifies or enables connection?

I've successfully hooked up wireless cards on two machines when eth was also hooked up and I verified by unplugging the eth. The link you provided only says have wireless and wired is cumbersome.

Have you verified router? I seem to remember that some allow for setting IP range of wireless connections. Is it possible you are out of that range?

Most likely issue is encryption. What is your router using? Putting info in rc.inet1.conf is sufficient for wep I think but people have had issues with wpa_supplicant for wpa2. I don't use public wireless and so I've never needed rc.wireless.conf. I delete or rename this such that it is not there.

Depending on what your doing you could always try rworkmans wicd. It's worked well for me.