Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
NAT Routing Issue
« previous
next »
Print
Pages: [
1
]
Author
Topic: NAT Routing Issue (Read 1456 times)
sfudali
Newbie
Posts: 1
Karma: 0
NAT Routing Issue
«
on:
August 15, 2020, 10:06:10 pm »
I have an odd one that I'm not able to sort out. Basic setup is as follows:
vmWare host running two VM's and opnSense 20.7. One physical NIC to internal router/switch, one physical NIC to external ISP. The VM's are in two different networks (192.168.0.0/25 and 192.168.1.0/27). Traffic is able to flow fine between everything internally, but the VM's are not able to ping out to the internet (was testing using 8.8.8.
.
From VM1:
1. Able to ping VM2
2. Able to ping default gateway on switch
3. Able to ping VM2 gateway on switch
4. Able to ping inside interface of opnSense.
From VM2:
1. Able to ping VM1
2. Able to ping default gateway on switch
3. Able to ping VM1 gateway on switch
4. Able to ping inside interface of opnSense.
From opnSense:
1, Able to ping VM1 and VM2
2. Able to ping switch mgmt IP, VM1 gateway, VM2 gateway
3. Able to ping 8.8.8.8.
Tracert from VM1 and VM2 makes it to and returns their default gateway as hop 1 (data switch), internal interface of opnSense as hop 2, and that's where it ends.
It seems like my problem is something possibly NAT related on the return traffic since opnSense is able to ping out to the internet, so I know the outside interface is correct.
In opnSense:
1. I have two gateways defined (default external, internal to my router/switch)
2. I have routes defined for each of the subnets on the switch and their gateway is set to the internal gateway defined above.
Any help would be much appreciated!
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.7 Legacy Series
»
NAT Routing Issue