** Summary changed:

- NetworkManager creates bogus default route for interfaces in 
/etc/network/interfaces without gateway
+ NetworkManager assigns default route to one of two interfaces despite their 
both being defined in /e/n/i and managed=false

-- 
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/442972

Title:
  NetworkManager assigns default route to one of two interfaces despite
  their both being defined in /e/n/i and managed=false

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

Bug description:
  Binary package hint: network-manager

  This bug may be related to bug #435620 or bug #442957.

  I have two wired network interfaces (one physical, one tagged (eth0.2) and 
one untagged (eth0) vlan). Both are configured statically in 
/etc/network/interfaces. My default gateway is on eth0.2:
  auto lo eth0 eth0.2
  iface lo inet loopback

  iface eth0 inet static
      address 172.19.0.33
      netmask 255.255.255.0

  iface eth0.2 inet static
      address 145.x.x.x
      netmask 255.255.255.248
      gateway 145.x.x.y

  Network manager is set not to touch this:
  [main]
  no-auto-default=00:15:17:xx:xx:xx
  [ifupdown]
  managed=false

  This used to work fine with jaunty. After the upgrade to karmic NM started to 
manage these interfaces. But worse, it adds a bogus default route for eth0:
  145.x.x.z/29 dev eth0.2  proto kernel  scope link  src 145.x.x.x
  172.19.0.0/24 dev eth0  proto kernel  scope link  src 172.19.0.33 
  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
  169.254.0.0/16 dev eth0  scope link  metric 1000 
  default via 172.19.0.33 dev eth0  proto static # this is the local IP address
  default via 145.x.x.y dev eth0.2  metric 100 

  According nm-applet, ifupdown (eth0) is enabled and ifupdown (eth0.2) is 
disabled, even though both are up and working. This may be why it adds a 
default route to eth0 in a desperate attempt to reach at least some hosts, 
although a high metric would be nice in that case. Even if I add a default 
route to eth0 with a higher metric, NM still overrides it with a new default 
route with a zero metric. After start networking but before start 
network-manager:
  145.x.x.z/29 dev eth0.2  proto kernel  scope link  src 145.x.x.x
  172.19.0.0/24 dev eth0  proto kernel  scope link  src 172.19.0.33 
  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
  169.254.0.0/16 dev eth0  scope link  metric 1000 
  default via 145.x.x.y dev eth0.2  metric 100 
  default via 172.19.0.65 dev eth0  metric 200

  After start network-manager:
  145.x.x.z/29 dev eth0.2  proto kernel  scope link  src 145.x.x.x
  172.19.0.0/24 dev eth0  proto kernel  scope link  src 172.19.0.33 
  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
  169.254.0.0/16 dev eth0  scope link  metric 1000 
  default via 172.19.0.65 dev eth0  proto static 
  default via 145.x.x.y dev eth0.2  metric 100 
  default via 172.19.0.65 dev eth0  metric 200

  The best solution in this case would probably for NM to start honoring
  managed=false again, although it would be nice if it were somewhat
  smarter about default routes and interfaces being up (if state=UP, the
  media state is up and it's got an IP address, it's probably up).

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Mon Oct  5 11:35:25 2009
  DistroRelease: Ubuntu 9.10
  Gconf:
   
  IpRoute:
   145.99.245.96/29 dev eth0.2  proto kernel  scope link  src 145.99.245.98 
   172.19.0.0/24 dev eth0  proto kernel  scope link  src 172.19.0.33 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   default via 145.99.245.97 dev eth0.2  metric 100
  Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
  RfKill:
   
  SourcePackage: network-manager
  Uname: Linux 2.6.31-11-generic x86_64
  WpaSupplicantLog:
   
  XsessionErrors:
   (gnome-settings-daemon:10063): GLib-CRITICAL **: g_propagate_error: 
assertion `src != NULL' failed
   (gnome-settings-daemon:10063): GLib-CRITICAL **: g_propagate_error: 
assertion `src != NULL' failed
   (polkit-gnome-authentication-agent-1:10105): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:10101): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:10097): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to 
allocate widget with width -6 and height 24

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to