Date: Fri, 18 Jun 2004 11:49:15 -0400 From: "JJB" <Barbish3@adelphia.net> To: "Robert Downes" <nullentropy@lineone.net>, <freebsd-ipfw@freebsd.org> Subject: RE: Blocked outbound traffic - what is it? Message-ID: <MIEPLLIBMLEEABPDBIEGOECIGDAA.Barbish3@adelphia.net> In-Reply-To: <40D301EA.3080606@lineone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
you may be reading the blocked log records wrong. Post complete content of your rules set plus ipfw log content for people to look at -----Original Message----- From: owner-freebsd-ipfw@freebsd.org [mailto:owner-freebsd-ipfw@freebsd.org]On Behalf Of Robert Downes Sent: Friday, June 18, 2004 10:54 AM To: freebsd-ipfw@freebsd.org Subject: Blocked outbound traffic - what is it? Having set up IPFW for NAT + stateful rules (as posted to this list recently, using skipto rules), my firewall setup seems to be doing a good job. GRC.COM reports all service ports as stealthed, and I seem to have no problem browsing web pages, checking mail, etc. But calling ` /var/log/security | grep out` gives a lot of reports of blocked outbound traffic to port 80 on legitimate websites. And occassionally to port 110 on legitimate mail servers. Seeing as I'm not having a problem with web browsing, and my mail *seems* to be collected without complaint from the client, why is so much outbound traffic being blocked? What are these packets doing to offend the IPFW ruleset? -- Bob _______________________________________________ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGOECIGDAA.Barbish3>