Connect PC or TV (or preferably both) using an ethernet cable!
Use WiFi only where it is required, e.g. mobile devices.
Config would be helpful: /export hide-sensitive
# may/20/2020 16:37:30 by RouterOS 6.43.11
# software id = 7HI7-56Z4
#
# model = RBD52G-5HacD2HnD
# serial number = A97409825A90
/interface bridge
add arp=proxy-arp fast-forward=no mtu=1500 name=LAN-Bridge
add arp=proxy-arp disabled=yes fast-forward=no mtu=1500 name=LAN-wifi
/interface ethernet
set [ find default-name=ether1 ] name=WAN speed=100Mbps
set [ find default-name=ether2 ] speed=100Mbps
set [ find default-name=ether3 ] speed=100Mbps
set [ find default-name=ether4 ] speed=100Mbps
set [ find default-name=ether5 ] speed=100Mbps
/interface pppoe-client
add add-default-route=yes disabled=no interface=WAN name=pppoe-out1 \
use-peer-dns=yes user=OnquBot3Ts
/interface wireless
set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode \
band=5ghz-onlyac channel-width=20/40/80mhz-XXXX country=japan disabled=no \
disconnect-timeout=15s distance=indoors frequency=5260 frequency-mode=\
regulatory-domain hw-protection-mode=rts-cts hw-retries=10 mode=ap-bridge \
multicast-helper=disabled name=LAN-wfi5ghz on-fail-retry-time=1s \
radio-name=MikroTik5G ssid=MikroTik5G tx-power=25 tx-power-mode=\
all-rates-fixed wireless-protocol=802.11 wmm-support=enabled wps-mode=\
disabled
set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode \
band=2ghz-onlyn disabled=no disconnect-timeout=15s frequency=auto \
frequency-mode=superchannel mode=ap-bridge multicast-helper=disabled \
name=LAN-wifi24ghz radio-name=Mikrotik2G ssid=Mikrotik2G \
wireless-protocol=802.11 wmm-support=enabled wps-mode=disabled
/interface wireless nstreme
set LAN-wfi5ghz enable-polling=no
set LAN-wifi24ghz enable-polling=no
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" \
group-key-update=1h mode=dynamic-keys supplicant-identity=MikroTik
add authentication-types=wpa-psk,wpa2-psk eap-methods="" name=none \
supplicant-identity=""
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=LAN-Pool ranges=192.168.88.2-192.168.88.254
add name=lan-wifi5ghz-pool ranges=192.168.90.2-192.168.90.254
/ip dhcp-server
add add-arp=yes address-pool=LAN-Pool disabled=no interface=LAN-Bridge \
lease-time=12h name=DHCP-Server
add add-arp=yes address-pool=lan-wifi5ghz-pool interface=LAN-wifi lease-time=\
12h name=dhcp-wifi
/system logging action
add disk-file-count=4 disk-file-name=disk1/log name=usb target=disk
/interface bridge port
add bridge=LAN-Bridge interface=LAN-wifi24ghz
add bridge=LAN-Bridge interface=LAN-wfi5ghz
add bridge=LAN-Bridge interface=ether2
add bridge=LAN-Bridge interface=ether3
add bridge=LAN-Bridge interface=ether4
add bridge=LAN-Bridge interface=ether5
/interface wireless access-list
add mac-address=5C:8D:4E:42:01:49 vlan-mode=no-tag
add comment=Maya mac-address=14:C2:13:7D:4F:11 vlan-mode=no-tag
/ip address
add address=192.168.88.1/24 interface=LAN-Bridge network=192.168.88.0
add address=192.168.90.1/24 disabled=yes interface=LAN-wifi network=\
192.168.90.0
/ip cloud
set ddns-enabled=yes
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=192.168.88.1 gateway=192.168.88.1 \
netmask=24
add address=192.168.90.0/24 dns-server=192.168.90.1 gateway=192.168.90.1 \
netmask=24
/ip dns
set allow-remote-requests=yes cache-size=4096KiB
/ip firewall address-list
add address=192.168.88.0/24 list=alow-ip
/ip firewall filter
add action=accept chain=input disabled=yes dst-address=192.168.88.1 dst-port=\
80 in-interface=pppoe-out1 protocol=tcp src-address=0.0.0.0 src-port=80
add action=accept chain=input disabled=yes src-address-list=alow-ip
/ip firewall nat
add action=masquerade chain=srcnat out-interface=WAN src-address=\
192.168.88.0/24
add action=masquerade chain=srcnat out-interface=pppoe-out1 src-address=\
192.168.88.0/24
add action=masquerade chain=srcnat out-interface=pppoe-out1 src-address=\
192.168.90.0/24
/ip route
add distance=1 dst-address=192.168.90.0/24 gateway=LAN-wifi pref-src=\
192.168.90.1 scope=10
/ip service
set telnet disabled=yes
set ftp disabled=yes
set ssh disabled=yes
/system clock
set time-zone-name=Europe/Samara
/system leds
add interface=WAN leds=user-led type=interface-status
/system logging
add disabled=yes topics=pppoe
add topics=system
add topics=critical
add topics=wireless
/system scheduler
add name="disable pppoe" on-event=\
"/interface pppoe-client disable pppoe-out1" policy=\
ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
start-date=feb/14/2019 start-time=05:00:20
add name="enable pppope" on-event="/interface pppoe-client enable pppoe-out1" \
policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
start-date=feb/14/2019 start-time=05:00:30
/tool graphing interface
add
Lags - this means that you can watch the video for 10 seconds, then you wait 20 seconds loading, etc."Lags" is not a good measurement. You should try to do some file transfer over wifi in 5GHz (not from TV, but some other way) and see what speed you get.
Also you can just monitor the interface speed in Winbox, when the movie is being watched. See what speed you get.
If the TV is modern, you should get good speeds. 4K movies are not that big, at most they run at some 80Mbit if it's a really big file.
didn't help.Try with hw-protection-mode=none and wmm-support=disabled
could you advise what options to use?ampdu-priorities=0,1,2,3,4,5,6,7.
What do you mean by wlan1? This is just the first time when I use Mikrotik.Do you have the same problems when using wlan1?
Yes, 2.4GHz. It's worth a try!What do you mean by wlan1? This is just the first time when I use Mikrotik.
if you mean 2.4 GHz Wi-Fi, then I do not use it.
I've tried. got better. but this is not enough to comfortably watch the videoYes, 2.4GHz. It's worth a try!What do you mean by wlan1? This is just the first time when I use Mikrotik.
if you mean 2.4 GHz Wi-Fi, then I do not use it.
You don't trust the auto negotiation? 100 Mbps is indeed potentially a trap with the half/full duplex mismatch./interface ethernet
set [ find default-name=ether1 ] name=WAN speed=100Mbps
set [ find default-name=ether2 ] speed=100Mbps
set [ find default-name=ether3 ] speed=100Mbps
set [ find default-name=ether4 ] speed=100Mbps
set [ find default-name=ether5 ] speed=100Mbps
channel width=20/40/80mhz-XXXX frequency=5260 -> you need 4 consecutive 20 MHz channels , and with XXXX you don't know which ones will be choosen.
/interface wireless
set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode \
band=5ghz-onlyac channel-width=20/40/80mhz-XXXX country=japan disabled=no \
disconnect-timeout=15s distance=indoors frequency=5260 frequency-mode=\
regulatory-domain hw-protection-mode=rts-cts hw-retries=10 mode=ap-bridge \
multicast-helper=disabled name=LAN-wfi5ghz on-fail-retry-time=1s \
radio-name=MikroTik5G ssid=MikroTik5G tx-power=25 tx-power-mode=\
all-rates-fixed wireless-protocol=802.11 wmm-support=enabled wps-mode=\
disabled
That is a red herring. The auto negotiation is actually enabled on those interfaces, but when it *would* be disabled the speed would be 100Mbps.You don't trust the auto negotiation? 100 Mbps is indeed potentially a trap with the half/full duplex mismatch./interface ethernet
set [ find default-name=ether1 ] name=WAN speed=100Mbps
set [ find default-name=ether2 ] speed=100Mbps
set [ find default-name=ether3 ] speed=100Mbps
set [ find default-name=ether4 ] speed=100Mbps
set [ find default-name=ether5 ] speed=100Mbps
Thanks Pe1chi. I'm not very fluent in the MKT CLI specifics, and the many defaults that are in action. And a "verbose" config then is too long to read all.That is a red herring. The auto negotiation is actually enabled on those interfaces, but when it *would* be disabled the speed would be 100Mbps.You don't trust the auto negotiation? 100 Mbps is indeed potentially a trap with the half/full duplex mismatch./interface ethernet
set [ find default-name=ether1 ] name=WAN speed=100Mbps
set [ find default-name=ether2 ] speed=100Mbps
set [ find default-name=ether3 ] speed=100Mbps
set [ find default-name=ether4 ] speed=100Mbps
set [ find default-name=ether5 ] speed=100Mbps
That output is actually the result of changed defaults in RouterOS over time, you can reset it to 1Gbps but it really would not matter as long as it is kept on auto negotiate.
(and it is, otherwise auto-negotiation=no would be in the parameterlist)
With WMM enabled NAS or TV could dominate airtime, when using high priorities on WLAN (no mangle rule needed). Frames send with lower priority could be lost or too delayed.wmm-support=enabled (still studying what the impact is) but how can it work without the QoS priority mangle rules. Everything is priority 0! No differentiation or special handling.
I would like to know how to use "high priorities on WLAN (no mangle rule needed)" , and get those high priorities without mangle rules. Would be very nice to have this.With WMM enabled NAS or TV could dominate airtime, when using high priorities on WLAN (no mangle rule needed). Frames send with lower priority could be lost or too delayed.wmm-support=enabled (still studying what the impact is) but how can it work without the QoS priority mangle rules. Everything is priority 0! No differentiation or special handling.
This is why it suggested to disable WMM.
This could explain why stream works when one side is connected by wire (priority 0 frames from this side because no mangle rules).
I would like to know how to use "high priorities on WLAN (no mangle rule needed)" , and get those high priorities without mangle rules.
Interesting!!! I have to dig deeper in this WMM. WMM priority when received over WLAN how is it marked? DSCP (TOS) or MKT priority?I would like to know how to use "high priorities on WLAN (no mangle rule needed)" , and get those high priorities without mangle rules.
This is how I understand it:
When AP and station are WMM enabled each can send (after negotiation) priority frames. So PC or TV could use more airtime.
The mikrotik (AP) WLAN will send priority frames when packets do carry internal priority information. For packets from "outside" interfaces priorities must be assigned by firewall-mangle or bridge-filters. But I would guess, frames received at the very same WLAN chip where forwarded to the same WLAN would also keep their WMM priority and sent accordingly.
Have you seen this article on the wiki: https://wiki.mikrotik.com/wiki/Manual:WMM?Interesting!!! I have to dig deeper in this WMM. WMM priority when received over WLAN how is it marked? DSCP (TOS) or MKT priority?
That's always a trade-off between bandwidth and latency. Sometimes you have to scarify one or the other for a specific traffic.If the priority is maintained in the MKT, then with the default config only priority=0 will use A-PMDU. Could be a performance disaster.
Yes I have seen that. It is well explained. But still I cannot formulate the answer to this statement ...." if I receive WMM negotiated traffic on a WLAN, and bridge forward it to the same or other WLAN in the same MKT will it still carry that WMM priority? ..."Have you seen this article on the wiki: https://wiki.mikrotik.com/wiki/Manual:WMM?Interesting!!! I have to dig deeper in this WMM. WMM priority when received over WLAN how is it marked? DSCP (TOS) or MKT priority?
I know this trade-off. But the implementation in MKT is not clear to me. Is the on/off selection per priority of the a-PMDU a selection between " 64 MSDU and 64 bit blockACK" or "no A-PMDU"? Or is this moderated or adaptive aggregation. Can we see what it does? ..... viewtopic.php?f=7&t=161295 (with links towards adaptive frame aggregation tests). Exemples of adaptive frame aggregation show typically 2 MSDU in one A-MSDU, 16 A-MSDU in one A-PMDU, but fluctuating like the MCS rate selection.That's always a trade-off between bandwidth and latency. Sometimes you have to scarify one or the other for a specific traffic.If the priority is maintained in the MKT, then with the default config only priority=0 will use A-PMDU. Could be a performance disaster.
Thanks Pe1chi, we are indeed quite off-topic here. 15 Mbps PC-AP-TV should indeed be no issue here with or without WMM.It is a bit of a pity that that article does not contain any examples, and that the "by default usually wanted" configuration of "take priority from DSCP" is not included in the default config of RouterOS (as it is on almost any other manufacturer's WiFi equipment).
That can make MikroTik APs look bad when compared to others...
There also is no checkmark for applying this default priority on the Wireless interface config page, next to the "WMM support" setting, as there is for some other config like "clamp TCP MSS".
I normally have this in my mangle config:
/ip firewall mangle
add action=set-priority chain=postrouting comment="From dscp high 3 bits" \
new-priority=from-dscp-high-3-bits
and of course:
/interface wireless
set [ find default-name=wlan1 ] wmm-support=enabled
That being said, priorities should not be the reason why the original problem that was being presented here is present. It would
help e.g. when you are doing file transfers and VoIP over the same link, but video usually has enough buffering to overcome temporary
problems like other data going before.
WMM priority when received over WLAN how is it marked? DSCP (TOS) or MKT priority?
Sorry, for still off-topic. I would prefer a default "take priority from DSCP" by RFC8325, not by "poor-man's" high-3-bits.It is a bit of a pity that that article does not contain any examples, and that the "by default usually wanted" configuration of "take priority from DSCP" is not included in the default config of RouterOS ... new-priority=from-dscp-high-3-bits
That setting is only available in ROS7, if you are having troubles finding it. For ROS6.x you can manually select a non-dfs channel and it would do the trick.I had similar problem.
I have OLED55C9 which worked great before I changed my router to hap ac2.
After setup i noticed some problems with films playback through dlna server. (btw it also affects to AirPlay which I noticed later)
I tried all the options from this thread but nothing helped.
And then I just started to messing with different settings and... skip-dfs-channels=all did the trick.
Also I checked my suspicious on Asus ax58u and i'v got similar behavior.
Seems like LG isn't friends with dfs. But this is certainly not a problem of MikroTik.
Actually no. I have it in 6.47.That setting is only available in ROS7, if you are having troubles finding it. For ROS6.x you can manually select a non-dfs channel and it would do the trick.
It is in ROS 6 (recently)
That setting is only available in ROS7, if you are having troubles finding it. For ROS6.x you can manually select a non-dfs channel and it would do the trick.
You are running an rather old version of RouterOS. You should upgrade to latest "long term" 6.45.9 or latest stable 6.47.# may/20/2020 16:37:30 by RouterOS 6.43.11