On Sat, Nov 19, 2011 at 3:22 AM, Guy Tetruashvyly wrote:
>
> After we've dealt with not touching traffic we shouldn't by the NAT
> engine, now we're talking about something else:
> recognizing GRE traffic - and understanding where it SHOULD go,
> based on the characteristics of the GRE packets th
After we've dealt with not touching traffic
we shouldn't by the NAT engine, now we're talking about something
else:
recognizing GRE traffic - and understanding where it SHOULD go,
based on the characteristics of the GRE packets themselves...
my next q
On Fri, Nov 18, 2011 at 1:45 PM, Guy Tetruashvyly wrote:
> I understand from the NAT rule that you expect the traffic to come FROM
> eth0 - i.e. this is the interface connected to "INTERNET" (how? do you have
> an additional home/NAT router there?) - as otherwise it wouldn't do any NAT
> work fo
I understand from the NAT rule that you
expect the traffic to come FROM eth0 - i.e. this is the
interface connected to "INTERNET" (how? do you have an
additional home/NAT router there?) - as otherwise it wouldn't do
any NAT work for traffic coming f
2011/11/18 Guy Tetruashvyly
> Greetings,
> this is an issue I've been struggling with for months now, didn't even
> make small headway .
>
> Scheme :
> LANLinux_X86_ROUTERINTERNET , so far, very simple.
>
> I have a PPTP server that's on the LAN, and has a LAN IP address (only) .
> The R
Greetings,
this is an issue I've been struggling with for months now, didn't
even make small headway .
Scheme :
LANLinux_X86_ROUTERINTERNET , so far, very simple.
I have a PPTP server that's on the LAN, and has a LAN IP address
(only) .
The
