desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/805013

Title:
  Network Manager unable to connect after anything changes in BIOS

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  When I change the 1st boot device in BIOS, this always happens. Then I
  need to enable LAN boot (which is useless for me otherwise) and it
  starts working again. But today it didn't, so I just created a new
  wired connection in Network Manager and whoala, I had internet again.
  Which means that the problem is not in BIOS, as I had thought. By "no
  connection" I mean that I receive an IP address, but no data comes
  through.

  I have an EeePC 1000H with the original BIOS (came with WinXP)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Jul  3 09:06:44 2011
  ExecutablePath: /usr/sbin/NetworkManager
  Gconf:

  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   158.195.192.0/19 dev eth0  proto kernel  scope link  src 158.195.196.69  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
   default via 158.195.192.1 dev eth0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  ProcEnviron: PATH=(custom, no user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/805013/+subscriptions