Date: Tue, 13 Mar 2001 09:37:32 -0700 From: Bradley Senff <brad@iBizcorp.com> To: "'freebsd-ipfw@freebsd.org'" <freebsd-ipfw@FreeBSD.ORG> Subject: RE: IPFW and forwarding from one interface to another (LONG) Message-ID: <40DFA2708D54D41193F20001025665B61ABBFF@MAIL>
next in thread | raw e-mail | index | archive | help
Nick, et al. I didn't see that the fwd was for outbound only. I have adjusted my filters to reflect that concept, and all is well. To summarize: To make this work, I went to the uplink port (fxp0), and put in a filter that was basically "add xxxx fwd 5.5.5.5 ip from 1.1.1.0/24 to any out fxp0" ... The only curiousity I have left is whether that forces the packets back through the firewall, since it will be going "out" a different port after that rule... Thoughts? Thank you for the kick in the head. :-) -brad -----Original Message----- From: Nick Rogness [mailto:nick@rogness.net] Sent: Tuesday, March 06, 2001 12:27 PM To: Bradley Senff Cc: 'freebsd-ipfw@freebsd.org' Subject: Re: IPFW and forwarding from one interface to another (LONG) On Tue, 6 Mar 2001, Bradley Senff wrote: [snip] > # HERE IS what should be FORCING the traffic back through dc0 > # but it isn't! > # I have also tried to use 5.5.5.6/30 as well, but no dice. > add 11000 fwd 5.5.5.5 ip from 1.1.1.0/24 to any via in dc1 ipfw fwd only works on outbound traffic. Nick Rogness <nick@rogness.net> - Keep on routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40DFA2708D54D41193F20001025665B61ABBFF>