I have a small capsman setup with three CAPs but running into user visible issues with a wifi client. It seems to me like it switches between two CAPs very often which also results in reported breaking connections which I do not really expect with capsman at all.
The logging when that happens looks like this:
Code: Select all
08:25:31 interface,warning ether4-Office: bridge port received packet with own address as source address (cc:2d:e0:c2:cf:8e), probably loop
08:25:35 dhcp,info default assigned 192.168.250.120 to 2C:0E:3D:26:75:C7
08:26:18 caps,info [::ffff:192.168.250.251:38207,Join,CAP-6A347E5C9611] joined, provides radio(s): CC:2D:E0:C2:CF:8E,CC:2D:E0:C2:CF:8F
08:26:18 caps,info dg-2g: selected channel 2452/20/gn(20dBm) (fixed)
08:26:18 caps,info dg-5g: selected channel 5180/20-Ceee/ac/P(23dBm) (fixed)
08:26:26 caps,info 2C:0E:3D:26:75:C7@dg-2g connected, signal strength -62
08:26:26 caps,info 2C:0E:3D:26:75:C7@eg-2g disconnected, registered to other interface
08:26:28 interface,warning ether4-Office: bridge port received packet with own address as source address (cc:2d:e0:c2:cf:8e), probably loop
08:26:34 interface,warning ether4-Office: bridge port received packet with own address as source address (cc:2d:e0:c2:cf:8e), probably loop
08:26:35 caps,info 2C:0E:3D:26:75:C7@dg-2g disconnected, interface disabled
08:26:38 caps,info 2C:0E:3D:26:75:C7@eg-2g connected, signal strength -77
08:26:45 dhcp,info default deassigned 192.168.250.120 from 2C:0E:3D:26:75:C7
08:26:45 dhcp,info default assigned 192.168.250.120 to 2C:0E:3D:26:75:C7
08:26:58 caps,info [::ffff:192.168.250.251:49277,Join,CAP-6A347E5C9611] joined, provides radio(s): CC:2D:E0:C2:CF:8E,CC:2D:E0:C2:CF:8F
Is this caused by the loop warning? Both CAPs are connected to capsman via that ether4-Office interface and the reported source address is one of the two wireless interfaces of the CAP which is reported to join frequently.
Any idea what happens here and what would cause it?