You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enabled NAT overloading on R1. I then created three clients: 2 VPCS and one Qemu client WinXP (I know its ancient, but...). All of them are able to acquire their IPs through helper-address.
NAT overloading is working just fine. All clients can ping each other and the default gateway 192.168.56.1/24.
The issue I'm seeing is that the two VPCS are unable to ping any nodes be it by hostname or IP outside their subnet. WinXP, however, can ping any nodes no problem as per screen shot.
While on my previous setup where the dhcp server is hosted on the Router1 itself, the VPCS can ping any nodes no problem. I don't have this setup anymore, though I might have to redo it just to verify it again.
I might add docker later just to see.
Other than this, VPCS is really awesome.
The text was updated successfully, but these errors were encountered:
I enabled NAT overloading on R1. I then created three clients: 2 VPCS and one Qemu client WinXP (I know its ancient, but...). All of them are able to acquire their IPs through helper-address.
NAT overloading is working just fine. All clients can ping each other and the default gateway 192.168.56.1/24.
The issue I'm seeing is that the two VPCS are unable to ping any nodes be it by hostname or IP outside their subnet. WinXP, however, can ping any nodes no problem as per screen shot.
While on my previous setup where the dhcp server is hosted on the Router1 itself, the VPCS can ping any nodes no problem. I don't have this setup anymore, though I might have to redo it just to verify it again.
I might add docker later just to see.
Other than this, VPCS is really awesome.
The text was updated successfully, but these errors were encountered: