What is the correct iptables rule when NATing multiple private subnets?

Jose Mendez asked:

I have a Centos minimal 6.5 acting as a router. eth0 is connected to a Cisco switch trunk port, allowing VLANs 200-213.

I have several VLAN interfaces just as this link suggests:


And have IPv4 forwarding, so all my network devices from any of the networks 200-213 can communicate with each other using this linux box as their router.

Problem is, I need them to access the Internet, so I added the following rule:

iptables -t nat -A POSTROUTING -s -j SNAT --to is the “outside” address. This works fine, devices connected to the internal networks can ping Intertnet addresses BUT, they stop being able to talk to each other across subnets, so can ping, but can’t talk to

As soon as I do a service iptables restart to remove the rule, I can start talking across internal subnets again.

What would be the correct way to set up NAT for multiple private subnets? Or maybe the correct way to set up forwarding?

My answer:

You also need to specify in your firewall rule the destination interface for the traffic to be NATted. Otherwise it will just attempt to NAT everything, and as you’ve seen, that doesn’t work. You should only be NATing traffic bound for the outside world.

So, let’s say that your default route for all your Internet-bound traffic goes out VLAN 200 (since you didn’t specify), a VLAN dedicated for external traffic. In that case, you’ll add -o eth0.200 to your firewall rule.

iptables -t nat -A POSTROUTING -s -o eth0.200 -j SNAT --to

View the full question and any other answers on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.