Ok, quick check: The broadcast packets you are seeing, are you sure they're not ARP? Secondly, only TCP has SYN and ACK packets, so talking about SYN for UDP doesn't make sense. The easiest thing would be to check the destination MAC address of the SYN-ACK packet and check that it actually matches the MAC address of your machine. It could be that someone's ARP cache is taking a while to notice that you changed your MAC address. Is the machine responding to your UDP packets that same as the one you're testing TCP against? Hope this helps, On Wed, Sep 08, 2004 at 04:15:31PM -0300, Eduardo Trápani wrote: > Ok, I didn't know that TCP had an explicit check for *MAC* broadcast > addresses. Do you happen to know where the check is taking place? I've > checked ethernet, ip and tcp (under ipv4) but I cannot find it. I'd like > to remove it and see if it works. > > I can understand that TCP does not accept the broadcast. What puzzles me > is the fact that UDP does accept it for, say, name resolution. Shouldn't > UDP also reject an answer packet going to a valid address/port pair if the > underlying ethernet destination address is FF:...:FF? > > Or maybe there is a valid use for such a packet, I don't know. > > Is TCP digging into the packet to reject a MAC broadcast addressed packet? > Or is it IP who's doing that before the internal routing? > > Eduardo. > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
pgpzo36pzYNmm.pgp
Description: PGP signature
