"John W. O'Brien" writes:
Hi John,
> I haven't done the mind meld with "reverse" yet.
> Could you comment on why you need to operate in a reversed NAT
> environment?
In this particular case, this is a test lab.
The purpose of this kind of setup is the following :
- administrator of the remote
On 3/7/14 1:40 PM, Eric Masson wrote:
> Philipp Schmid writes:
>
> Hi Philipp,
>
>> FreeBSD 10 seems to have problems with IPSec and filtering/nat.
>> Maybe your problem is related to:
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=185876
>
> I've rebuilt a kernel with the last patch ava
Philipp Schmid writes:
Hi Philipp,
> FreeBSD 10 seems to have problems with IPSec and filtering/nat.
> Maybe your problem is related to:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=185876
I've rebuilt a kernel with the last patch available in the PR.
It doesn't work (return nat rule in
Philipp Schmid writes:
Hi Philipp,
> FreeBSD 10 seems to have problems with IPSec and filtering/nat.
> Maybe your problem is related to:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=185876
I'll try the patch enclosed asap (overwhelmed by paid work these days).
Regards
Éric
--
voila
"John W. O'Brien" writes:
Hi John,
> You also need to perform NAT processing on the traffic that returns to
> gateway1 from gateway2.
>
> $cmd add 200 nat 100 all from 192.168.21.0/24 to 172.16.0.1
I've been privately told about the return rule (I'm used to pf not
ipfw), but no luck.
Seems
Hi Eric,
FreeBSD 10 seems to have problems with IPSec and filtering/nat.
Maybe your problem is related to:
http://www.freebsd.org/cgi/query-pr.cgi?pr=185876
- Philipp
On 07 Mar 2014, at 03:48, John W. O'Brien wrote:
> Hi Eric,
>
> On 1/25/14 10:28 AM, Eric Masson wrote:
>> Hi,
>>
>
Hi Eric,
On 1/25/14 10:28 AM, Eric Masson wrote:
> Hi,
>
> I've setup a lab to experiment nat before ipsec scenario.
> Architecture :
> - 3 host only interfaces have been set up on the host
> - 4 FreeBSD10 guests have been set up :
> - 2 clients connected to their respective gateways via dedica
