After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 352731 - fake route is added to loopback when using link-local address obtained by zeroconf
fake route is added to loopback when using link-local address obtained by zer...
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2006-08-24 20:48 UTC by Gergely Gábor
Modified: 2008-08-18 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gergely Gábor 2006-08-24 20:48:28 UTC
Please describe the problem:
A fake route is (also) added (before the correct one) to the routing tables when NM obtaines a link-local ip addr by zeroconf. The packets therefore go to a wrong way. To work around, you only have to remove the fake route

Steps to reproduce:
1. Start NM.
2. obtain a link-local address
3. try to figure out, why nothing works


Actual results:
the packets go wrong way

Expected results:
for example ping to work

Does this happen every time?
yes, it does.

Other information:
a simple workaround is present: add the following script ot the /etc/NetworkManager/dispatcher.d drectory, make it executeable, and us NM-dispatcher as well. Here comes the script:
#!/bin/sh

if [ "$1" == "eth0" ]; then
        if [ "$2" == "up" ] ;then

                if [ `/sbin/route | grep lo | grep "169.254" | wc -c ` -gt 0 ] ; then
                        /sbin/ip route flush dev lo;
                        logger "NetworkManagerDispatcher::kill_fake_loopback_routes.sh: Once again a Link-local adress has been obtained... so I have to do my work... to work around: )"
                fi;
        fi;
fi;
Comment 1 Dan Williams 2008-08-17 23:17:04 UTC
Can you paste the output of "/sbin/route -n" and "/sbin/ip route list" when the problem occurs into this bug report?  Thanks!
Comment 2 Gergely Gábor 2008-08-18 09:52:37 UTC
Actually since then, I've left fedora, that used NM by default, to gentoo, that i'm just about to leave in favour of NetBSD, and I have stopped using NM in favour of openrc, and wpa_supplicant-gui, so I cannot confirm or deny the existence of the bug anymore.

Best regards: Gergely Gábor
Comment 3 Dan Williams 2008-08-18 17:47:01 UTC
ok, closing as fixed since the auto-ip code has undergone a substantial rewrite and I'm pretty sure we don't touch lo routes any more.