Messages in this thread | | | From | kuznet@ms2 ... | Subject | Re: Token Ring Bug (Broadcast and Multicast address check) | Date | Thu, 6 May 1999 20:15:02 +0400 (MSK DST) |
| |
Hello!
> byte with 0x80 and not 1 when checking for a broadcast or multicast > address.
Excellent! This puzzle bedevils me for year or so... And nobody was able to give any intelligible answer 8)
Let me one question to complete the picture: the same bit of tr source address is TR_RII. Is it true? Do another magic bits exist?
Also, could you write tr_header_parse routine to fetch source address? (Look at eth_header_parse)
BTW, could you send me piece of "tcpdump -p -e" with samples of multicast packets originated by another hosts?
> This bug can be reproduced by setting an LAA of 4fffffffffff which is a > valid > single node address on TR. We get neighbour table overflow messages > from the > kernel
I do not understand this. Even if it is misinterpreted, neigh table overflow is not explained yet.
Alexey
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |