0

I have a remote private network connected to the internet via a Linux gateway. The gateway has the following arrangement:

  • eth0 - external IP
  • br0 - with eth1, and tap0 devices added to the bridge.

eth1 is the internal network, we'll call it 192.168.0.1. eth1 serves DNS and DHCP. Everything is working perfectly on that internal network, clients get DHCP addresses and DNS works.

Now I want to ether bridge to the remote network from a local site. The local site consists of only two machines on another private network: local gateway and a client machine. So I've run on the local gateway:

ssh -o Tunnel=ethernet -w 0:0 root@remote.gateway

This partially works. There are no errors reported by ssh. The client machine acquires an IP address from the DHCP server 192.168.0.1, and can ping the server and perform DNS lookups however it can't communicate with any other machines on the remote private network (e.g. Remote server).

What do I need to do to tell the local/remote gateway that packets should be forwarded on to relevant remote machines?

enter image description here

0

This didn't work because the VMWare virtual switch I was using for the remote server network was not in promiscuous mode. The ARP requests were getting as far as the remote server NIC, but never getting back to the gateway. So the answer was to configure the switch to allow promiscuous mode. In vSphere, with the host selected Manage -> Networking -> Virtual Switch -> edit.

More here: https://kb.vmware.com/s/article/1002934

New contributor
Keeely is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.