Have an update. Did a packet capture and saw that the router that is doing the nat is not replying to pings.
I double-checked the config and saw that "source IP address spoofing protection" was enabled, once it was turned off the default route was working and I was able to ping.
So basically the router decided that my client was a spoof attack.
The clients are showing the proper IP address of their default gateway.
For example when a client received a DHCP lease from 10.1.20.0/24 (client ip 10.1.20.2, default gateway 10.1.20.200), the client on that network could not ping 10.1.30.1 which was originally the default route on the switch while directly from the switch 10.1.30.1 was replying to pings.
All vlan interfaces have IP assigned to them and clients are able to communicate in between vlans. There are no ACL set on the router.
Current workaround that I am using is adding default route with same priority for each vlan 10.1.20.1, 10.1.30.1, 10.1.40.1 and so on.
I will run a packet capture today hopefully that will provide additional insight into the problem.
Mr.Larry91
3 Posts
0
October 15th, 2020 07:00
Hi guys,
Have an update. Did a packet capture and saw that the router that is doing the nat is not replying to pings.
I double-checked the config and saw that "source IP address spoofing protection" was enabled, once it was turned off the default route was working and I was able to ping.
So basically the router decided that my client was a spoof attack.
DELL-Josh Cr
Moderator
•
9.4K Posts
0
October 14th, 2020 13:00
Hi Mr.Larry91,
When the clients are being assigned DHCP do they show the proper ip address for their default gateway?
Mr.Larry91
3 Posts
0
October 14th, 2020 23:00
Hi,
The clients are showing the proper IP address of their default gateway.
For example when a client received a DHCP lease from 10.1.20.0/24 (client ip 10.1.20.2, default gateway 10.1.20.200), the client on that network could not ping 10.1.30.1 which was originally the default route on the switch while directly from the switch 10.1.30.1 was replying to pings.
All vlan interfaces have IP assigned to them and clients are able to communicate in between vlans. There are no ACL set on the router.
Current workaround that I am using is adding default route with same priority for each vlan 10.1.20.1, 10.1.30.1, 10.1.40.1 and so on.
I will run a packet capture today hopefully that will provide additional insight into the problem.