[lkml]   [1998]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Odd error.
Ok.  I will grant that just for the simple fact that A) Its happening;
and; B) You have quite a bit more experience in this then I do. However,
this problem only began when I upgraded the server to 2.1.118 from 2.0.35.
Considering that I know the source, and their reluctance to change their
side, what recourse do I have, other then dropping back to 2.0.35? (I
know that dropping back to 2.0.35 is a minimalistic approach, as is trying
to make my side deaf, dumb and blind... So please, no flames from the
peanut gallery *grin*) Never-the-less, thanks. :)


On Tue, 1 Sep 1998, Alan Cox wrote:

> And is faulty or misconfigured. Basically the reporting
> machine got an icmp message back complaining about a broadcast frame.
> You are not allowed to send icmp replies to broadcast frames. Its strictly
> forbidden in the RFCs. The normal cause of this is misconfiguration of
> broadcast addresses between the two nodes, although even then on ethernet
> the is probably breaking RFC requirements since it should
> have been a mac layer broadcast too

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.077 / U:1.728 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site