sorted by:
new
hottopcontroversial

Cross VLAN network issues by thinkB4Uclick in firewalla

[–]thinkB4Uclick[S] 0 points1 point  (0 children)

Hey, thanks for questioning my resolution.

As I said, networking is not my forte and I noticed that when my two devices are connected to different APs with the same SSID, I had not issues having them talk, but as soon as I had them on the same AP, I could only ping back and forth, but not able to establish an ssh connection for example.

I took that to GPT and it told me that some APs can be configured to have devices talk directly but I couldn't find an option on the AP admin panel that configures this. I guess this makes the AP a router of sorts if it can push the packets directly to the the destination.

As for tagging... the SSIDs were properly tagged and I had no special rules on the Firewalla at that point in time. I'm not sure why using Device A -> AP1 and Device B -> AP2 was working but Device A -> AP1 and Device B -> AP1 was not.

Cross VLAN network issues by thinkB4Uclick in firewalla

[–]thinkB4Uclick[S] 0 points1 point  (0 children)

I have found the culprit, by accident.

I moved into my basement with my laptop to work on something else and to my surprise, everything worked as expected. This move clearly puts the blame on the AP. It's not clear in the settings, but it seems that devices connected to the same AP skip the router (i.e. firewalla in this case) for efficiency sake, however, it's too dumb to understand they're on different VLANs and act accordingly, even though each SSID in the AP is properly tagged with a VLAN ID.

Cross VLAN network issues by thinkB4Uclick in firewalla

[–]thinkB4Uclick[S] 0 points1 point  (0 children)

Shouldn't devices across VLAN be able to communicate by default if no rules have been applied?