Community discussions

MikroTik App
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:03 pm

I have a site which I manage remotely over the internet. (INPUT chain has a blanket allow rule from src: my static IP address for simplicity).

This site was running a hAP ac2, however the users - heavy gamers - were reporting 20-30 second drops in connectivity.

Whenever I tried to connect to the hAP via winbox using the public IP address it would also trigger a lock up of the router.

I can connect via SSH without issue, and I can generate a /system/sup-output file, but I can't scp this file off the device on to my computer - it hangs at 0%.

My config is extremely basic (included below), so I took the drastic action of getting a hEX S, updating it to 7.2, then moving the config over.

It exhibits the same problem.

Where do I start when I can't get a supout.rif ?
# apr/09/2022 13:15:48 by RouterOS 7.2
# software id = YEPP-2C2D
#
# model = RBD52G-5HacD2HnD
# serial number = A6490AD14FEE
/interface ethernet
set [ find default-name=ether3 ] disabled=yes
set [ find default-name=ether4 ] disabled=yes
set [ find default-name=ether5 ] disabled=yes
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX distance=indoors frequency=auto installation=indoor mode=ap-bridge ssid=\
    MikroTik-AA6BEF wireless-protocol=802.11
set [ find default-name=wlan2 ] band=5ghz-a/n/ac channel-width=20/40/80mhz-XXXX distance=indoors frequency=auto installation=indoor mode=ap-bridge ssid=\
    MikroTik-AA6BF0 wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
add comment=vpn name=VPN
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip ipsec profile
set [ find default=yes ] dh-group=modp2048 enc-algorithm=aes-256 hash-algorithm=sha256 nat-traversal=no
/ip ipsec proposal
set [ find default=yes ] auth-algorithms=sha256 enc-algorithms=aes-256-cbc,aes-256-gcm pfs-group=none
/ip pool
add name=dhcp ranges=192.168.18.2-192.168.18.254
/ip dhcp-server
add address-pool=dhcp interface=ether2 lease-time=1w name=defconf
/queue type
add cake-atm=ptm cake-diffserv=besteffort cake-nat=yes cake-overhead=22 cake-overhead-scheme=bridged-ptm,via-ethernet cake-rtt=50ms kind=cake name=cake-default
add cake-atm=ptm cake-bandwidth=36.0Mbps cake-diffserv=besteffort cake-nat=yes cake-overhead=22 cake-overhead-scheme=bridged-ptm,via-ethernet cake-rtt=50ms \
    kind=cake name=cake-up
add cake-atm=ptm cake-bandwidth=90.0Mbps cake-diffserv=besteffort cake-nat=yes cake-overhead=22 cake-overhead-scheme=bridged-ptm,via-ethernet cake-rtt=50ms \
    kind=cake name=cake-down
/queue simple
add bucket-size=0.001/0.001 name=cake queue=cake-down/cake-up target=ether1 total-queue=cake-default
/routing table
add fib name=""
/ip neighbor discovery-settings
set discover-interface-list=LAN
/ip settings
set max-neighbor-entries=8192
/ipv6 settings
set max-neighbor-entries=8192
/interface list member
add comment=defconf interface=ether1 list=WAN
add interface=ether2 list=LAN
/interface ovpn-server server
set auth=sha1,md5
/ip address
add address=192.168.18.1/24 interface=ether2 network=192.168.18.0
add address=192.168.1.100/24 comment="modem: access to modem" disabled=yes interface=ether1 network=192.168.1.0
/ip dhcp-client
add comment=defconf interface=ether1 use-peer-dns=no
/ip dhcp-server lease
add address=192.168.18.2 client-id=1:64:eb:8c:59:75:3 mac-address=64:EB:8C:59:75:03 server=defconf
/ip dhcp-server network
add address=192.168.18.0/24 comment=defconf dns-server=192.168.18.1 gateway=192.168.18.1 netmask=24
/ip dns
set allow-remote-requests=yes cache-size=20480KiB max-concurrent-queries=1000 max-concurrent-tcp-sessions=200 query-server-timeout=1s query-total-timeout=5s \
    servers=1.1.1.1 verify-doh-cert=yes
/ip firewall address-list
add address=x.x.x.a disabled=yes list=allowed-dns
add address=x.x.x.b disabled=yes list=allowed-dns
add address=x.x.x.c disabled=yes list=allowed-dns
add address=x.x.x.d list=allowed-dns
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=accept chain=input comment="wan: accept from blurrybird" in-interface-list=WAN log=yes log-prefix=blurrybird src-address=x.x.x.e
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat comment="dns: dst-nat all dns to router" dst-address-list=!allowed-dns dst-port=53 in-interface-list=LAN protocol=udp \
    to-addresses=192.168.18.1
