Weirdness with ES switch and IP reporting - Actually working in a very weird manner
The following devices are connected to an ES switch within the management scope of my main site with an ER8411 router. These devices are on a switch only vlan that exists on this omada site purely to allow me to add the vlans to port profiles. The gateway for these vlans is actually on a ER7206 v2 running the new 2.2.3 which is the gateway for all my public access / insecure networks . The ER7206 has a trunk vlan from the main sire core switch carrying the management vlan, and all the public access vlans it hosts
No IP reported, as expected with this switch model with all current firmwares on the main site.
However, here are the same 3 clients on this ES switch, from the point of view of the ER7206 v2 (different site) which is the actual gateway for these vlans.
IPs are being reported.
Why is this given what we know about these units? Why do the IPs show up on the 7206 ?
Im not sure if this might help the devs narrow down whatever the IP reporting issue is with these switches and the ARP scanning feature of the gateways which currently doesnt work on the "host" site of the ES switches
Topology
- The ER8411 on the left is the host of all our main private LANs. It is not aware of the public LANs, no routes etc.
- All network hardware (all switches, APs etc) is adopted on the ER8411 site. This site has the ER7206 hosted lans added as switch only vlans to allow port profiles.
- The ER7206 on the right is the host of the Public access LANs
- The ER8411 and ER7206 share common management vlan (1) so can both be managed by OC300 and "exist" on the same physical network just as different sites.
- All network hardware is downstream of the SG3428X switch at the bottom and belongs on the ER8411 site