[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
Hi, the file /var/lib/dhcp3/dhclient.eth0.leases does not exist. In the directory, only dhclient.leases exists, but it is empty. The following is the result of grep dhcp syslog, even though I don't think this is really what you meant: Feb 10 14:19:33 qwghlm dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Feb 10 14:26:35 qwghlm dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Feb 10 14:26:35 qwghlm dhclient: can't create /var/lib/dhcp3/dhclient.leases: Permission denied Feb 10 14:30:32 qwghlm NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 3771 Feb 10 14:30:38 qwghlm dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Feb 10 14:31:36 qwghlm NetworkManager: info eth0: canceled DHCP transaction, dhcp client pid 4835 Feb 10 14:31:40 qwghlm dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Feb 10 14:37:02 qwghlm dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Instead, in the following are the lines that I think are of interest: Feb 10 14:37:05 qwghlm dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 int erval 3 Feb 10 14:37:05 qwghlm dhclient: DHCPOFFER of 192.168.1.1 from 192.168.1.254 Feb 10 14:37:05 qwghlm dhclient: DHCPREQUEST of 192.168.1.1 on eth0 to 255.255.255.2 55 port 67 Feb 10 14:37:05 qwghlm dhclient: DHCPACK of 192.168.1.1 from 192.168.1.254 Feb 10 14:37:05 qwghlm NetworkManager: info DHCP: device eth0 state changed prein it - bound Feb 10 14:37:05 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Co nfigure Get) scheduled... Feb 10 14:37:05 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Co nfigure Get) started... Feb 10 14:37:05 qwghlm NetworkManager: infoaddress 192.168.1.1 Feb 10 14:37:05 qwghlm NetworkManager: infoprefix 24 (255.255.255.0) Feb 10 14:37:05 qwghlm NetworkManager: infonameserver '192.168.1.254' Feb 10 14:37:05 qwghlm NetworkManager: infodomain name 'lan' Feb 10 14:37:05 qwghlm NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Feb 10 14:37:05 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Feb 10 14:37:05 qwghlm NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... And this is how it looks in intrepid: Feb 12 07:26:24 qwghlm dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 int erval 7 Feb 12 07:26:24 qwghlm avahi-daemon[4982]: Registering new address record for fe80:: 21e:37ff:fe15:1b70 on eth0.*. Feb 12 07:26:26 qwghlm dhclient: DHCPOFFER of 192.168.1.1 from 192.168.1.254 Feb 12 07:26:26 qwghlm dhclient: DHCPREQUEST of 192.168.1.1 on eth0 to 255.255.255.2 55 port 67 Feb 12 07:26:26 qwghlm dhclient: DHCPACK of 192.168.1.1 from 192.168.1.254 Feb 12 07:26:26 qwghlm NetworkManager: info DHCP: device eth0 state changed prein it - bound Feb 12 07:26:26 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Co nfigure Get) scheduled... Feb 12 07:26:26 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Co nfigure Get) started... Feb 12 07:26:26 qwghlm NetworkManager: infoaddress 192.168.1.1 Feb 12 07:26:26 qwghlm NetworkManager: infoprefix 24 (255.255.255.0) Feb 12 07:26:26 qwghlm NetworkManager: infogateway 192.168.1.254 Feb 12 07:26:26 qwghlm NetworkManager: infonameserver '192.168.1.254' Feb 12 07:26:26 qwghlm NetworkManager: infodomain name 'lan' Feb 12 07:26:26 qwghlm NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Co nfigure Commit) scheduled... Feb 12 07:26:26 qwghlm NetworkManager: info Activation (eth0) Stage 4 of 5 (IP Co nfigure Get) complete. Feb 12 07:26:26 qwghlm NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Co nfigure Commit) started... So, it really looks like what you have said: the gateway isn't set during the DHCP request. As it works without any trouble in intrepid, I do dare to say that it must be ome problem with either dhclient or NetworkManager. Do you have any idea how I can get more detailed information? ** Changed in: ubuntu Status: Incomplete = New -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
I' moving this now to network-manager, as I think it is connected to either network-manager, or dhclient. ** Changed in: network-manager (Ubuntu) Sourcepackagename: None = network-manager -- Jaunty alpha 4: n-m doesn't get gateway https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
** Changed in: ubuntu Status: New = Incomplete -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
Hi, thanks again. In order to determine whether or not it's actually a dhcp problem, could you try including the contents of the following files in the report: * /var/lib/dhcp3/dhclient.eth0.leases * The output of 'grep dhcp /var/log/syslog' -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
** Description changed: I don't know which package to assign this to, as it a pretty general problem. I have installed Kubuntu Jaunty alpha 4 on an AMD64 machine (Lenovo Thinkpad R61, Core 2 Duo). The machine is connected to the internet via a router. When logging in, the network manager plasma apparently correctly - connects to the network, both wireless or wired. + connects to the network, both wireless or wired. For details, see the + output of ifconfig below. However, when I try to connect to any network address (e.g. via ping, konqueror, or anything), the network seems to be unreachable (ping says: connect: Network unreachable). Only the addresses on the router itself - work fine. + work fine. See output of the ping commands. When I use DNS (via host or nslookup), everything works fine, even when I try to resolve addresses that I have never used before (so the router cannot have them in its cache). This proves that the router does have network connection. However, the problem is NOT the setup of the router, - as everything works fine when I use intrepid. - - I had created a log of the output of various commands yesterday, but - can't find them anymore, so I will have to redo this in time to attach - more information. + as everything works fine when I use intrepid. See the output of the + host commands. The problem might be related to bug 326718 or bug 326003. + + Output of some commands: + + ol...@qwghlm:~$ lsb_release -ar + No LSB modules are available. + Distributor ID: Ubuntu + Description:Ubuntu jaunty (development branch) + Release:9.04 + Codename: jaunty + + ol...@qwghlm:~$ ifconfig + eth0 Link encap:Ethernet HWaddr 00:1e:37:15:1b:70 + inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 + inet6 addr: fe80::21e:37ff:fe15:1b70/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:16 errors:0 dropped:0 overruns:0 frame:0 + TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:100 + RX bytes:2094 (2.0 KB) TX bytes:4571 (4.5 KB) + Memory:fe00-fe02 + + loLink encap:Local Loopback + inet addr:127.0.0.1 Mask:255.0.0.0 + inet6 addr: ::1/128 Scope:Host + UP LOOPBACK RUNNING MTU:16436 Metric:1 + RX packets:16 errors:0 dropped:0 overruns:0 frame:0 + TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:776 (776.0 B) TX bytes:776 (776.0 B) + + ol...@qwghlm:~$ ping www.heise.de + connect: Network is unreachable + + ol...@qwghlm:~$ host www.heise.de + www.heise.de has address 193.99.144.85 + www.heise.de mail is handled by 10 listserv.heise.de. + + ol...@qwghlm:~$ ping www.xyz.com + connect: Network is unreachable + + ol...@qwghlm:~$ host www.xyz.com + www.xyz.com has address 199.26.172.101 + www.xyz.com mail is handled by 10 penguin.xyz.com. -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
Hi, Can you please include the output of ip route? 'Network is unreachable' generally means your computer doesn't know where to send packets for the destination; lack of a default route is the most obvious cause. That could be caused by a problem with your DHCP server, (less likely) with Jaunty's DHCP client or even (but *much* less likely) with the Jaunty kernel. -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
** Changed in: ubuntu Status: New = Incomplete -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326802] Re: Jaunty alpha 4: IP address set, but still no network
Here is the output of ip route: ol...@qwghlm:~$ ip route 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 And this is the output of ip route on intrepid on the same computer, using the same router: [12:16:33]qwghlm:~ ip route 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.1.254 dev eth0 proto static So, I don't think that this is a problem of the router, therefore I guess that it has something to do with the dhcp client - or the kernel, as you say. I would be happy to help looking into the details. ** Changed in: ubuntu Status: Incomplete = New -- Jaunty alpha 4: IP address set, but still no network https://bugs.launchpad.net/bugs/326802 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
