On Thu, 26 Jul 2001, Stefan Laudat wrote: > Believe it or not, I got a OpenBSD-2.9 current hanged up out there. > I'll test further systems. What amazed me was different types of > system reaction with different drivers at different links. Maybe there's something wrong with your approach or test environment. As long as there's no comsat or any other service running on this port, and you do not actually trash your link layer, there's absolutely no reason for this to succeed. It is normal, system-generated UDP packet, and apparently, as expected, has no impact on boxes I can reach from there... -- _____________________________________________________ Michal Zalewski [[EMAIL PROTECTED]] [security] [http://lcamtuf.coredump.cx] <=-=> bash$ :(){ :|:&};: =-=> Did you know that clones never use mirrors? <=-=
- UDP packet handling weird behaviour of various operat... Stefan Laudat
- Re: UDP packet handling weird behaviour of vario... Michal Zalewski
- Re: UDP packet handling weird behaviour of v... Kevin Day
- Re: UDP packet handling weird behaviour of v... Cade Cairns
- Re: UDP packet handling weird behaviour ... Michal Zalewski
- Re: UDP packet handling weird behaviour of v... Stefan Laudat
- Re: UDP packet handling weird behaviour ... Michal Zalewski
- Re: UDP packet handling weird behaviour of v... Stefan Laudat
- Re: UDP packet handling weird behaviour ... Niels Bakker
- RE: UDP packet handling weird behaviour of v... David LeBlanc
- Re: UDP packet handling weird behaviour of v... Radu-Adrian Feurdean
- Re: UDP packet handling weird behaviour of vario... trop
- Re: UDP packet handling weird behaviour of vario... Paul Sack
- Re: UDP packet handling weird behaviour of v... Stefan Laudat
- Re: UDP packet handling weird behaviour ... Sean Hunter
- Re: UDP packet handling weird behavi... Sean Hunter
- Re: UDP packet handling weird behaviour ... Adrian Chadd
