Em Fri, Mar 02, 2001 at 12:03:14AM +0100, Petr Vandrovec escreveu: > On Thu, Mar 01, 2001 at 11:43:24PM +0100, J.R. de Jong wrote: > > > > 000049 802.2 from 001D8022:0000C0B8E0DC:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > 000050 802.2 from 001D8022:0000C0B8E0DC:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > Nobody replicated these two... > > > 000245 802.2 from 001D8022:00E02929131C:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > 000246 802.2 from 001D8022:00E02929131C:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > Someone else... No dups... > > > 000326 802.2 from 001D8022:0000C074A9CE:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > 000327 802.2 from 001D8022:0000C074A9CE:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > No dups... > > > 000361 802.2 from 001D8022:00E0293DC0D1:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > 000362 802.2 from 001D8022:00E0293DC0D1:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > No dups... > > > 000465 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > 000466 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > > 000471 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > 000472 802.2 from 001D8022:00E0294410EF:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > > 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. > > > 000489 802.2 from 001D8022:00E02905B305:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > 000490 802.2 from 001D8022:00E02905B305:0455 to 001D8022:FFFFFFFFFFFF:0455 > > type 0x14 (propogated Client-NetBios) > > 000491 802.2 from 001D8022:00E02905B305:0553 to 001D8022:FFFFFFFFFFFF:0553 > > type 0x14 (propogated Client-NetBios) > > 000492 802.2 from 001D8022:00E02905B305:0553 to 001D8022:FFFFFFFFFFFF:0553 > > type 0x14 (propogated Client-NetBios) > > Innocent... > > > 000496 802.2 from 001D8022:00E02909BB72:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > 000497 802.2 from 001D8022:00E02909BB72:0555 to 001D8022:FFFFFFFFFFFF:0555 > > type 0x14 (propogated Client-NetBios) > > ... same below. Again no spamming, although maybe you should think > about some other policy for Windows network, and for some IPX games. Question, what version is this? 2.4.2-pre7 + my latest patch? If this is so it seems that I can safely submit this to davem for inclusion? 8) - Arnaldo PS.: I'm implementing the sysctl right now, as it seems that the spamming case is solved, I'll transform the PPROP if into a function and only call it when the type = 14, if it returns some value, I'll drop the packet right away, if not, normal processing follows, and I'll do the same for the case when we discover the interface netnum (/* See if we should update our network number */), that way ipxitf_rcv will be more clear, with exceptions separated into functions, that way we'll get even better icaching 8) Comments? - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
