[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: update: net/nmap
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: update: net/nmap
- From: Chris Kuethe <chris_(_dot_)_kuethe_(_at_)_gmail_(_dot_)_com>
- Date: Tue, 20 Sep 2005 16:36:08 -0600
- Reply-to: chris_(_dot_)_kuethe_(_at_)_gmail_(_dot_)_com
On 9/20/05, Okan Demirmen <okan_(_at_)_demirmen_(_dot_)_com> wrote:
> yea, so turn off pf(4), or more specifically, state creation, especially
> when you are doing syn-scans (default when done as root).
yes, pf was turned off on both the source and destination machine and
they were on the same dumb switch. Not that it should matter if Nmap
is forging frames on the wire with bpf...
> which archs did it break for you?
> on a side note, i recently found that state creation on amd64 and
> sparc64 seem to top out around 140, but on i386, i can create states up
> to the configured max. however, none of this is highly scientific. i
> still need to isolate more to figure it out.
I'll try my zaurus and see... offhand I seem to recall being able to
generate lots of states...
GDB has a 'break' feature; why doesn't it have 'fix' too?