____________________________ ____________________________ | Host | | Client | | Public IP: 188.8.131.52 | | | | Internal IP: 10.0.3.1 | <---------> | Internal IP: 10.0.3.192 | ---------------------------- ----------------------------
- Host with public IP (=184.108.40.206)
- Linux Container (LXC), called client in the rest of the post, started with
vethnetwork option on which a webserver is running.
- On the host, the firewall is configured with
ufwand the respective ports are opened and forwarded to the client, this works.
iptables port forwarding in the
# nat Table rules *nat :PREROUTING ACCEPT [0:0] -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.3.192:80 -A PREROUTING -i eth0 -p tcp --dport 443 -j DNAT --to-destination 10.0.3.192:443 # don't delete the 'COMMIT' line or these rules won't be processed COMMIT
/etc/network/interfaces on host:
# The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 220.127.116.11 netmask 255.255.255.0 network 18.104.22.168 broadcast 22.214.171.124 gateway 126.96.36.199 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 188.8.131.52
/etc/network/interfaces on client:
# The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.3.192 netmask 255.255.255.0 gateway 10.0.3.1 broadcast 10.0.3.255
Port scan from client
Starting Nmap 5.21 ( http://nmap.org ) at 2014-04-18 18:46 CEST Nmap scan report for 184.108.40.206 Host is up (0.00011s latency). PORT STATE SERVICE 80/tcp closed http 443/tcp closed https
Port scan from "outside"
Starting Nmap 6.40 ( http://nmap.org ) at 2014-04-18 19:54 CEST Nmap scan report for 220.127.116.11 Host is up (0.41s latency). PORT STATE SERVICE 80/tcp open http 443/tcp open https Nmap done: 1 IP address (1 host up) scanned in 1.28 seconds
$ iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination DNAT tcp -- anywhere anywhere tcp dpt:http to:10.0.3.192:80 DNAT tcp -- anywhere anywhere tcp dpt:https to:10.0.3.192:443 DNAT tcp -- anywhere anywhere tcp dpt:43211 to:10.0.3.192:22 DNAT tcp -- anywhere anywhere tcp dpt:http-alt to:10.0.3.192:8080 Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE tcp -- anywhere 10.0.3.192 tcp dpt:http MASQUERADE tcp -- anywhere 10.0.3.192 tcp dpt:https MASQUERADE all -- 10.0.3.0/24 !10.0.3.0/24
- Ubuntu 12.04 (host as well as client)
- LXC (1.0.3-0ubuntu1~ubuntu12.04.1~ppa1)
I want to access the webserver on port 80 on the client from the client itself over the public IP, e.g.
$ curl http://18.104.22.168 curl: (7) couldn't connect to host
should give the same result as
$ curl http://10.0.3.192 <html>.....
$ ping 22.214.171.124 from the client inside the private network works though.
What I tried
I see that this problem is very much related to the so called Hairpin NAT / Loopback NAT, though I could not configure the masquerading with the following rules, such that it works (in
/etc/ufw/before.rules after the
# nat Table rules *nat :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth0 -d 10.0.3.192 -p tcp --dport 80 -j MASQUERADE -A POSTROUTING -o eth0 -d 10.0.3.192 -p tcp --dport 443 -j MASQUERADE # don't delete the 'COMMIT' line or these nat table rules won't be processed COMMIT
My guess to the solution is that the bridged network or just my incapability of adapting the MASQUERADE rule correctly to my setup is the problem. Any suggestions and comments, also to the setup in general are appreciated.
Related questions or articles, but not helping
- LXC networking with public IP
- About different network modes of LXC: http://containerops.org/2013/11/19/lxc-networking/
- Using NAT for container with private IPs (explicitly written that it will not work from inside the private network): https://openvz.org/Using_NAT_for_container_with_private_IPs
- Clean LXC + NAT configuration: https://coderwall.com/p/k0gutq
- iptables - how to access local server using external ip (disadvise of doing so, suggest setting up DNS or editing host file, but based on FQDN): http://www.tomshardware.co.uk/forum/12532-42-iptables-access-local-server-external
- Is NAT Loopback on my router a security problem? (Gives SNAT rule,: http://security.stackexchange.com/questions/16343/is-nat-loopback-on-my-router-a-security-problem
- NAT loopback using iptables: http://for-invent.com/nat-loopback-using-iptables/