however we have a few hundred spread out over many sub-maps, so a "back-door" solution is preferable, also to automate for future changes.
I prefer it that Bandwidth tests, pings, tracert, etc. time out after a while, but maybe 50 is to quick.In draws only 50 bars and then stops updating the histogram.
+1 and to have a firewall filter/mangle:Feature Request for 6.3
adding the possibility to execute script with parameters
/system script run script1 $1 $2 $3 $4
Thanks, but that will use to many frequencies to cover a flat area where APs can see each other, but clients can see all APs.Dont use mesh and add separate links
Could it be that AP & clients was on 'unspecified' causing a problem. I would assume if 'unspecified' on AP is selected, it will default to 802.11?What wireless mode are you running? 802.11?
Don't have it on 4.16 though.2) and 3) are normal behavior on low traffic times.
On both AP & station?Try to play with the hw-retries setting - lower or increase it.
Try disabling the adaptive-noise-immunity.
Does that mean NV2 will also have packet aggregation into frames (framing policy terminology?) as NStreme does?You can think of it as of improved nstreme.
My bad. It's official then; I'll call it a draining hole from now on.I also know of plenty of breathing designs, but I can't think of any designs that have so many joining edges without any sort of a gasket and on vertical surfaces too.
I agree. Think of it as "breathing holes", not "drain holes". Pshycologically it sounds less apocalyptic.So unless your CPE is hermetically sealed with an inert dry gas in the air space within the unit you will always need a way for water to get out