capsman wifiwave2 roaming arp issue

RouterOS Wireless Networking
1

Hi very quick

I have 2 hap ax2 and and rb5009 for capsmanager

Setup look ok however I have a issue with FT roaming .

hapax2_1 – vlan trunk —> rb5009 <— vlan trunk — poweline addapters – hapax2_2 (different room)

wifi is via vlan however I do not thinks this is the issue.

The problem, When I connect to hapax2_1 and move to the other room hapax2_2 stop to receive apr request from the gw rb5009
If I back to hapax2_1 everting start to work again. (with ft roaming )

If I first connect to hapax2_2 everting work, when I go to hapax2_1 still work when I back to hapax2_2 stop working … If I do the same again hapax2_1 work hapax2_2 not (the arp I mean)

What I can see all bridges changes the ports and look ok .. but If is sniff the traffic

hapax2_2 → send ARP requests for gw ip address .. but no replay !
rb5009(capsman) see them and replay but for some reasons they never reach hapax2_2

With hapax2_1 I do not have such issue

As I say I have powerlines adapter between hapax2_2 and rb5009 … hapax2_1 is directly connected
Not sure if they are responsible for this .. but they do not have any arp tables .. so I guess for now I consider them as single cable

I wonder what I can do with those arps … is the problem in the rb5009 bridge or hapax2_2 bridge

I try do reduce bridge ageing and arp timeouts .. same

If I leave the client for some time .. hapax2_2 start to receive arp replays and everything start to work .. so I guess is arp cache issue and the fact roaming mov same client mac from hapax2_2 to hapax2_1 and vice versa

Also I update ROS rom 7.11.2 to the test beta 7.12b9 .. no changes

Any idea or advice what I can try to solve this arp issue (btw dhcp is on rb5009 wifi vlan … and more strange is … client aways get ip address .. after disconnect as well !!! … also I do not think is rstp related .. except the moment when wifi interfaces (dynamic) go to forward mode .. but I guess is not related )

Wireless clients cannot connect
2

Ahh so I think I found the problem

Everything leading to arp cache issues, I check all ros devices also I make the problematic ap with dedicated network and nat .. and yes the problem still remain !!

So this arp issues must be related to devolo powerline adapters ..
And look like this was the problem :smiley:

If someone have similar issues like this one and use powerline adapters specially Magic 2 LAN 1-1 probably will find this solution as interesting
The solution is very simple , EoIP tunnel between wifiwave2 capsman gw and the CAP behind devolo :slight_smile: .. Probably L2VPN will be much faster for now this work.

hapax2_1 -- vlan trunk ---> rb5009 <--- vlan trunk --- poweline addapters -- hapax2_2
                                <----------------------- EoIP ------------------>

On remote CAP hapax2_2 just add EoIP interface in dedicated bridge also the wifi interfaces .. and yes I’m using vlan filtering not sure why in the help docs they don’t .. anyway

note: during testing’s I revert to ros 7.11.2

Regards :slight_smile:

3

Good find and thanks for reporting how you solved it.
Others might benefit from it.

4

Actually I found and another problem which was fixed by 7.12rc1 (wifiwave2 - use CAPsMAN’s “datapath.vlan-id” on CAP for bridge port “pvid”) + some fixes in my L2 and vlan ingress filtering .. eoip is removed and for now everting work as expected however if someone have a issues with arp and broadcast eoip/l2vpn are still a options :slight_smile: