Hi
following another thread that was closed already I am reopening this case because my issue wasn’t solved yet.
I have hEX s as CAPsMAN and hAP ac^2 as AP
I have few lost of connectivity’s and losing pings during some time to time - losing pings for 6-7 and once its back I see it reach 2000ms
I am exporting here the configuration I use
when I move the hAP ac^2 to be WISP AP as a standalone the pefromance is much much better. not the best as for my Meraki AP
on Meraki I could get full of 200mbit/200mbit connection, on hAP ac^2 I get at most ~150mbit .
Use fixed channels.
Set all configuration (like country code, installation, etc.)
Nothing wrong with using DFS (only discomfort is the time it might take to scan)
With the settings supplied in your other topic I am able to get 400 ~ 450 Mbps (on the 5GHz radio of course).
As I understand then you are pinging from wifi client device that is connected to AP? Try isolate issue by testing network stability from CAP to CAPSMAN server.
Couldn’t find a flapping port. I have reset both devices to default. Set ac2 as cap and hex s as capsman and issue was reappear even when i connected the meraki so i am quite convinced that the issue is on hEX s . For testings i want to give few says with the ac^2 as main router and wifi as router.
I also noticed that ether2 was configured as the gateway ip and not as bridge that had the default ip 192.168.88.1 i am thinking that it could be bridge configuration mismatch.
Hi, usual mistakes … ethernet interfaces that are ports to the bridge, are slave interfaces. Settings for them must be done on the bridge not on the interface.
Set IP address on the bridge bridge1, not on ether2
Make bridge1 member of the LAN interface list (ether2-ether5 are part of bridge1). If the ether2-5 are in the LAN list or not, that information does not harm, but is not used. Lucky as ether1 on the WAN list is wrong, if it is on the bridge also.
You tweak for performance (hwretries=3) but all performance tuning should be well understood. HWretries=3 will reduce the interface rate faster, and will disconnect faster, when there are retransmits.
Don’t use a/n/ac if you do not need a, use n/ac . If you do not need n , use ac-only (=less overhead, better throughput)
Never rely on “auto” frequency with MKT. Set it yourselves after checking with Scan/Freq usage/Snooper for others to be avoided. Set Ceee or eCee,eeCe, eeeC , not XXXX as you don’t know what will be choosen.
Ether2 was set as 192.168.88.1 probably as default and not by me.
Following what you said about slaves it means that i dont need to configure bridge for CAP?
When ether1 on ac2 was on a bridge it was when i tried to power up the ac2 with poe in. I figured out that hex s doesnt have enough power to do it properly eventhough it was working.
Who could tell what capsman configuration are recommended to avoid any lose or cut of bandwidth. And also what are the rates being recommended to be use.
Actually 192.168.88.1 on (slave interface) ether2 is a default configuration (or quick set) thingy. And; I think we’re here to share & learn, not to call BS on each other.
well well … going back to Quick Set after doing anything in Winbox or webfig … is a guaranteed way to get in trouble.
Never ever re-enter Quick-Set if something has been touched. The scripts are not smart, and do not consider whatever someone has done except what was in the default config.
Would not be surprised there are indeed mis-configs in Quick Set. After some experience one stays away from Quick Set.
There are 7 Quick Sets for the hAP ac2. And which is what? What if you change Quick Set choice while entering data? These Quick Sets are not the Default Config.
“ethernet” is not one of the hApac2 Quick Sets, you are on CHR.
Leave the rates on default. Wifi is dynamically adjusting. The wifi performance can be followed in wireless tables menu, tab “registrations”.
In tab list check signal level , TX/RX CCQ, and interface rate used (rate/bandwidth/streams/guard).
This is essential information before touching anything in the wireless settings.
CCQ values may be low until there is enough traffic generated.
