Re: Routing return NAT traffic based on interface

2012-12-05 Thread Peter McAlpine
Ermal this looks to be working perfectly. Thank you so much! -Peter On Wed, Dec 5, 2012 at 10:21 AM, Ermal Luçi wrote: > > > > On Wed, Dec 5, 2012 at 3:51 PM, Peter McAlpine wrote: > >> First off, thanks for all the suggestions from both of you. My email >> filters were messed up causing me to

Re: Routing return NAT traffic based on interface

2012-12-05 Thread Ermal Luçi
On Wed, Dec 5, 2012 at 3:51 PM, Peter McAlpine wrote: > First off, thanks for all the suggestions from both of you. My email > filters were messed up causing me to miss your replies. > > On 19 November 2012 18:56, David DeSimone wrote: > > If I understand the poster's problem, it is that there c

Re: Routing return NAT traffic based on interface

2012-12-05 Thread Peter McAlpine
First off, thanks for all the suggestions from both of you. My email filters were messed up causing me to miss your replies. On 19 November 2012 18:56, David DeSimone wrote: > If I understand the poster's problem, it is that there could be whole > worlds of other networks behind $int_if, and he i

Re: Routing return NAT traffic based on interface

2012-11-19 Thread Kevin Wilcox
On 19 November 2012 18:56, David DeSimone wrote: > This doesn't seem right, because even traffic coming in via the external > interface will have its target IP changed to be the router, even if > it is destined for some other place. Previously you were using "from > $int_if:network" to prevent t

Re: Routing return NAT traffic based on interface

2012-11-19 Thread David DeSimone
Kevin Wilcox wrote: > > On Nov 19, 2012 5:54 PM, "Kevin Wilcox" wrote: > > > It is. The "pass in" rule I used in my example assumes the inside > > interface and the other devices it talks to are in the same network. > > Correction, the "pass in" and "nat" rules, not just the pass. They > both ha

Re: Routing return NAT traffic based on interface

2012-11-19 Thread Kevin Wilcox
On Nov 19, 2012 5:54 PM, "Kevin Wilcox" wrote: > It is. The "pass in" rule I used in my example assumes the inside interface and the other devices it talks to are in the same network. Correction, the "pass in" and "nat" rules, not just the pass. They both have to be modified. kmw __

Re: Routing return NAT traffic based on interface

2012-11-19 Thread Kevin Wilcox
On Nov 19, 2012 3:12 PM, "Peter McAlpine" wrote: > > Thanks for your reply. I've tried the configuration you suggested but > it's providing the same issue I was encountering before. > > My goal is to route all traffic from the tunnel out the external > interface nat'ing it on the way out. Any traf

Re: Routing return NAT traffic based on interface

2012-11-19 Thread Peter McAlpine
Thanks for your reply. I've tried the configuration you suggested but it's providing the same issue I was encountering before. My goal is to route all traffic from the tunnel out the external interface nat'ing it on the way out. Any traffic coming in on the external interface should be un-nat'd (i

Re: Routing return NAT traffic based on interface

2012-11-16 Thread Kevin Wilcox
On 16 November 2012 09:40, Peter McAlpine wrote: > data_if = "tap3" > ext_if = "em0" > set skip on lo0 > nat on $ext_if from !$ext_if:network to any -> ($ext_if) > pass in on $ext_if route-to $data_if from any to !$ext_if:network > The issue I'm having is that the 'pass' rule is not being matche