We have a test setup where several components are connected to their own network. This network has the the following address: Most, if not all, of the components have static IP addresses, as they are defined by several standards and documents.

Our company network is separated from this machine network for obvious reasons, yet for different testing scenarios, certain components from within the machine network must be able to communicate with the Internet.


For our setup, we have the machine network connected to a RaspberryPi 4 (8GiB) via a USB Ethernet adapter (10/100/1000T) and the built-in network adapter connected to the company network with access to WAN.

The idea is, that the Pi masquerades the traffic coming from to <anywhere>.

The setup has worked for quite a long time, but recently it has simply stopped routing the traffic. I'm at a loss as to why.

IP Rules

We have a script that sets up the iptables rules and this has previously worked up until the weekend (this past weekend):




# enable ip forwarding in the kernel
echo 'Enabling Kernel IP forwarding...'
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
echo 'Flushing rules and deleting existing chains...'

# enable masquerading to allow LAN internet access
echo 'Enabling IP Masquerading and other rules...'



echo 'Done.'

The resulting iptables rules look like this:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             ctstate NEW,RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere             state NEW,RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             state NEW,RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination    

As far as I can tell, this should route all the traffic from eth1 (LAN) to eth0 (WAN) - which is exactly what it has previously done. Yet evidently, when I try to ping Google's DNS, I get the following:

ping -I eth0
PING ( 56 data bytes
--- ping statistics ---
1317 packets transmitted, 0 packets received, 100% packet loss

Any help on the matter would be much appreciated. Without packet forwarding/masquerading, our most critical tests can't run. Thanks!


As per request the output of ip route: via dev eth0 
default via dev eth0 dev eth0 proto kernel scope link src dev docker0 proto kernel scope link src linkdown dev eth1 proto kernel scope link src 

Edit: the second

The RasPi has the following IPs on its interfaces: eth0 = eth1 =

Pings: Pinging works as expected. Avg. ping time is 0.5ms.

Pinging the outgoing interface of the Pi ( also works. Avg. ping time is 0.667ms.

This means that I can assume some of the traffic at least makes it to the interface and back to the LAN. However, I still do not see why the traffic isn't leaving the interface to the "WAN" (company network). Running tcpdump -i eth1 shows that when pinging clients in the company network, ARP requests arrive at the interface:

13:12:39.660173 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has tell, length 46
2 packets captured
492 packets received by filter
484 packets dropped by kernel

Calling tcpdump on eth0, however, does not yield any messages from eth1. To me this indicates the problem is with the iptables rules, which have previously worked, but that is no longer the case; meaning I'm back at my original question.

  • 1
    (1) Why are you masquerading both directions? You only want to masquerade outgoing connections from LAN to WAN, right? (2) Run tcpdump in several terminals on all interfaces (RaspPi, LAN, WAN), do ping along all addresses on the route to get a better idea of where it breaks.
    – dirkt
    Oct 12, 2021 at 10:17
  • Please tell me the output of ip route command.
    – K-attila-
    Oct 12, 2021 at 10:38
  • @K-att- See my post edit
    – SimonC
    Oct 12, 2021 at 10:58
  • @dirkt If I understood it correctly when we enabled these rules, it lets us perform certain tests directly on the devices, instead of having to open an SSH session on the Pi and then connecting to the devices behind it. This has proven quite useful for certain tests. I checked the output on eth0 and eth1 using tshark and while traffic came on eth1 (LAN), it did not appear on eth0 (WAN)
    – SimonC
    Oct 12, 2021 at 11:00
  • What happened when you try this: ping -I eth1 ? (from 172 to 10)
    – K-attila-
    Oct 12, 2021 at 11:51

1 Answer 1


I've found the problem

So the solution to my specific problem turned out to be quite simple. Either I overlooked it in other forum posts, or I simply didn't find any posts with this suggestion. The iptables rules are all fine, however I was missing the following command:

echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp

Executing this command immediately fixed the issue and now all is well.

Nevertheless thanks to everyone who commented!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .