>
> > natd chokes on the latest windoze worms and I have implemented some DoS
> > prevention/worm protection in ipnat but I'm seeing this memory leak
without
> > my improvements there at all.
> >
> > If it's in the kernel, ipnat is kept under control when natd would
normally
> > be sucking the
ntrol when natd would normally
be sucking the CPU dry and preventing things like remote logins, very
slugish updates, etc...
and others I don't particularly want to go into at the moment.
vec
- Original Message -
From: "marcos" <[EMAIL PROTECTED]>
To: "Vector
ntrol when natd would normally
be sucking the CPU dry and preventing things like remote logins, very
slugish updates, etc...
and others I won't go into at the moment.
vec
- Original Message -
From: "marcos" <[EMAIL PROTECTED]>
To: "Vector" <[EMAIL PRO
I was using ipfw and natd but I wanted to move nat into the kernel so I
recompiled with ipfilter and ipnat. Now, after terminating natd, and
setting up ipnat rules in /etc/ipnat.rules, I see memory increase at a rate
of just under 1MB per minutes. Has anyone else seen a memory leak in ipnat
or ip
What happened to ipintrq? I know it is now defined in ip_input.c...problem
is I'm trying to port a driver to 5.1. The files are in a subdirectory in
/usr/src/sys/dev and in order to get it to compile, I've declared it like
this:
extern struct ifqueue ipintrq;
But upon linking, I get unresolved s
