20-30sThis problems are very short in time loke 1-2sek or longer like 30s?
Right now i have not been able to recreate that problemIf you can "do/recreate a problem" then this will be perfect. If not then only checking logs will be good.
Will do thatSetup the netwatch script at every ros device to check other one.
Fixed the links.About SXT(R) check this:
Simple watchdog: https://forum.mikrotik.comviewtopic.php ... og#p767767
Advance watchdog: https://forum.mikrotik.comviewtopic.php ... og#p768392
Watch LTE parameters: https://forum.mikrotik.comviewtopic.php ... og#p768105
What i said was that the LTE end is OK there is no problem pinging from the SXT-LTE. There is no heat issue, the SXT is outside with temps around 15 degrees celsius.Watch LTE parameters - LteLogger should show you a change between BTS Band/Cell and many that behavior like
* after reboot pings are ok
* when I wait ... then can fix itself
* I move device position and it's fix
can be logged to what cell id you are connect and when all works properly you can do:
* cell lock to have connection with one band and his specific "antenna".
* log change of cellid and that way discover witch one is proper for you.
This all what I write are 80% true.
Some times when you are at CellLock and see the problems are sometimes... then you can thinking then about
* differ signals means parametes of quality link between you and bts
* you should correct position of device etc...
and I say one, you do other one.Watch LTE parameters: viewtopic.php?f=7&t=153622&hilit=watchdog#p768105
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan2
add bridge=bridge1 interface=wlan1
add bridge=bridge1 interface=ether1
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan2
add bridge=bridge1 interface=wlan1
True
Or better yet the bridge should have it's own mac address that is unique to the network.
/ip neighbor print
# INTERFACE ADDRESS MAC-ADDRESS
0 ether1 192.168.88.1 B8:69:F4:01:35:55
bridge1
1 ether1 192.168.88.2 02:2A:F3:AA:A1:E2
bridge1
2 ether1 192.168.88.2 B8:69:F4:B1:FC:C0
bridge1
3 ether1 192.168.88.3 02:2F:19:EF:AF:37
bridge1
4 ether1 192.168.88.3 B8:69:F4:95:63:8E
bridge1
5 ether1 192.168.88.4 B8:69:F4:23:27:AE
bridge1
6 ether1 192.168.88.5 B8:69:F4:B4:1D:66
bridge1
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan2
add bridge=bridge1 interface=wlan1
add bridge=bridge1 interface=ether1
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan2
add bridge=bridge1 interface=wlan1
.... if you manually set MAC address on bridge first. And even then you might experience (transitional) loss of connectivity because management MAC may change this way or another. If you connect to RB via IP (and IP address setup survives changes in L2 configuration of your RB), you might have to re-connect. If you connect to RB via MAC, then you'll have to connect to the new bridge MAC.no difference
This is technical forum, we not speculate... check logs of this event. Try repeat a problemNow i did notice this morning when i moved from one room to another the connection dropped on the ipad and i was not able to ping 192.168.88.1 (SXT - main router) from the ipad.
The isssue lasted for about 1.5minutes and then ping started to work again. Maybe a problem switching from one AP to another? I was moving in the house so it could have been 192.168.88.2 (OruAPMaja) or 192.168.88.6 (OruAPMajaKatusTV) APs.
This is why it is posted in the beginner basics. I don't understand the hostility.This is technical forum, we not speculate... check logs of this event. Try repeat a problemNow i did notice this morning when i moved from one room to another the connection dropped on the ipad and i was not able to ping 192.168.88.1 (SXT - main router) from the ipad.
The isssue lasted for about 1.5minutes and then ping started to work again. Maybe a problem switching from one AP to another? I was moving in the house so it could have been 192.168.88.2 (OruAPMaja) or 192.168.88.6 (OruAPMajaKatusTV) APs.
I see logs disabled in the config filesI have all the logs enabled even debug but the log is empty? Is there a guide how to turn it on?
Actually your ether1 is a "LAN" port. The border between WAN and LAN is in the SXT LTE, everything below that is LAN.Okay that mac address problem seemed to do the trick.. had to set the admin mac address on the bridge..
The admin mac address on the bridge is set to eth1 which is my "WAN" port that is connected to the switch.
Also got my logging working as well.
The site is in the middle of a forest with the closest neighbour at least 1.5km away. When i did a survey on 2.4 and 5Ghz frequencies i saw absolutely nothing but my own devices.You selected very well channel 1,6 and 11 on your 3 wifi devices, as seen in the config.
"Every AC lite box runs 2.4GHz on different channels to make sure they don’t overlap."
Excellent, but what about the rest of the site survey? 2.4GHz tends to interfere well over 1 km in all directions.
The only way to now is measuring.
All tools needed are in your AP's. "Freq usage", "SCAN", and "Snooper".
If neighbors are using other channels than 1,6 or 11 you may have a quite bad wifi experience.
I also see that you have set up the 5GHz with the same SSID. Fine for operational status. But you do not want to be confused by devices selecting 5 GHz without expecting that.
So as i understand you correctly and feel free to correct me the correct setup should beActually your ether1 is a "LAN" port. The border between WAN and LAN is in the SXT LTE, everything below that is LAN.Okay that mac address problem seemed to do the trick.. had to set the admin mac address on the bridge..
The admin mac address on the bridge is set to eth1 which is my "WAN" port that is connected to the switch.
Also got my logging working as well.
So in:
/interface list member
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan1 list=LAN
add interface=ether1 list=WAN
add interface=wlan2 list=LAN
ether1 should be in the LAN list. But as ether1 is also attached to the bridge it is of no use.
The other interfaces are not important, as they are slave to bridge1. So bridge1 should be in the LAN list.
The list names WAN and LAN are used in the default config, they have no 'meaning' as such. They could be called "Cookie" and "Monster".
Look for the word LAN and WAN in your config files, to see if it matters:
E.G.:
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Right now i have enabled all the topics above. Will add the wireless topic as well.I see logs disabled in the config filesI have all the logs enabled even debug but the log is empty? Is there a guide how to turn it on?
/system logging
set 0 disabled=yes
set 1 disabled=yes
set 2 disabled=yes
set 3 disabled=yes
Should be
/system logging
set 0 action=memory disabled=no prefix="" topics=info
set 1 action=memory disabled=no prefix="" topics=error
set 2 action=memory disabled=no prefix="" topics=warning
set 3 action=echo disabled=no prefix="" topics=critical
A line with "wireless" as topic is an interesting addition here
add action=memory disabled=no prefix="" topics=wireless
Well as all those interfaces are a port on bridge "bridge1", they become slave interfaces. So the really important one is "bridge1".
So as i understand you correctly and feel free to correct me the correct setup should be
/interface list member
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan1 list=LAN
add interface=bridge1 list=LAN
add interface=wlan2 list=LAN
and ether1 should not be on any list?
and also a futher update my bridge on the APs atm has a seperate admin mac that is unique to the network, should this be changed back to being the same as ether1 mac address?
That's a very clean area. Even the trees are very good RF filters.
The site is in the middle of a forest with the closest neighbour at least 1.5km away. When i did a survey on 2.4 and 5Ghz frequencies i saw absolutely nothing but my own devices.
Wifi interface 2 (5Ghz) is disabled so only 5Ghz is in use.
So i added bridge1 to the LAN interface list. Quick question, if i start without default config and then just paste my configuration to the terminal. How are the interface lists even an issue if i don't use them anywhere in the configuration?Well as all those interfaces are a port on bridge "bridge1", they become slave interfaces. So the really important one is "bridge1".
So as i understand you correctly and feel free to correct me the correct setup should be
/interface list member
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan1 list=LAN
add interface=bridge1 list=LAN
add interface=wlan2 list=LAN
and ether1 should not be on any list?
and also a futher update my bridge on the APs atm has a seperate admin mac that is unique to the network, should this be changed back to being the same as ether1 mac address?
No need to change back the MAC address of the bridge. Make sure your MAC addresses are unique in the network.
You have some similar devices, and it is tempting to copy/paste a configuration by doing backup/restore which will copy the MAC addresses as well.
Even EXPORT contains MAC addresses that might be imported.
I could turn the question around. If you don't use the interface list, then why do you make them? I prefer , if you make interface lists, that they are correct, unless you want to confuse yourselves or make the config hard to read for humans. And even more, those WAN/LAN interface lists are in the default configs, and are used there at several places. And so actually you are using them ....
So i added bridge1 to the LAN interface list. Quick question, if i start without default config and then just paste my configuration to the terminal. How are the interface lists even an issue if i don't use them anywhere in the configuration?
Logging is not 100% insync, I assume ...small diff in clocks or actually the disconnect is only detected after all the retries and a timeout.if the device didn't announce it is leaving. But "registered to other device in network " looks like it did announce.Just saw connection drop checked the logs on the AP's only saw this:
MajaAP
07:50:22 wireless,info 24:1B:7A:94:74:AF@wlan1: connected, signal strength -84
07:50:54 wireless,info 24:1B:7A:94:74:AF@wlan1: disconnected, registered to other device in network
MajaAPKatusTV
07:50:23 wireless,info 24:1B:7A:94:74:AF@wlan1: disconnected, registered to other device in network
07:50:54 wireless,info 24:1B:7A:94:74:AF@wlan1: connected, signal strength -56
no logs on the SXT side on that time. Is there a specific topic i should log? Right now i log the default topics.
Difficult to hint what the tuning should be without seeing the "registration" information (detailed view) and its fluctuation over time. That, together with "freq usage" and "snooper" scans, would give some clue on what is causing your poor wifi experience.Thanks for the detailed explanation.
I had to rollback that interface list removal change. After that change the whole network went haywire.
On another note yesterday i worked with an ethernet cable attached from my laptop to OruAPSaun, everything worked like clockwork, no connectivity issues at all.
Behind wifi i cannot even make slack audio calls properly, not to mention even video calls, it's very laggy and keeps disconnecting.
Very good suggestions. Although i will put the blame under hap ac lite. I did some monitoring and research and i have come to the conclusion that the transmit power for hap ac lite is very weak compared to similar products on the market like hap ac and RB951G-2HnD.Difficult to hint what the tuning should be without seeing the "registration" information (detailed view) and its fluctuation over time. That, together with "freq usage" and "snooper" scans, would give some clue on what is causing your poor wifi experience.Thanks for the detailed explanation.
I had to rollback that interface list removal change. After that change the whole network went haywire.
On another note yesterday i worked with an ethernet cable attached from my laptop to OruAPSaun, everything worked like clockwork, no connectivity issues at all.
Behind wifi i cannot even make slack audio calls properly, not to mention even video calls, it's very laggy and keeps disconnecting.
Remedies are like moving the AP away from wall and furniture. Check signal strength in both directions. Avoid interference by moving channel and even by lowering bandwidth.
Sending smaller aggregation packages can avoid large retransmits (but this also lowers the max data throughput) , by reducing the A-PSMDU from 8192 to 2048.
Improving the respons time on time and jitter critical communication, by setting the user priority and enabling WMM. (enabling WMM without setting priority doesn't help much)
viewtopic.php?f=7&t=161295#p795361
If you start using user priority don't forget to extend the use of A-PMDU for those other priorities except voice (7)