Date: Thu, 21 Feb 2002 08:49:55 -0800 From: "Crist J. Clark" <cjc@FreeBSD.ORG> To: Simon J Mudd <sjmudd@pobox.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ipfw and getting the interface logged Message-ID: <20020221084955.C48401@blossom.cjclark.org> In-Reply-To: <Pine.LNX.4.44.0202211714050.30303-100000@phoenix.ea4els.ampr.org>; from sjmudd@pobox.com on Thu, Feb 21, 2002 at 05:18:59PM %2B0100 References: <Pine.LNX.4.44.0202211714050.30303-100000@phoenix.ea4els.ampr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 21, 2002 at 05:18:59PM +0100, Simon J Mudd wrote:
> Hello,
>
> I'm running 4.5-STABLE with ipfw and having trouble with my firewall
> rules. However they are probably my own doing.
>
> Via syslog I see messages of the type:
>
> Feb 21 16:13:56 unicorn /kernel: Connection attempt to TCP 44.133.228.2:6000 from 44.133.228.5:2187
> Feb 21 16:13:57 unicorn /kernel: Connection attempt to TCP 44.133.228.2:6000 from 44.133.228.5:2188
Which are from net.inet.tcp.log_in_vain being set, not from ipfw(8).
> Which I think my rules should allow:
>
> ${fwcmd} add pass all from ${inet} to ${inet} via ${iif}
And they are letting it through if they are being logged in vain.
> where
>
> # set these to your inside interface network and netmask and ip
> iif="ed0"
> inet="44.133.228.0/26"
> iip="44.133.228.2"
>
> How can I get syslog to log more information such as at least the
> interface over which the traffic is arriving?
If ipfw(8) was logging the packets, the interface information would be
there.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020221084955.C48401>