Re: how to debug non-working hole in nat

2012-01-03 Thread Randy Bush
>> ignore. i sorted it. > Too late, sucked in .. diff from prior config might be bone enough? i had forgotten to remove the nat enable from /etc/ppp/ppp.conf when i moved to natd. randy ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/

Re: how to debug non-working hole in nat

2012-01-03 Thread Ian Smith
On Tue, 3 Jan 2012 17:52:53 +0900, Randy Bush wrote: > ignore. i sorted it. Too late, sucked in .. diff from prior config might be bone enough? cheers, Ian ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net

Re: how to debug non-working hole in nat

2012-01-03 Thread Paul A. Procacci
> add divert natd all from any to any via bridge0 This nat's all internal traffic on your lan. You probably don't want this. I'd place the nat on the tun0 interface. Which leads me to If you machine receives a syn from the tun0 interface, what firewall rule is in place to redirect t

Re: how to debug non-working hole in nat

2012-01-03 Thread Randy Bush
ignore. i sorted it. randy ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"