Re: dhcp connects but cannot resolve names
On 2008-02-04 13:15:17 +0100, oxy wrote: i get a wifi dhcp connection at home, but cannot resolve names. Bug 462570? -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp connects but cannot resolve names
On Mon, 4 Feb 2008 13:15:17 +0100, oxy [EMAIL PROTECTED] wrote: me% dhclient ath0 There is already a pid file /var/run/dhclient.pid with pid 5104 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wifi0: unknown hardware address type 801 wifi0: unknown hardware address type 801 Listening on LPF/ath0/hardware address Sending on LPF/ath0/hardware address Sending on Socket/fallback DHCPREQUEST on ath0 to 255.255.255.255 port 67 DHCPACK from 192.168.2.1 bound to 192.168.2.36 -- renewal in 164964 seconds. me% ifconfig ath0 ath0 Link encap:Ethernet HWaddr hardware address inet addr:192.168.2.36 Bcast:192.168.2.255 Mask:255.255.255.0 The DHCP server at 192.168.2.1 handed you an address - OK. It should have also handed the client additional network information such as a default route, name servers, etc. me% route add default gw 192.168.2.36 This is incorrect. The gateway will be a router - you have defined the default gateway to be your own client machine. I would start over downing the ath0 interface, and going back through your routine, stopping after you get an IP from 'dhclient ath0'. Assuming the DHCP server is also the gateway router (and the DHCP server is configured properly), you should already have a default gateway route of 192.168.2.1. What is the output of the command 'route -n'? me% nslookup www.yahoo.com ;; connection timed out; no servers could be reached Check the contents of /etc/resolv.conf for 'nameserver [IP_address]' entries. 'cat /etc/resolv.conf'? Can you ping those IP addresses? To see what the DHCP server is actually handing the client, 'cat /var/lib/dhcp3/dhclient.ath0.leases', please. -- Kind Regards, Michael Shuler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dhcp connects but cannot resolve names
Hi friends, i get a wifi dhcp connection at home, but cannot resolve names. I can ping ip addresses around the world, but cannot ping hostnames, since they are not resolved. I configured with iwconfig, iwpriv as shown bellow. The first configuration i tried with network manager. No success, but many people report problems with it anyway. Take a look at my main steps to connection: me% iwconfig ath0 essid server name key numbers me% iwpriv ath0 authmode 1 me% iwconfig ath0 ap hardware address me% dhclient ath0 There is already a pid file /var/run/dhclient.pid with pid 5104 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wifi0: unknown hardware address type 801 wifi0: unknown hardware address type 801 Listening on LPF/ath0/hardware address Sending on LPF/ath0/hardware address Sending on Socket/fallback DHCPREQUEST on ath0 to 255.255.255.255 port 67 DHCPACK from 192.168.2.1 bound to 192.168.2.36 -- renewal in 164964 seconds. me% echo but i am connected, look the ping .. me% ping 64.233.187.99 PING 64.233.187.99 (64.233.187.99) 56(84) bytes of data. 64 bytes from 64.233.187.99: icmp_seq=3 ttl=240 time=194 ms 64 bytes from 64.233.187.99: icmp_seq=4 ttl=240 time=189 ms 64 bytes from 64.233.187.99: icmp_seq=7 ttl=240 time=186 ms ... ... ... me% ifconfig ath0 ath0 Link encap:Ethernet HWaddr hardware address inet addr:192.168.2.36 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::bla bla bla/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:572 errors:0 dropped:0 overruns:0 frame:0 TX packets:493 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:186953 (182.5 KiB) TX bytes:102942 (100.5 KiB) me% route add default gw 192.168.2.36 me% nslookup www.yahoo.com ;; connection timed out; no servers could be reached me% echo its a debian etch, madwifi driver, atheros r5 card :-) \ thanks in advance for any help ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp connects but cannot resolve names
Hi friends, i got the connection with this /etc/network/interfaces file: iface ath0 inet dhcp wireless-essid xxx wireless-key a number auto ath0 My question now is, something is asking me on boot time which connection i should try, netenv.conf or new connection. Can i disable that? Also, how can i inform in /etc/network/interfaces that my connection is Master, WEP, open? I wanna know details for next configurations. Thank you very much for the nice help ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
