But isn't the DHCP REQUEST first? As far I understand we cast it on 255.255.255.255 so packet goes everywhere, then we receive an IP and send dhcp offer and routing table is afterwards updated? I have such output in sysconfig after wlan0 connects to my wireless:
Jun 4 14:46:29 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 4 14:46:29 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jun 4 14:46:29 lechup-laptop NetworkManager: <info> (wlan0): device state change: 5 -> 7 Jun 4 14:46:29 lechup-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Jun 4 14:46:29 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jun 4 14:46:29 lechup-laptop NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit Jun 4 14:46:29 lechup-laptop dhclient: Listening on LPF/wlan0/00:1b:77:b3:10:5d Jun 4 14:46:29 lechup-laptop dhclient: Sending on LPF/wlan0/00:1b:77:b3:10:5d Jun 4 14:46:29 lechup-laptop avahi-daemon[4363]: Registering new address record for fe80::21b:77ff:feb3:105d on wlan0.*. Jun 4 14:46:33 lechup-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 Jun 4 14:46:33 lechup-laptop dhclient: DHCPREQUEST of 192.168.1.79 on wlan0 to 255.255.255.255 port 67 Jun 4 14:46:33 lechup-laptop NetworkManager: <info> DHCP: device wlan0 state changed preinit -> bound Jun 4 14:46:33 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... Jun 4 14:46:33 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... Jun 4 14:46:33 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Jun 4 14:46:33 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. Jun 4 14:46:33 lechup-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Jun 4 14:46:33 lechup-laptop avahi-daemon[4363]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.79. Jun 4 14:46:33 lechup-laptop avahi-daemon[4363]: New relevant interface wlan0.IPv4 for mDNS. Jun 4 14:46:33 lechup-laptop avahi-daemon[4363]: Registering new address record for 192.168.1.79 on wlan0.IPv4. Jun 4 14:46:34 lechup-laptop NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Jun 4 14:46:35 lechup-laptop NetworkManager: <info> (wlan0): device state change: 7 -> 8 Jun 4 14:46:35 lechup-laptop NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Jun 4 14:46:35 lechup-laptop NetworkManager: <info> Policy set 'Auto Czuchnowskiego 12' (wlan0) as default for routing and DNS. The last step is to set the routing table and DNS. PS: After doing sudo route add default gw 192.168.1.1 I get an error, SIOCADDRT: No such process And nothing more happens?! Pozdrawiam Leszek Piątek jr 2009/6/3 jonj <jsj...@familyjackson.net>: > lechup, > > What is the output of the 'route' command on your system? I have a similar > issue, and for whatever reason, there was no 'default' entry in the route > table. The short-term solution for me is to run > sudo route add default gw <my router ip address> > > -- > dhcp fails, but succeeds after ifdown/ifup in rc.local > https://bugs.launchpad.net/bugs/374006 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in "network-manager" source package in Ubuntu: New > > Bug description: > Binary package hint: network-manager > > The bug occurred after upgrading to jaunty. > I'm not sure about the network-manager, it could also be the kernel, a driver > for my network card, > or perhaps the cause in the reorderings done to increase the booting speed in > jaunty. > Also I expect this to be duplicate bug, but I couldn't determine an existing > one that was really close enough. > > I reported this earlier at this existing report, but then found that > ubuntu-bug is preferred, so > I'm repeating this here: > > can't connect via dhcp > https://bugs.launchpad.net/bugs/312157 > > After boot using the default kernel there is no wired connection to the > internet, but everything on the local network is available. (ping by name to > local machines works, but pop for email fails.) > If I did not have another machine on the local network, I would have had no > way to know how to fix this, as this isolates the upgraded machine from the > internet. > > I can always correct this by doing: > > sudo ifdown eth0 > sudo ifup eth0 > > Since this is repeatable, I'd like to hunt it down to the source of the > problem, but I have no idea how to proceed. > > The network icon in the system tray does not show an active network > (neither wired nor wireless) before and after the ifdown/ifup fix. > > Any suggestions as to what I could do to fix this? > > ProblemType: Bug > Architecture: i386 > DistroRelease: Ubuntu 9.04 > Gconf: > > Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 > ProcEnviron: > PATH=(custom, user) > LANG=nl_NL.UTF-8 > SHELL=/bin/bash > SourcePackage: network-manager > Uname: Linux 2.6.28-11-generic i686 > WpaSupplicantLog: > -- dhcp fails, but succeeds after ifdown/ifup in rc.local https://bugs.launchpad.net/bugs/374006 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
