Note the differences in DHCP requests and responses, all on the same
device:
Jul 3 06:48:25 zsolt-1000H dhclient: Listening on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:25 zsolt-1000H dhclient: Sending on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:25 zsolt-1000H dhclient: Sending on Socket/fallback
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPREQUEST of 192.168.1.131 on eth0 to
255.255.255.255 port 67
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPNAK from 158.195.192.1
Jul 3 06:48:25 zsolt-1000H NetworkManager[900]: <info> (eth0): DHCPv4 state
changed preinit -> expire
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 3
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPOFFER of 192.168.1.131 from
192.168.1.254
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPREQUEST of 192.168.1.131 on eth0 to
255.255.255.255 port 67
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPNAK from 158.195.192.1
Jul 3 06:48:25 zsolt-1000H dhclient: DHCPACK of 192.168.1.131 from
192.168.1.254
Jul 3 06:48:47 zsolt-1000H NetworkManager[900]: <info> (eth0): DHCPv4 state
changed nbi -> preinit
Jul 3 06:48:47 zsolt-1000H dhclient: Listening on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:47 zsolt-1000H dhclient: Sending on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:47 zsolt-1000H dhclient: Sending on Socket/fallback
Jul 3 06:48:47 zsolt-1000H dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 3
Jul 3 06:48:47 zsolt-1000H dhclient: DHCPOFFER of 158.195.196.69 from
158.195.192.1
Jul 3 06:48:47 zsolt-1000H dhclient: DHCPREQUEST of 158.195.196.69 on eth0 to
255.255.255.255 port 67
Jul 3 06:48:47 zsolt-1000H dhclient: DHCPACK of 158.195.196.69 from
158.195.192.1
Jul 3 06:48:47 zsolt-1000H dhclient: bound to 158.195.196.69 -- renewal in
80033 seconds.
And it also seems to be on the same network, although a slightly
different connection. Please review your connections to make sure the
settings are all how they should be, and that your network is indeed
giving out the IP you really are expecting when the connection doesn't
work. Everything else related to the BIOS is probably coincidental, and
if not, it's a kernel issue.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805013
Title:
Network Manager unable to connect after anything changes in BIOS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/805013/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
