[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work

2007-04-25 Thread Martin Pitt
*** This bug is a duplicate of bug 82335 ***
https://bugs.launchpad.net/bugs/82335

** This bug has been marked a duplicate of bug 82335
   network-manager should not set offline mode when it manages no device

-- 
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu (via bug
82335).

-- 
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work

2007-04-02 Thread Tom Wood
Tracked the problem down to NetworkManager.  Implementing the steps
necessary to turn off NetworkManager as referenced in bug # 82335
alleviates the problem.

As stated in bug # 82335, NetworkManager really needs not to cause this
conflict on a purely statically addressed machine.

-- 
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work

2007-04-02 Thread Tom Wood
Changed package to reflect actual source of the problem.

** Changed in: network-manager (Ubuntu)
Sourcepackagename: ifupdown => network-manager

-- 
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 97058] Re: adding non-default route in /etc/network/interfaces doesn't work

2007-04-02 Thread Tom Wood
After booting, the "up route ..." line is not run, as evidenced by
"netstat -r" not showing the route specified.  However, running
"/etc/init.d/networking stop" followed by "/etc/init.d/networking start"
after boot runs the "up route ..." line.  Race condition of some sort,
perhaps, at boot time?

** Description changed:

  Binary package hint: ifupdown
  
  As I understand it, the proper way to introduce a non-default route at
  boot time is to add a "up route add -net ..." line to the network
  interface in question to the /etc/network/interfaces file in the
  interface stanza, like so:
  
  iface eth0 inet static
  address 10.1.1.123
  netmask 255.255.255.0
  network 10.1.1.0
  broadcast 10.1.1.255
  gateway 10.1.1.1
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-nameservers 192.168.1.50
  dns-search example.com
  up route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.1.1.2
  
  However, the "up route" line doesn't get executed.
  
  As a separate but related issue, there's no way using
  System->Administration->Network to add a non-default route either.  That
- would be a nice RFQ.
+ would be a nice idea for an enhancement.

-- 
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs