Tag Info

New answers tagged

1

The problem can be at two different layers: at the forwarding level: ipforwarding can be disabled, or iptables rules be misconfigured at the routing level: your corporate network must be informed that the various 10.2.80.x networks can be reached via IP 10.2.82.195. If this is not possible, you had to "masquerade" (NAT) yours 10.2.80.x network using the ...


0

The answer is not really mine, but... Try following Open vSwitch on VirtualBox There was also a brief text file from some Fedora people on similar subject: libvirt and OpenVSwitch in a form of text file... wasn't able to locate it though. as per comment, here's short summary: (1) Create vnet0 interface and br0 bridge: ovs-vsctl add-br br0 ip tuntap add ...


0

In general, TCP/IP based networks expect all machines in the same subnet to be directly reachable. You break this rule in your setup. Configure two subnets, 192.168.0.x for the master and 192.168.1.x for the slave, set up device3 to forward packets (router functionality) and tell master that in order to reach 192.168.1.x use device3 as the gateway, and ...



Top 50 recent answers are included