Messages in this thread | | | Subject | Re: 2.4.18pre4aa1 | From | Robert Love <> | Date | 22 Jan 2002 05:12:28 -0500 |
| |
On Tue, 2002-01-22 at 05:02, Russell King wrote: > On Tue, Jan 22, 2002 at 02:37:42AM -0500, Dan Chen wrote: > > No weird anomalies here. I believe the ones you refer to were a result > > of ipv6 bits not being updated as well. Russell posted two patches for > > those. > > No - I do see weirdness in ipv4 as well:
OK, this is the anomaly I spoke of. Weird ICMP errors. I've seen others with this problem.
I don't think we have a proper solution here.
> bash-2.04# uptime > 10:00am up 18:57, 1 user, load average: 0.02, 0.03, 0.00 > bash-2.04# dmesg|grep 'broad' > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > 127.0.0.1 sent an invalid ICMP error to a broadcast. > > Only one of these happened on boot. The rest randomly pop up over time. > I'm going to try tcpdumping lo to see if I can work out what's causing > them.
Robert Love
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |