I posted this on r/Ubiquiti, nothing but crickets, so here we go.
[Here's the current topography](https://imgur.com/a/oV2gXjh)
I know this might not be the most efficient setup, and I will most likely be making some changes before there are actual users at the branch site. That said...
The issue I have here is that no device on the 1.0 subnet can ping ANT1 at the 1.90 LAN address. It seems like any static routes actually overrule directly connected hosts.
Current facts:
*Subnet 2.0 (branch office) has total access to everything: all internal LANS and WAN.
*ANT1 can be reached via the 10.0.0.1 IP as expected, from any subnet.
*The ASA is the only device in the 1.0 subnet that can ping 1.90.
*Any device can reach ANT1 via 1.90 IF I add a static route for them on ANT1.
One caveat that confused me was that the "WAN" interface only seems to be able to be present on the WLAN side, which makes the default gateway a little confusing since its pointing the wrong way. Nothing from the 2.0 subnet could ping anything from the 1.0 subnet until I added the 192.168.1.0/24 --> 192.168.1.90 static so the ASA could hairpin route the traffic back on the same interface. Now everything works, except 1.0 devices cant ping 1.90, they have to ping 10.0.0.1.
Is this normal behavior for ubiquity to have static route overule directly connected subnets with correct subnet masks?
Again, I know there are different, more efficient topologies. But even so, shouldn't the antenna still reply to pings on the same subnet?
No comments:
Post a Comment