Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Let me explain a context where i faced this problem.
Some body in a private network( a branch office ) with private ip address is going to communicate with the peer system which is located in another private network ( a head office) with its private ip address itself. In this scenario, i need to offer security for the packets through ipsec.
So, In this context, whether my packets in one branch is natted by the NAT router or not. Because, i heard that IPsec doesn't support NATing concept. Then how does my packet with IPsec security goes to that peer system.
ok, well ipsec as a protocol doesn't use port numbers, unlike tcp or udp as such it is not possible to easily nat an ipsec packet as it traverses a device like an adsl firewall, which naturally nats traffic from an internal subnet to the single public ip. to get around this, many ipsec implementations will allow the option of adding a dummy tcp or udp header, allowing for an arbitrary port number to be added. this then can be used within a nat table to manage the connections.
in your scenario though, you have an ipsec tunnel between two edge devices at the sites? from there, there's not going to actually be any natting taking place, as the peers themselves will be the public addresses. if there's a single vpn termination point behind the edge device, then you would conventionally just forward all ipsec traffic to that internal device.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.