Public bug reported:
Binary package hint: network-manager
I have a wired interface and a wireless interface, which both connect through
to the same network (although incorrect behaviour has been observed on a
machine with just a wired interface).
It seems that in some situations NM ends up with a routing table that has a
host route for the router and a default route, but no network route. Or the
network route may be on a different interface.
Attached is a syslog snippet which shows network manager connecting
correctly and producing a routing table of:
Destination Gateway Genmask Flags Metric Ref Use Iface
10.45.43.0 0.0.0.0 255.255.255.0 U 1 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1
0.0.0.0 10.45.43.1 0.0.0.0 UG 0 0 0 eth1
At around 15:09 it then changes the routing table to having
10.45.43.1/255.255.255.255 via eth1, 0.0.0.0/0.0.0.0 via 10.45.43.1 and
10.45.43.0/255.255.255.0 via wlan0.
On the machine which had no wireless, this left it with just routes for
10.45.43.1 and 0.0.0.0 - traffic for 10.45.43.0/24 would go via the
router (which is blocked, so no LAN traffic was able to flow, so no DNS
lookups to .2, printing to .5, etc)
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
odd routing behaviour
https://bugs.launchpad.net/bugs/279647
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
