I don’t use Winbox as I don’t use Windows. I’ve been using the GUI and the CLI for the Mikrotik. I think Winbox and the GUI have things in the same places. But I don’t see the settings available in the GUI actually.
I was doing these setting changes through the CLI. The command in the CLI are:-
To see the current settings:- /ip/firewall/connection/tracking/print
To make the changes:- /ip/firewall/connection/tracking/set udp-timeout=40s
There’s a fair amount of stuff that is in winbox that isn’t in the webgui.
If you’re on linux and don’t mind using snaps: there’s a wine+winbox package in the snapstore.
ah that seemed to work for now fingers crossed thank you so much now I can really see how many nodes I can load on this thing I have the same router as you the rb 5009 how many nodes are you able to push with it?
udp-timeout (time; Default: 10s) Specifies the timeout for udp connections that has seen packets in one direction udp-stream-timeout (time; Default: 3m) Specifies the timeout of udp connections that has seen packets in both directions
ahh I spoke too soon, damn that didn’t seem to work I spoke too soon my internet connection still bogs down and cuts in and out IDK what the issue may be and I’m only running 150 nodes
But that’s more to do with my 80/25 ADSL than number of connections. I will be trying to squeeze another few on. But I’ve noticed bandwidth used by those nodes is creeping up over the last couple of days so maybe not.
ah ok yea I am new to mikrotik routers and dont really know how to set any of that up and would have to do some research one guy in discord was saying he needed to hire a guy on fiverr to setup his network for him maybe I should go that route lol?
To share my findings thus far with the users of this thread.
It appears through trial and error that the answer to scaling a home setup is not by getting the biggest router that you can find but by getting multiple small decent performing routers each of which is assigned a static ip of its own.
This scales well, as you grow your rig you can add routers and IP’s until you run out of bandwidth and need a second line, then a 3rd then a psych eval.
I hope this saves some of you time in figuring out how to scale, it was a bumpy ride for me.
But of course we are waiting on new node sizes and many nodes may rapidly become a thing of the past.
Hold off before you call your ISP
I have the fiber to my ONT which then goes to a 2.5Gbps unmanaged switch.
(Needed to downgrade from 5Gbps cause they don’t offer statics with that)
So each router connects to the switch.
This is something I am trying to figure out.
My CCR2116 can only comfortably run 600 Nodes, it is idling with that many, 15GB of free RAM while using at most 20% CPU.
At 700 nodes it is in pretty much in the same state but sporadically drops to 5Mbps for short bursts. Maybe 2 or 3 minutes.
Nothing is stressed and I have loads of bandwidth available.
I suspect it is happening at my ISP side, any ideas?
The smaller routers can run at 90% all day 24/7 with zero troubles even while the big guy gets throttled.
This makes me more convinced it is a limit reached per IP.
You know this sounds like last century garbage collection going on in memory. The router decides it needs to collect together all the small bits of memory no longer used into larger blocks and maybe shift some around.
During that time everything else has to work around that.
Wonder if you could search the web for a fix to that. Like fixing some tables, or fixing packet memory to max sized packet. Maybe max packet size that the router handles. 1536 if I recall correctly is a standard for max packet size from some time ago.