The official Mikrotik router thread

When you leave devices and forget about them, this happens.

Screenshot 2022-12-31 at 20.48.31.png

Good to see my power backup on these work. Time to do some updates and reconfigure networking on them.
 
When you leave devices and forget about them, this happens.

View attachment 1450455

Good to see my power backup on these work. Time to do some updates and reconfigure networking on them.
All yours? My IP->Neighbors list has about 6 or 7 Tiks on Frogfoot around my area, as Frogfoot doesn’t do client isolation on their network.
 
I am not at home at the moment to show screenshots but I can see some devices in the Teraco DC via my Cybersmart Mikrotik
I remember on the old Internet Solutions network you could see hundreds of tiks. I forgot the precise amount but somewhere around 500? Anyways, you could run a 1 gig VPN between two tiks. Get a 10MB service in Bloem and another in Durbs for peanuts and then run a 1 Gig VPN between the two.

And that is why they went TITSUPS. No recon.
 
FNOs that don't do client isolation should hang their heads in shame. If they cannot do that imagine what else they cock up...
Oh I know, take a look at the Frogfoot PE thread to see what we have to deal with on the daily:p

1672604015859.png
 
Last edited:
Busy playing around with using Traffic Monitor to route traffic intelligently depending on WAN usage % using some ideas here. PCC doesn't work well with asymmetrical connections, unfortunately.

Slide 1 (mikrotik.com)
 
Busy playing around with using Traffic Monitor to route traffic intelligently depending on WAN usage % using some ideas here. PCC doesn't work well with asymmetrical connections, unfortunately.

Slide 1 (mikrotik.com)
In the ADSL days this was an issue as requests to sites came from two/more different public IP's-not sure I that is still an issue these days
 
In the ADSL days this was an issue as requests to sites came from two/more different public IP's-not sure I that is still an issue these days
You still need to (generally) clamp your connections to take the same return paths to avoid constant IP switching issues
 
You still need to (generally) clamp your connections to take the same return paths to avoid constant IP switching issues
Ye but per a connection also causes issues on some sites with auth, so one ends up doing it per an internal host eventually :ROFL:

Hub and spoke like @r00igev@@r mentioned is the way, 2X wireguard tunnels upstream, one over each connection
 
In the ADSL days this was an issue as requests to sites came from two/more different public IP's-not sure I that is still an issue these days
I haven't picked up any issues running with PCC but when doing it the manual way, you need some mangle rules to 'sticky' the connections until they time out. Been running this for a bit now and seems to be working quite well. But only time will tell whether I'll stick with it, as I like changing it up quite often.
 
Top
Sign up to the MyBroadband newsletter
X