/ip ssh
set forwarding-enabled=both
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=ether2 type=internal
add interface=ether1 type=external
/ipv6 address
add eui-64=yes from-pool=dhcp6 interface=ether2
add address=fd3e:9134:9285::1 comment="ULA: fd3e:9134:9285::/48" interface=ether2
/ipv6 dhcp-client
add add-default-route=yes interface=ether1 pool-name=dhcp6 request=address,prefix use-peer-dns=no
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
add address=::224.0.0.0/100 comment="defconf: other" list=bad_ipv6
add address=::127.0.0.0/104 comment="defconf: other" list=bad_ipv6
add address=::/104 comment="defconf: other" list=bad_ipv6
add address=::255.0.0.0/104 comment="defconf: other" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" port=33434-33534 protocol=udp
add action=accept chain=input comment="defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp src-address=fe80::/10
add action=drop chain=input comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=drop chain=forward comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
/ipv6 nd
set [ find default=yes ] advertise-dns=no interface=ether2 other-configuration=yes ra-interval=5s-10s
/snmp
set enabled=yes
/system clock
set time-zone-name=Australia/Melbourne
/system identity
set name=Something
/system logging
add disabled=yes topics=dhcp
/system ntp client
set enabled=yes
/system ntp client servers
add address=time.cloudflare.com
/system routerboard settings
set auto-upgrade=yes cpu-frequency=716MHz
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Last edited by blurrybird on Sat Apr 09, 2022 1:24 pm, edited 1 time in total.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:08 pm

I have thousand on hAP ac2 installed on my clients, all on 6.44.6 or 6.46.8 or 6.47.10 or 6.48.6, and never have problem,
why you do not use a long-term version, but use just-out version?
What have 7.2 for hAP ac2 that 6.48.6 can not do?
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:23 pm

What have 7.2 for hAP ac2 that 6.48.6 can not do?
How can we run Wireguard on 6.48.6 without investing in other external hardware ?
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:23 pm

What have 7.2 for hAP ac2 that 6.48.6 can not do?
cake QoS.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:24 pm

@fragtion
I'm talking about OP export, no trace of wireguard...
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:26 pm

no trace of wireguard
I disabled and deleted my wireguard config (which I was using) while trying to debug this problem.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:29 pm

What have 7.2 for hAP ac2 that 6.48.6 can not do?
cake QoS.
Ah, really indispensable
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 1:29 pm

no trace of wireguard
I disabled and deleted my wireguard config (which I was using) while trying to debug this problem.
Ok, that's worth it
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 2:05 pm

Only hoping, that the post counter will go past 9999.
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 2:28 pm

Back on topic..
@OP I did a thorough check through your cfg and can't find any issues with it. Maybe someone else can spot something I didn't?
I would suggest disabling cake and rebooting for a start, to see if maybe that is interfering somehow? as it is a relatively newer queueing method which has been known to cause some instabilities but my exposure to that is very limited.
Otherwise you could try disabling some firewall drop rules? You say you're connecting from a static IP... if that's the allowed WAN IP then you shouldn't be having these problems.
Router itself shouldn't be locking up from such config , let alone two separate routers with the same error-free config. Are you sure it isn't the WAN connection? Could you try lowering the MTU?
And this one of course goes without saying, but make sure you're using latest Winbox.. You could try connect from a different PC/network using latest winbox?
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sat Apr 09, 2022 3:21 pm

Router itself shouldn't be locking up from such config , let alone two separate routers with the same error-free config. Are you sure it isn't the WAN connection? Could you try lowering the MTU?
I agree, I also tried 7.1.5 with the same symptoms, and I managed to get a teamviewer connection to a PC in the LAN segment and the crashing / instability happens when connecting via Winbox in the LAN too.

Latest winbox (3.35).
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 1:27 pm

Back on topic..
[…]
I would suggest disabling cake and rebooting for a start, to see if maybe that is interfering somehow? as it is a relatively newer queueing method which has been known to cause some instabilities but my exposure to that is very limited.
Thanks for the suggestion here. It is early days but I’m hearing of success with this.

The key was rebooting after disabling cake - I tried to repeatedly disable it and test but there was no difference.

I guess the way tc is integrated at the kernel level, it needs a reboot to flush out?
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 1:44 pm

