I’m currently struggling with the following problem:
Connecting to a wired network with NetworkManager (0.7.1) is no problem at all: Everything is set up automatically, including the default route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.178.0 * 255.255.255.0 U 1 0 0 eth0
192.168.178.0 * 255.255.255.0 U 2 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
default fritz.box 0.0.0.0 UG 0 0 0 eth0
However, if no cable is connected the default route is deleted in the table (even though the wireless network interface itself gets configured correctly):
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.178.0 * 255.255.255.0 U 2 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
When I now add the route manually it works.
But as soon as the cable is plugged in, the NetworkManager overwrites the routing table entry again (which makes it quite annoying).
On 07/11/2010 10:36 AM, MartinWegner wrote:
>
> Hi folks,
>
> I’m currently struggling with the following problem:
>
> Connecting to a wired network with NetworkManager (0.7.1) is no problem
> at all: Everything is set up automatically, including the default
> route:
>
> Code:
> --------------------
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.178.0 * 255.255.255.0 U 1 0 0 eth0
> 192.168.178.0 * 255.255.255.0 U 2 0 0 eth1
> loopback * 255.0.0.0 U 0 0 0 lo
> default fritz.box 0.0.0.0 UG 0 0 0 eth0
>
> --------------------
>
>
> However, if no cable is connected the default route is deleted in the
> table (even though the wireless network interface itself gets configured
> correctly):
>
> Code:
> --------------------
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.178.0 * 255.255.255.0 U 2 0 0 eth1
> loopback * 255.0.0.0 U 0 0 0 lo
>
> --------------------
>
>
> When I now add the route manually it works.
> But as soon as the cable is plugged in, the NetworkManager overwrites
> the routing table entry again (which makes it quite annoying).
>
> Does anyone know a way to avoid this behaviour?
Which version of openSUSE? If it is 11.2, is this a new installation? Have
you done the upgrades? The distribution media have a bug that does exactly
what you describe, but it is fixed.
Yes, it’s 11.2 and yes, I’ve done all upgrades (afaik).
Do you happen to know which package contains the bug (NetworkManager?) and from which version on it is fixed?
Yes: I changed the IP-addres option from “DHCP” to “manual configuration” in order to be able to specify a default gateway - no success
Apart from that I found that the nameserver entry was deleted, too (even though I had specified it in the NetworkManager as well), so I had to edit /etc/resolv.conf manually to make it work.
On 07/12/2010 03:56 PM, MartinWegner wrote:
>
> lwfinger;2187254 Wrote:
>> On 07/11/2010 10:36 AM, MartinWegner wrote:
>> Which version of openSUSE? If it is 11.2, is this a new installation?
>> Have
>> you done the upgrades? The distribution media have a bug that does
>> exactly
>> what you describe, but it is fixed.
>
> Yes, it’s 11.2 and yes, I’ve done all upgrades (afaik).
> Do you happen to know which package contains the bug (NetworkManager?)
> and from which version on it is fixed?
No, I do not know which component has the problem, but I know it was fixed
immediately after 11.2 was released. I always let DHCP get the DNS entry. After
the update, all that was necessary was to delete /etc/resolv.conf and remake the
connection using the NM applet.
I’m thinking out on a limb here.
Maybe because you have eth0 and eth1 with the same IP address to the router its already assigned the route for wired so and doesn’t seek another route when wired is unplugged.
I reserve IP addresses on the router for each MAC address of my core network. IOW, Box #3 has different IP address for eth0 and eth1.