Re: ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0

2011-06-25 Thread Ian Smith
On Thu, 23 Jun 2011, umage wrote: > Some points: > 1) I did use the handbook as reference, and my ruleset mimics the layout used > there. Excuse the late response, I've been away. The best reference, apart from ipfw(8), is /etc/rc.firewall. 'Nuff said. > 2) Handbook uses divert natd, whic

Re: ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0

2011-06-23 Thread umage
Some points: 1) I did use the handbook as reference, and my ruleset mimics the layout used there. 2) Handbook uses divert natd, which I used until I switched to the kernel nat approach. 3) I did not find any concrete examples of ipfw nat rule usage, so I'm using them the old natd way. I did s

Re: ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0

2011-06-23 Thread Ian Smith
In freebsd-questions Digest, Vol 368, Issue 6, Message: 21 On Tue, 21 Jun 2011 20:16:32 +0200 umage wrote: > Hi, I'm an ipfw user that finally got the opportunity to set up NAT on > an interface with a public IP. I was doing some multi-homing experiments > using ipfw fwd combined with outbound

ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0

2011-06-21 Thread umage
Hi, I'm an ipfw user that finally got the opportunity to set up NAT on an interface with a public IP. I was doing some multi-homing experiments using ipfw fwd combined with outbound ipfw nat - and since I needed to run both, and both immediately ended ipfw ruleset execution, I had to turn off net.i