Balance20 VLAN

Lost my post due to 500 :frowning: bad attempt at rewrite.

Trying to setup another VLAN but can not communicate across boundaries. I tired to change the AP to use but could not connect to it for some reason- Will keep trying to get a known good device on the 1.2 subnet and confirm that it is not the device. I think since I’m seeing ‘!H’ in tracenet that it’s not that?

Long-short: Trying to connect LCI CAN<->Ethernet controller to the router. Directly connected via ethernet, moved devices and can lines around to work that. Other CAN devices are still operating as expected, so do not expected device to be non-functional in anyway.

➜  ~ ifconfig en0
	ether 88:66:5a:1c:89:2a
	inet netmask 0xffffff00 broadcast
	media: autoselect
	status: active
➜  ~  curl
curl: (7) Failed to connect to port 8080: Network is unreachable
➜  ~ traceroute
traceroute to (, 128 hops max, 52 byte packets
 1  balance-9867 (  5.390 ms  3.042 ms  3.869 ms
 2  balance-9867 (  3076.091 ms !H  3004.095 ms !H  3006.996 ms !H
➜  ~ traceroute
traceroute to (, 128 hops max, 52 byte packets
 1 (  4.416 ms  2.990 ms  3.560 ms
➜  ~ traceroute
traceroute to (, 128 hops max, 52 byte packets
 1 (  7.750 ms  2.345 ms  2.486 ms

If inter VLAN routing is enabled it blocks traffic to (and from) that VLAN to (and from) other VLANs that have inter-VLAN routing enabled.


this doesn’t seem to change anything and feels wrong? The way I read that is two VLANs with intervlan can not talk to each other, that one has to have inter vlan and the other does not?

edit: deleted a bunch of stuff that was here before related to my BGP setup working for a 10 second window on clicking apply. This was because I had a LAN setup on the same subnet since I wasn’t sure if it was needed but after understanding BGP more it seemed clear that needed to go.

From One Control Connect Anywhere with NEW Blue Label - Page 6

The solution is likely related to the hardware. Needed to be set to access mode instead of trunk mode on the LAN port settings.

A little curious why it showed up as a client before this- but I imagine it must have been in some sort of half-connected state.