Routing Between Subnets

General questions
1

Hi,

Sorry if this has been asked before, but not managed to find the answer.

I’ve deployed vyos firewall into my test lab which is running on VMworkstation and want to be able to connect via rdp to VMs running on my lab subnet from my home wifi.

I have 3 networks configured with VMworkstation as follows:
VMNET1 = bridge directly to home network 192.168.0.0/24
VMNET2 = 10.0.0.0/24
VMNET3 = 10.0.1.0/24

I have configured 3 ethernet interfaces on the vyos as follows:
eth0 = VMNET1 192.168.0.254
eth1 = VMNET2 10.0.0.254
eth2 = VMNET3 10.0.1.254

I can ping each eth interface .254 from all VMNETS, but can’t RDP or ping any host on any other networks from my home network.

So i can ping from my laptop on wifi home network:
192.168.0.254
10.0.0.254
10.0.1.254

if i run tracert from my laptop to 10.0.0.1 it hits 192.168.0.254 but doesn’t go to the next hop of 10.0.0.254 which i think is the problem, but dont know how to solve?

Any help would be much appreciated

Thanks

Tommy.

2

So i finally managed to solve this. It’s turns out that the order i added the NICs to the system wasn’t the same order as vyos displayed.

So NIC 1 within the VM wasn’t NIC 1 within vyos, so when i added the address to the interface it wasn’t on the same network/subnet. doh!

Anyway, i can now ping across all subnets, but have a odd issue that some the the devices on VMNET 2 are not pingable from VMNET 1

So i can ping from 192.168.0.200 to 10.0.0.2 but i can’t ping from 192.168.0.200 to 10.0.0.1.

If i rdp onto 10.0.0.2 device i can ping 10.0.0.1. so i know is contactable.

What might be causing this?

Thanks

Tommy

3

On the 10.0.0.1 device, what is the default gateway? Presumably the 10.0.0.2 device is using 10.0.0.254 as its gateway, so the ping replies get back to 192.168.0.200.

My guess is that the 10.0.0.1 device does not use 10.0.0.254 as its gateway, or it has some other route to 192.168.0.0/24 so the reply packets are not getting back.