** Summary changed:

- Previously working DHCP on wired ethernet is assigned static IP from 
unrelated interface after upgrade to Intrepid
+ ifupdown plugin should not export any parse connection configuration when 
running in managed=false mode (Was: Previously working DHCP on wired ethernet 
is assigned static IP from unrelated interface after upgrade to Intrepid)

** Description changed:

- 
- Proposed fix: for managed=false the ifupdown plugin should only parse the 
configuration, but dont export any connection config.
+ Proposed fix: for managed=false the ifupdown plugin should only parse
+ the configuration, but dont export any connection config.
  
  Binary package hint: network-manager
  
  I'm using Intrepid Ibex, just upgraded from Hardy.
  
  The version of network-manager is svn20081018t105859-0ubuntu1, but I
  don't know if that was the version which broke the configuration, or if
  network-manager has been upgraded in Intrepid since October 26th.
  
  Since the upgrade, a previously working laptop with wired and wireless
  networks broke both.  The wireless breakage is perhaps reported
  elsewhere; this is about the wired connection.
  
  Previously, it would use DHCP on eth0 if there was a cable plugged in.
  Very sensible.
  
  Now, the nm-applet dialog shows:
  
        Wired connections
        ifupdown (tap2)
        ifupdown (tap0)
        ifupdown (tap1)
  
        Wireless connections
        [access points if any]
  
  When I plug a cable into eth0, it then assigns a _static_ configuration
  to eth0, which has no relevance to eth0.   (This is the opposite of a
  bug others have reported where static configurations change to DHCP
  after upgrade :-) )
  
  Specifically, after plugging in a cable, nm-applet shows it has selected
  "ifupdown (tap1)", and is applying static IP 10.1.1.1 to _eth0_, which
  is the static IP that is given for tap1 in /etc/network/interfaces.
  
  My full /etc/network/interfaces, with comments removed, is as follows:
  
  auto lo
  iface lo inet loopback
  
  iface ppp0 inet ppp
          provider BluetoothDialup
  iface ppp1 inet ppp
          provider free-dialup
  iface ppp2 inet ppp
          provider cameldial
  iface ppp3 inet ppp
          provider freeukisp
  iface ppp4 inet ppp
          provider 123-reg
  auto ppp0
  auto tap0
  iface tap0 inet static
        address 10.1.100.1
        netmask 255.255.255.0
        tunctl_user jamie
  auto tap1
  iface tap1 inet static
        address 10.1.1.1
        netmask 255.255.255.0
        tunctl_user jamie
  auto tap2
  iface tap2 inet static
        address 10.1.2.1
        netmask 255.255.255.0
        tunctl_user jamie
  
  Sometime in the past, it also has "auto eth0" and maybe "iface eth0 inet
  dhcp", but I removed those to let NetworkManager handle eth0 in Hardy.
  
  Intrepid selected "ifupdown (tap1)" and proceeds to set eth0 to its
  settings, which have never been appropriate for eth0:
  
  [EMAIL PROTECTED]:~$ ifconfig eth0
  eth0      Link encap:Ethernet  HWaddr 00:16:36:4f:e6:80  
            inet addr:10.1.1.1  Bcast:10.1.1.255  Mask:255.255.255.0
            inet6 addr: fe80::216:36ff:fe4f:e680/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000 
            RX bytes:0 (0.0 B)  TX bytes:5265 (5.2 KB)
  
  
  So my questions / bug report are:
  
      - Why did it create "ifupdown (tap0)" (+tap1, +tap2) connections?
  (I can see them in Edit Connections in nm-applet, btw).
  
      - Having imported data for those connections on upgrade to Intrepid,
  why does it then _apply_ the settings for tap1 to eth0???!!!!  That is
  obviously wrong.
  
      - Why does it not have a DHCP connection under the Wired Networks
  created, since that's what eth0 was doing before the upgrade.
  
  I've worked around this by running "sudo dhclient eth0", and later by
  creating another connection in Edit Settings called simply "DHCP", and
  explicitly selecting that.  I've no idea what the normal process would
  have called the connection, and it's kind of ugly to have: "Wired
  Settings" "DHCP" in nm-applet's main window, but that's purely cosmetic.
  
  I'd provide a screenshot, but Alt-PrintScreen doesn't work when nm-
  applet's main selection window is popped up.
  
  Thanks.

** Summary changed:

- ifupdown plugin should not export any parse connection configuration when 
running in managed=false mode (Was: Previously working DHCP on wired ethernet 
is assigned static IP from unrelated interface after upgrade to Intrepid)
+ ifupdown plugin should not export any parsed connection configuration when 
running in managed=false mode (Was: Previously working DHCP on wired ethernet 
is assigned static IP from unrelated interface after upgrade to Intrepid)

-- 
ifupdown plugin should not export any parsed connection configuration when 
running in managed=false mode (Was: Previously working DHCP on wired ethernet 
is assigned static IP from unrelated interface after upgrade to Intrepid)
https://bugs.launchpad.net/bugs/291902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to