Networking sets up a default route to every interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Low
|
Basilio Kublik |
Bug Description
Binary package hint: network-manager
I've seen similar bug reports, but wasn't sure if I should just add to them or report this one as new.
I have a test machine with two network interfaces. Gutsy detected them as eth0 and eth2 (I don't know why no eth1, but for this bug it doesn't matter).
The usual configuration for this machine is to have one network card (eth0) connected to the 172.17.x.x network and the other to the 192.168.0.x network. My router to the Internet is on the 172.17.x.x network, so I want the default route (0.0.0.0/0) to be to eth0.
Problem is, for some reason, Gutsy insists on setting up two default routes. When I look at the routing table, I have two "default" entries, one to eth0, and one to eth2. Unless I've missed something very fundamental in my networking theory, there can be only one default route (no load balancing). What's even more unnerving, is the fact that the first default route in the table always seems to be the wrong one. That may just be bad luck, but it's quite annoying.
Just a side note, I multi-boot this machine with Windows XP, RHEL 5 (soon to be 5.1) and Ubuntu. The networking works correctly with RHEL 5.0 and Windows XP.
Forgot one thing . . .
Simply entering:
route del default
at a bash prompt does fix the problem, but it doesn't seem to work from rc.local, plus it really should be necessary.