Date: Thu, 18 Oct 2007 08:39:56 -0700 From: "Michael K. Smith - Adhost" <mksmith@adhost.com> To: "Nikos Vassiliadis" <nvass@teledomenet.gr>, <freebsd-questions@freebsd.org> Subject: RE: Odd PF Denied Message Message-ID: <17838240D9A5544AAA5FF95F8D5203160297F7BC@ad-exh01.adhost.lan> In-Reply-To: <200710181829.48220.nvass@teledomenet.gr> References: <17838240D9A5544AAA5FF95F8D5203160297F7B3@ad-exh01.adhost.lan> <200710181829.48220.nvass@teledomenet.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Nikos: > -----Original Message----- > From: Nikos Vassiliadis [mailto:nvass@teledomenet.gr] > Sent: Thursday, October 18, 2007 9:30 AM > To: freebsd-questions@freebsd.org > Cc: Michael K. Smith - Adhost > Subject: Re: Odd PF Denied Message >=20 > On Thursday 18 October 2007 17:59:49 Michael K. Smith - Adhost wrote: > > Hello All: > > > > We're getting a ton of these. > > > > +Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:52655 > flags:0x02 >=20 > This doesn't look like a pf(4) message. This looks like > sysctl net.inet.tcp.log_in_vain is 1. It logs every connection > attempt to a non-listening TCP port. >=20 > > > > We've basically allowed all traffic to and from 127.0.0.1 in our > > ruleset, but nothing seems to work. Does anyone have a magic bullet > to > > make this go away? >=20 > Yes, set the afore-mentioned sysctl to 0. Thank you for the clue! We are using log in vain as part of our security logging for this particular box, but this is the only message I've ever seen so I'm not sure it's really needed. Regards, Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17838240D9A5544AAA5FF95F8D5203160297F7BC>