Re: NAT Port Forward problem in a not so simple network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Grant Taylor a écrit :
On 04/15/08 07:15, whiplash wrote:

Of course. A possible solution is to SNAT packets exiting from 192.168.0.11 with destination 192.168.0.2.

*nod*

However, SNATing will have the possibly undesirable side effect of making the traffic appear to be from the machine that is doing the SNATing.

It does not matter so much as, according to the packet trace, Cisco1 appears to SNAT incoming connections forwarded to HPpro1 anyway. So all you get in the logs is HPpro1's address instead of Cisco1's...
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux