On Sunday 09 May 2004 07:11 pm, mailinglists@ianschorr.com wrote:

What does ifconfig say about eth0? Does the route go away if you ifdown and ifup eth0?

Quoting Glenn Holmer :

...

I've seen this on a couple machines already: on my internal network, using 192.168.1.x, "route -n" is showing

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.7 0.0.0.0 UG 0 0 0 eth0

Where is the 169.254.0.0 coming from? I wasn't seeing this with 9.0.

Do a whois 169.254.0.0 and you'll see it is called part of the Blackhole. As I read it, it is the /dev/null for wayward machines who cannot get an IP from their dns. Nothing to really worry about except figuring how to get your machine back talking to its DNS. See the RFC 3330. I first came across it a few days ago when my Firewall blocked me from going out onto the net. To me it simply means something like - You dumass you forgot to set up your firewall properly, which is what happened to me but then I dont do windows often enough to care. Rebooted to Linux where I have much better problems. Richard

This appears to be due to the fact that you have zeroconf ("Rendevous" in Apple-speak) running on your system. https://listman.redhat.com/archives/shrike-list/2003-September/msg00895.html http://www.zeroconf.org/Rendezvous/Linux.html Unless someone can help me get 9.1 to run, I can't verify this, but presumably you have an entry in your ifup script that says something like: ip route replace 169.254.0.0/16 dev ${REALDEVICE} Presumably adding this route will bridge the commonly used zero-conf network through one of your physical interfaces, for communication with other zero-conf (Rendezvous) devices. OS X uses Rendezvous for all sorts of cool things, I'm not sure how Linux/SuSE uses it. Perhaps someone else can shed some light here... Ian Quoting Michael Nelson :

On Sun, May 09, 2004 at 06:10:20PM -0500, Glenn Holmer wrote:

...

I've seen this on a couple machines already: on my internal network, using 192.168.1.x, "route -n" is showing

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.7 0.0.0.0 UG 0 0 0 eth0

Where is the 169.254.0.0 coming from? I wasn't seeing this with 9.0.

I'm seeing the same with 9.1, and ifconfig eth0 output looks normal.

Michael

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Quoting Michael Nelson :

On Sun, May 09, 2004 at 06:54:41PM -0700, mailinglists@ianschorr.com wrote:

...

This appears to be due to the fact that you have zeroconf ("Rendevous" in Apple-speak) running on your system.

Nope. I never even heard of zeroconf before your message, and there are no Macs here.

It's hard-coded in /etc/sysconfig/network/scripts/ifup-route, and I didn't put it there, SuSE did.

I didn't say you did. I said that you have zeroconf running on your system. I was simply answering the original message about where the route came from. ...And the Apple comment was just to give context since that's the only implementation of zeroconf, the technology, that many people are interested in. Ian