Re: Linksys WMP55AG gets IP address but no DNS

Thomas Hedden <thomas@xxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

Thanks for your quick response and suggestions.

Now you need to look at
/etc/resolv.conf
route -n

[with eth0 up]
$ cat /etc/resolv.conf
[comments removed]
search local
nameserver 192.168.1.1

[with eth0 down]
$ cat /etc/resolv.conf
[comments removed]
search local
[=> no nameserver line! <=]

Well, you will certainly not be able to do anything. with that.
Either dhcp is screwed up or you did not tell it to give you a dns or you
have setup the router not to give dns to wireless clients.


[with eth0 up]
$ /sbin/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 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

[with eth0 down]
$ /sbin/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

Again, no default destination. I suspect that your router is set up to not
give dns or net access to wireless clients.



Can you ping the wireless nic?
$ ping 192.168.1.109
PING 192.168.1.109 (192.168.1.109) 56(84) bytes of data.
64 bytes from 192.168.1.109: icmp_seq=1 ttl=64 time=0.034 ms
64 bytes from 192.168.1.109: icmp_seq=2 ttl=64 time=0.030 ms
64 bytes from 192.168.1.109: icmp_seq=3 ttl=64 time=0.031 ms
[same with eth0 up or down]

Can you ping the address in /etc/resolv.conf?
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.278 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.204 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.284 ms
[same with eth0 up or down]

Is it the same as the address you get for your wired nics?
With eth0 up, /etc/resolv.conf has "nameserver 192.168.1.1".
I can ping this address whether or not eth0 is up. However,
this nameserver line is absent from /etc/resolv.conf if I
try to connect with wlan0 instead of eth0.

I wonder whether the problem has to do with DHCP. I think
that things are set up so that the nameserver data is
updated via DHCP.

Yes, it has to do with dhcp. It is not delivering dns or gateway info for
wireless clients. Misconfiguration of the modem or of the computer.
Now you could just have a little script
echo nameserver 192.168.1.1 >>/etc/resolv.conf
route add default gw 192.168.1.1 wlan0
after you bring up your wireless or find out where the misconfiguration is.



Do you have any ideas?

Thanks in advance.

Tom
--
Unruh wrote:
[snip]
.

Relevant Pages