Date: Fri, 18 Aug 2000 11:57:46 +0100 From: Mike Bristow <mike@urgle.com> To: "O. Hartmann" <ohartman@ipamzlx.physik.uni-mainz.de> Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SAMBA and IP filtering Message-ID: <20000818115746.A35276@lindt.urgle.com> In-Reply-To: <Pine.BSF.4.10.10008181157370.742-100000@ipamzlx.physik.uni-mainz.de>; from ohartman@ipamzlx.physik.uni-mainz.de on Fri, Aug 18, 2000 at 12:03:24PM %2B0200 References: <Pine.BSF.4.10.10008181157370.742-100000@ipamzlx.physik.uni-mainz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 18, 2000 at 12:03:24PM +0200, O. Hartmann wrote: > Is anybody out here who has IP filtering (IPFIREWALL) on and has still > full SAMBA access via NT clients? > I have the following problem: IP filtering is enabled and working well on > our FBSD 4.1 box running samba. One of the first rules is to allow all traffic > from and to the server via the local network, that means no restrictions. With > many services this runs well - but not for SAMBA! compile your kernel with IPFIREWALL_VERBOSE and add a "log" keyword to all of the reject rules (duplicating the default rule if neccessary with a log keyword in it) and then see what the rule is that drops the packets, what the packets are, and then (of course) allowing them. -- Mike Bristow, seebitwopie 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?20000818115746.A35276>