I'm experimenting with cake for the first time, and also seeing random connection loss while it's enabled (seems to occur mostly while traffic is peaking, eg on speedtest). It's working great except for while connection locks out. If I leave it for a few minutes, pings resume, but logging in via winbox (burst of traffic) locks the connection out again for several minutes.

So we can be basically certain at this point that it's the cake which is causing your problems because I'm seeing the same symptoms. There seems to be a bug unless we've configured something incorrectly. Very unfortunate as cake seems pretty awesome if it works properly. I presume MikroTik are aware of this issue by now ? Perhaps log a support ticket referencing this thread

Edit: I can easily reproduce/trigger the issue by doing a bwtest (Protocol: TCP, Direction: SEND) from the router with cake configured. As soon as it tries to send the traffic, ping timeouts occur until the queue is disabled. It happens after rebooting the router also, so it's definitely some kind of bug. Doesn't occur with fq_codel, so it's specifically affecting cake.
 
jmszuch1
just joined
Posts: 10
Joined: Fri Oct 19, 2018 10:21 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 4:18 pm

Saw the post over in the cake thread (viewtopic.php?p=925547#p925547) and just wanted to add my experience. I didn't experience any lockups or loss of connection during the testing I did in the other thread, although maybe I just wasn't pushing the router hard enough. I'm running a RB5009 with cake setup like this:
/queue type
add cake-bandwidth=10.0Mbps cake-diffserv=diffserv4 cake-memlimit=32.0MiB \
    cake-mpu=64 cake-nat=yes cake-overhead=18 cake-overhead-scheme=docsis kind=\
    cake name=cake-up
add cake-bandwidth=105.0Mbps cake-diffserv=diffserv4 cake-memlimit=32.0MiB \
    cake-mpu=64 cake-nat=yes cake-overhead=18 cake-overhead-scheme=docsis kind=\
    cake name=cake-down
/queue simple
add name=Spectrum queue=cake-up/cake-down target=\
    192.168.88.0/24,2600:6c4a:5a00:56a::/64,192.168.5.0/24
For the bandwidth test, were you running that to another Mikrotik on the local network? Or something else? I'd definitely like to see if I can trigger the problem on my router as well.
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 4:22 pm

For the bandwidth test, were you running that to another Mikrotik on the local network? Or something else? I'd definitely like to see if I can trigger the problem on my router as well.
I'm also on a 5009 but I'm seeing the same on a 4011. The bandwidth test is being done through the PPPoE WAN interface (where cake is implemented) to a CHR located on the internet (accessible via same WAN interface).
As soon as I start the TCP SEND on the bwtest, I lose WAN access from that router entirely until the queue is disabled. Occurs when using your config template as well.

On an unnrelated note, I wanted to try fq_codel as an alternative, but I seem to be having an issue with upload speeds when using fq_codel. A 1Gbit connection is peaking out at about 450mbps upstream. So back to my regular queue trees it is then I guess.
Last edited by fragtion on Sun Apr 10, 2022 5:05 pm, edited 1 time in total.
 
jmszuch1
just joined
Posts: 10
Joined: Fri Oct 19, 2018 10:21 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 5:03 pm

So I think I was able to duplicate that issue. Did a quick and dirty test by setting up the Mikrotik Bandwidth Test app on a spare Windows computer and then did the TCP Send from my RB5009 while running a ping to the routers IP (192.168.88.1). The ping starts failing shortly after the test is started and resumes as soon as I disable the simple queue that has cake attached to it. The ping then remains working when I re-enable the queue.

Here's a video I made of the test for reference: https://youtu.be/OMxxVsrLbpI
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 5:29 pm

Good, no baking for me, so not to worry, but I did wonder why the OP thought it was a good idea to have an open door to his router via his remote public IP???
(Not a big fan upnp if it can be avoided as well.)

The one thing I didnt understand is the reason and function of this rule....
add action=dst-nat chain=dstnat comment="dns: dst-nat all dns to router" dst-address-list=!allowed-dns dst-port=53 in-interface-list=LAN protocol=udp \
to-addresses=192.168.18.1
 
jmszuch1
just joined
Posts: 10
Joined: Fri Oct 19, 2018 10:21 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Sun Apr 10, 2022 8:35 pm

I did a little more testing with some routers I can winbox into over a SSTP connection and did experience some connection instability as described in this thread. It doesn't look like the router actually crashes; but it seems to stop accepting connections for a time. I'm going to see if I can consistently duplicate the issue and then gather some support files.

I'd definitely recommend anyone else in this thread who are experiencing this do the same and open a ticket with Mikrotik so they can be made aware, just in case they aren't already. Pictures or a video (like I made) would probably help speed up them duplicating the problem.

So far, I haven't seen the same issue on my own router with fq_codel enabled on a simple queue. Although that's a bummer if the performance is a bit more limited as fragtion mentioned.
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Mon Apr 11, 2022 3:04 am

Funny you mention the RB5009 - that is what I use on a 1000/50 connection with cake configured and running RouterOS 7.2.

Perhaps I'm not loading it up as hard as this other site is loading their 100/40 connection, but I wasn't experiencing instability.

I've disabled cake on the rb5009 for now to be safe.
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Wed Apr 13, 2022 3:54 pm

lmao ok - definitely cake.

Re-enabling the queue caused my RB5009 to completely lock up until restarted.
 
jmszuch1
just joined
Posts: 10
Joined: Fri Oct 19, 2018 10:21 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Thu Apr 14, 2022 12:42 am

Yeah, so far, I've been able to consistently lock up my RB5009 using the bandwidth test fragtion mentioned and a simple queue with cake attached. In my case it doesn't seem to be a full lock up though, I'm able to remain connected in winbox if I'm running it from a computer directly connected to the router. Although I have to be connected using the MAC address in order the connection to maintain itself. Happens on the 7.3 beta that was just released as well.

I generated a couple supout files while the router was refusing connections and filed a ticket with Mikrotik. Hopefully they can replicate and pinpoint the issue.
 
kikikaka
just joined
Posts: 9
Joined: Sun Jul 03, 2011 9:50 am

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox  [SOLVED]

Thu Apr 14, 2022 8:26 pm

I have similar experience too. When using cake in simple queue, the connection lock up for a while when doing a speed test.
/queue/simple add bucket-size=0.01/0.01  max-limit=960M/960M name=queue-cake queue=\
    cake-ul/cake-dl target=bridge
I found that if I set only the target , it always have problem.
If I also set the dst , for example, , dst=ether8 (the WAN interface), it seems works fine. (at least tested 1 to 2 days of general use, although I finally change back to fq-codel)
/queue/simple add bucket-size=0.01/0.01  dst=ether8 max-limit=960M/960M name=queue-cake queue=\
    cake-ul/cake-dl target=bridge
PS: I am using RB5009
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Thu Apr 14, 2022 8:51 pm

I found that if I set only the target , it always have problem.
If I also set the dst , for example, , dst=ether8 (the WAN interface), it seems works fine. (at least tested 1 to 2 days of general use, although I finally change back to fq-codel)
Great find! Testing this out now on my RB5009 as I really want to try cake some more (seems incredibly tasty so far! Generally way more effective & efficient than all other queues in ROS that I've tried at least) - but this bug is obviously a major impediment to actually using it.

This won't technically fix the underlying bug (eg: when using the bwtest method, as that takes place from the router doing the cake). But it conveniently bypasses it, as wan traffic to/from the router *itself* is no longer affected by the simple queue. This is also good news from a remote wan management perspective (ie OP/@bluebird's initial approach) as we won't get locked out of the router remotely anymore from this, unless the CPU/kernel somehow gets hit & we land up with cake in our face 😂

If it stabilizes all lan<->wan traffic then it's going to be a great workaround for us in the meanwhile. Hopefully MikroTik will fix the issue soon but for those of us who are more eager to try this out, an effective workaround is a welcome icing for some freshly baked goodness! 😁

P.S.: @anav I generally don't consider myself much of a baker either to be honest, but I strongly suggest indulging in a slice if you haven't - you'll probably not regret it !

Update @t+2h: Looking pretty solid so far, I think this is good.
 
dtaht
Member Candidate
Member Candidate
Posts: 209
Joined: Sat Aug 03, 2013 5:46 am

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Mon Apr 18, 2022 3:47 am

I don't "get" why anyone needs to set a bucket when using cake. Cake has its own shaper.

Setting it on the bridge is usually the wrong thing. You want to set it on the actual physical interface you are trying to shape, so it sees all traffic.

Per customer shaping is different, but elided here.
 
blurrybird
newbie
Topic Author
Posts: 38
Joined: Sun Jan 19, 2020 12:25 pm

Re: 7.2 - Router(s) Lock Up When Connecting via Winbox

Tue Apr 19, 2022 4:26 am

I don't "get" why anyone needs to set a bucket when using cake. Cake has its own shaper.
It's a requirement of the mikrotik QoS interface. Not setting any value here just defaults to a bucket size of 0.1.

Who is online

Users browsing this forum: No registered users and 25 guests