I have a problem with hap ac. When wlan interface works as stand alone interface (without bridge) then everything works fine. Problem is when wlan gets connected as bridge port. Then is situation as follows:
ping from client to router is ~1ms
ping from router to client is somewhere between 1ms and 200ms.
ping from client to client on the same interface is, if not lost, then around 1000-2000ms.
When i say “client” I mean everything: computers (win/osx, phones, tablets…).
I’ve tried every possible combination of configuration for bridge and ports (even tried with only one port) and it does not work. As soon as I disconnect wlan from bridge then everything works fine.
Any ideas? I tried with 6.36 and then with 6.34 but always same problem.
Simplify and work backwards. Disable all of your firewall rules as well as your NAT and Mangle. If you are stable at that point, enable one at a time to find out where your problem lies.
Well, this is brand new device. No fw or mangle rules. No load on device (only devices used for testing).
I’ve done some more testing this morning and bridge is only thing that makes problem.
So if anyone has some idea of how to configure bridge in order to work properly…? As i said, I tried every possible combination but problem is still there but maybe I missed something…
PING 10.2.1.1 (10.2.1.1): 56 data bytes
64 bytes from 10.2.1.1: icmp_seq=0 ttl=64 time=2.912 ms
64 bytes from 10.2.1.1: icmp_seq=1 ttl=64 time=1.765 ms
64 bytes from 10.2.1.1: icmp_seq=2 ttl=64 time=1.170 ms
64 bytes from 10.2.1.1: icmp_seq=3 ttl=64 time=1.768 ms
64 bytes from 10.2.1.1: icmp_seq=4 ttl=64 time=1.736 ms
64 bytes from 10.2.1.1: icmp_seq=5 ttl=64 time=1.850 ms
64 bytes from 10.2.1.1: icmp_seq=6 ttl=64 time=1.007 ms
64 bytes from 10.2.1.1: icmp_seq=7 ttl=64 time=1.811 ms
64 bytes from 10.2.1.1: icmp_seq=8 ttl=64 time=1.182 ms
64 bytes from 10.2.1.1: icmp_seq=9 ttl=64 time=3.040 ms
64 bytes from 10.2.1.1: icmp_seq=10 ttl=64 time=1.897 ms
64 bytes from 10.2.1.1: icmp_seq=11 ttl=64 time=1.807 ms
64 bytes from 10.2.1.1: icmp_seq=12 ttl=64 time=1.036 ms
64 bytes from 10.2.1.1: icmp_seq=13 ttl=64 time=1.169 ms
64 bytes from 10.2.1.1: icmp_seq=14 ttl=64 time=1.736 ms
64 bytes from 10.2.1.1: icmp_seq=15 ttl=64 time=1.696 ms
64 bytes from 10.2.1.1: icmp_seq=16 ttl=64 time=1.832 ms
64 bytes from 10.2.1.1: icmp_seq=17 ttl=64 time=1.772 ms
64 bytes from 10.2.1.1: icmp_seq=18 ttl=64 time=1.260 ms
64 bytes from 10.2.1.1: icmp_seq=19 ttl=64 time=1.569 ms
64 bytes from 10.2.1.1: icmp_seq=20 ttl=64 time=1.775 ms
64 bytes from 10.2.1.1: icmp_seq=21 ttl=64 time=1.852 ms
As I already said. Changing client device does not help. This was on 5ghz interface but it is the same on 2,4 as long as interface is on bridge. I tried to add virtual interface which would not be part of bridge and it works then correctly. So, the only problem seems to be the bridge…