ifconfig alias creates bogus route
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| net-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Routes begin looking like this:
root@net2:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 96.31.77.1 0.0.0.0 UG 100 0 0 eth0
localnet * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
root@net2:~# ifconfig eth0:1 96.31.77.160 up
New ip can be pinged, but other off machine pings fail because
of munged routing, which now looks like this:
Destination Gateway Genmask Flags Metric Ref Use Iface
default 96.31.77.1 0.0.0.0 UG 100 0 0 eth0
96.0.0.0 * 255.0.0.0 U 0 0 0 eth0
localnet * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
Problem is fixed by this:
root@net2:~# route del -net 96.0.0.0 netmask 255.0.0.0 dev eth0
root@net2:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 96.31.77.1 0.0.0.0 UG 100 0 0 eth0
localnet * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
Questions include:
1) Where's this bogus route coming from?
2) How to issue ifconfig and suppress route creation?
/etc/network/
# The primary network interface
auto eth0
iface eth0 inet static
address 96.31.77.159
netmask 255.255.255.0
network 96.31.77.0
broadcast 96.31.77.255
gateway 96.31.77.1
# dns-* options are implemented by the resolvconf package, if installed
dns-search davidfavor.com
auto eth0:1
iface eth0:1 inet static
address 96.31.77.160
netmask 255.255.255.0
| David Favor (davidfavor) wrote | #1 |
| Andreas Henriksson (andreas-fatal) wrote | #2 |
| affects: | iproute (Ubuntu) → net-tools (Ubuntu) |
| Changed in net-tools (Ubuntu): | |
| status: | New → Invalid |
Hum... Using inotifywait on /etc and /run shows no file access.
So another question also:
3) From where does ifconfig get it's interface configuration information?