Date: Thu, 8 May 2003 14:50:42 +0100 From: Philip Payne <philip.payne@uk.mci.com> To: 'Wayne Swart' <fixx@fixx.co.za>, FreeBSD Mailing list <freebsd-questions@freebsd.org> Subject: RE: ipfw + natd Message-ID: <36D04A8168B2D41182250008C7E6F8780374F6D4@ukcamexch2.cbg.uk.corp.eu.uu.net>
next in thread | raw e-mail | index | archive | help
Hi, > -----Original Message----- > From: Wayne Swart [mailto:fixx@fixx.co.za] > Sent: 08 May 2003 13:31 > To: FreeBSD Mailing list > Subject: ipfw + natd > > > Lo > > I am running FreeBSD4.8-RELEASE and have a problem with ipfw and natd. > > the two interfaces (dc0 and dc1) have the following ip setup. > > dc1 ip: 10.10.10.1 > dc0 ip: 196.x.x.x > > now i can't do any requests through my box to "the outside" > anymore, since > i added a default to deny rule. > > i use the following ipfw rules for the nat, but it does not > seem to have > any impact on the requests that has to go through it. > > ipfw add divert natd all from any to any via dc0 out keep-state > ipfw add allow all from 10.10.10.0/24 to any via dc0 out keep-state > ipfw add allow all from 10.10.10.0/24 to any via dc1 in keep-state > > is there an easier way to troubleshoot this? > > any help is appreciated... Generally speaking, a good way to start is to switch on logging on every rule and also include a specific deny all rule that logs at the end of your rules list. That way, you guarantee picking up what traffic is being dropped and by what rule.... therefore , you can start to see what useful traffic the previous default allow was letting through and allow it specifically. If your log is too noisy you'll either need to manipulate the output using grep -v or perl.... or an alternative is to start introducing more specific rules that do not log to filter out the noise. Once you're sorted, switch off the logging. Hope that helps. Phil.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36D04A8168B2D41182250008C7E6F8780374F6D4>