On Thu, 1 Mar 2001, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 02, 2001 at 01:21:07AM +0100, J.R. de Jong escreveu: > > Anyway, our main server died (it wasn't me!) which is another reason to > > wait for tomorrow to get consistent results (the other being that I'm too > > tired right now to run the right kernel, leading me to send you wrong data > > before). > > Ok, so please test this patch, that has that small damn bug (!= should be > ==) fixed, I think it'll cure the bug, when you confirm that I'll submit it > for inclusion, ok? > Congrats, I'm not broadcasting anymore!! I tried your patch on 2.4.2-ac7. Now I only get normal arp reply messages in tcpdump. Also, in iptraf I'm only sending out 21 non-IP (ipx) packages in five minutes, exactly in correspondence with tcpdump output. I guess it's not an issue anymore to put any logs on http and I think you can safely submit the patch. >> 000475 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 >> type 0x14 (propogated Client-NetBios) >> 000476 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 >> type 0x14 (propogated Client-NetBios) > Who's that? It is really often. I don't know... it doesn't seem to be the main server. Unfortunately I don't have access to the local database of MAC adresses. It does show up in slist however. All I know is that I'm REALLY getting a lot of IPX broadcast traffic. Even more than the TCP/UDP traffic we're generating in our own linux network segment. And that's just IPX broadcasts... the rest is supposed to be filtered by our switch. These IT guys have a very loud windows network on their hands. Maybe I'll complain to THEM for a change ;) >> 00:29:21.754475 0:d0:b7:18:62:e3 > Broadcast sap e0 ui/C >> >>> Unknown IPX Data: (51 bytes) >> [000] FF FF 00 66 01 14 00 1D 80 22 FF FF FF FF FF FF ...f.... ."...... >> [010] 05 55 00 1D 80 22 00 00 C0 B8 E0 DC 05 55 00 1D .U...".. .....U.. >> [020] 80 22 00 01 00 00 00 1E 06 01 53 4E 41 50 50 59 ."...... ..SNAPPY >> [030] 02 02 06 ... >> -- >But WHY you are sending this packet? It must came here from somewhere... Beats me.. probably tcpdump isn't showing us everything. Is this an artifact of the (intrfc != ifcs) bug? Anyway, the spamming bug seems to have been solved. Good work =) - Johan de Jong. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
