-   Linux - Networking (
-   - in Kernal IP routing table (

aikempshall 01-25-2004 11:37 AM in Kernal IP routing table
I have a Speedtouch 510iv4 which has entries in its IP route table for which has been fed through to the Kernal IP routing table table as follows

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface U 0 0 0 eth0 U 0 0 0 eth0 U 0 0 0 lo UG 0 0 0 eth0

What is Do I need it?

I've removed it from the Kernal IP routing table and from the IP route table of the Speedtouch, start/stop eth0 but it just reappears!

codedv 01-26-2004 03:02 AM

It looks like its the network your medem is connected to. It will be their while your modem is plugged in and connected.

aikempshall 01-26-2004 04:10 AM

It's not a network that I recognise. Where would the Kernal IP routing table get this address from?

codedv 01-26-2004 04:37 AM

Your modem will have an IP address and when it is connected a route to the network is usually added.

If you bring the eth0 interface down then the route should disappear.

You can also check the modems IP address. If it begins 169.254 then then the route is your modem.

tomaslarsson 01-26-2004 02:13 PM

I have the same entry, but on eth1 which is connected to my local LAN, not the adsl modem, so where does it come from.

Parksy 01-26-2004 05:46 PM

The 169.254 address range is used for some kind of intermediary step to the internet. The Speedtouch modem may always tell the computer that its ip address is in the 169.254 range because that range isn't used for the internet or for LANs, so it shouldn't conflict with anything.

That's just a guess. I don't know anything about those modems or much about the 169.254 addresses.

fataldata 01-26-2004 06:02 PM

the 169.254 addresses popup usually when you are using DHCP but have not been able to obtain an address. They are associated with DHCP and are not routable.

Found this thread on the net:

The range of 169.254.x.x has been reserved for this purpose. The idea is
that when DHCP fails, it still gives clients a way to communicate with
TCP/IP. It is, off course, not intended to production use, but it will give
the client a chance to use TCP/IP in order to recover. For example, on a
widely switched Ethernet backbone, it could enable the user to at least
e-mail MIS saying that their network connection is flaky.

tomaslarsson 01-27-2004 01:42 AM

But I'm not using DHCP, all my IP's are static.
One more thing, I cant delete it from the routing table.
NET not found is replied when i try to "route del", maybe I'm doing something wrong, but....

aikempshall 01-27-2004 04:54 AM

To delete the route need to supply more information -

route del -net netmask dev eth0

I did this to remove the entry from the table and also removed the corresponding entries from the modem. Recycled eth0 and 169.254 reappeared - spooky. Must also be added somewhere from within Linux.

aikempshall 01-27-2004 05:01 AM

Sorry should be of course -

route del -net netmask dev eth0

tomaslarsson 01-27-2004 05:03 AM

Tnx aikempshall, it worked.
The big question is where does this route come from?

fataldata 01-27-2004 10:10 AM

Well I'm not sure about the DHCP causing the route entry and subsequent address, but I have encountered it many times when I would configure an adapter for DHCP, but it failed to get an address so instead it would use the

Glad you were able to remove the entry anyhow.

guillote 03-10-2004 03:36 PM

for delete that route only add NOZEROCONF=yes to /etc/sysconfig/network file and restart the network (/sbin/service network restart)

Salut !

charon79m 03-11-2004 12:30 AM

APIPA is what the 169.254 address scheme is. Automatic Private IP Addressing is what it stands for. Micro$oft uses it to address a NIC when DHCP fails. It's kind of becoming a standard though not and RFC, at least not one I'm aware of.

There is no problem with it being in your routing table, it will not affect your IP routing.

Hope it helps.


All times are GMT -5. The time now is 01:19 PM.