lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

63
active users

#mikrotik

0 posts0 participants0 posts today

💻 HomeLab & Mikrotik RB5009 💻

Do you really need the missing serial console for remote out-of-band managemnt, like most of their devices?

Well, I had one and then returned it for that reason. I've been considering it again, but not without the serial connection... so a little digging around and I found some PCB images and quick info on the OpenWRT site.

Then decided to add those bits to a fork for personal tracking... for those interested in the PCB photos and quick-doc:

- github.com/em-winterschon/open

Clearly still a WIP, and would need to re-purchase the device to test it out... so perhaps in the next few months that will happen.

Some light discussion: forum.openwrt.org/t/add-suppor

Tonight I had to reboot the switch again. Performance had dropped to ridiculous levels - at most 100 Mbit/sec on all devices, but actually even less. It’s not the first time this has happened with this device, and it’s strange because MikroTik switches are usually reliable, even with very long uptimes. I’ll try to figure it out, but the logs don’t show anything unusual

Hey #networking #mikrotik specialists!

I'm thinking of checking out exposing my local services to the Web using github.com/fatedier/frp

Let's say I want to expose a HTTP server running on a Pi. I would put that Pi on a different VLAN for security. Can I setup my local communication in a way that I could SSH into that Pi from my laptop in another VLAN, but that Pi would not be able to connect in any way to other machines in my local network?

What is the industry standard way to handle this?

GitHubGitHub - fatedier/frp: A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet. - fatedier/frp

Last night I was amazed that even the most remote devices remained connected to the 'small' MikroTik CAP AC. This morning one of the devices disconnected and couldn't reconnect. I conducted a brief survey (using WifiMan on the Pixel 7 with GrapheneOS, disabling the polling frequency limit for wifi from developer options) and indeed, the difference compared to the Ruckus is quite marked. At the limits of the house, even though the Ruckus shows a weak signal, the devices can still communicate well without packet loss. The MikroTik signal is definitely weaker and more unstable. I expected this for two reasons: I'm comparing two devices from completely different ranges, from totally different generations, and with significantly different prices. In fact, for the price of one Ruckus, you could buy about 12 or 13 CAP AC units. So the question I now ask myself is: was it more sensible to keep two separate access points in two key areas of the house (as I did years ago) or a central Ruckus? I will answer this once I get a more recent generation MikroTik for a client. That will be a clearer test. Ruckus excels in particularly crowded environments, which is certainly not my home.

Today, I decided to bring one of my MikroTik access points out of the closet, a CAP AC. I used two of them in my home for almost 4 years with no major issues before switching to Omada WIFI6 devices. Later on, I switched to Ruckus, and one of them is now my primary home access point. I managed to reduce from two access points to just one. While one of the Omada units lost signal in far corners of the house, the Ruckus remained stable.

Meanwhile, MikroTik has started supporting wave2, so I decided to give it a test. I removed OpenWRT (which I had installed for testing purposes) and reinstalled RouterOS 7.18. After setting it all up and turning off the Ruckus, I noticed slightly lower coverage compared to the Ruckus, but the stability was comparable, with all the benefits of RouterOS. Definitely a nice surprise, and for me, MikroTik remains a genuinely honest company that continues to update old devices for a long time without imposing artificial limits or paywalls. I use their devices a lot, even for clients, and everyone is very satisfied.

Ok, if anyone can solve my little #selfhosting power problem, it's the people connected to me on Mastodon. Feel free to boost.

I just turned off a #Juniper switch that was pulling like 200W and replaced it with a #Mikrotik switch that pulls 20W. The Juniper had one benefit that the Mikrotik lacks, and that's dual power supply. Mikrotiks just have one 24V 1.5A DC in.

If I want to buy 2 power supplies and connect them to my 2 UPSes and achieve some measure of redundancy, is it possible? What's the name of the device and is it expensive? I've drawn a picture to help.

If this is like past tech questions I've asked on Mastodon, I'm gonna get 10 Alibaba links to a "bivalent multivolt snargleprong" or some shit I've never heard of, and everyone else has like 3 in their top desk drawer.

In today's #fuckshit with #mikrotik. Hardware is kinda Fire.. The way you guys do shit is weird! At the very least this shit is not for rest of us. VyOS software router didn't take this much brain power to get going. I finally got my network moved over to it. I needed to add bridge, vlans, vlan interfaces, trunk ports in bridges, add interfaces and vlan interfaces to bridges, add interfaces to interfaces lists to allow firewalls shit, add address pools, then dhcp servers, and then add networks ( which are not vlans). I still have not set up PBR. And before you come at me with this, "do you even network bro bullshit"!! NO! I don't.. I'm not sure this fucking thing networks without you getting drugged in in a foreign country for your kidneys!!

Now don't get me wrong( or get me all the way wrong)!!! The software is a POS 🤣 It's powerful, I'm sure! You just need to kill a baby unicorn goat! Then it fucks with ya!

And now for something lighter:

Trying out a minimal setup that serves most of my requirements for #SelfHosting

From left to right:
1) WD Red Plus 4TB drive
2) Raspberry Pi 4 4GB, running openmediavault
3) MikroTik L009 router
4) Raspberry Pi 4 8GB running docker containers
5) Raspberry Pi 4 2GB running Pi-hole and caddy

Not shown: another 4TB drive for external backup (the 1 in 3-2-1).

Power consumption 105W, plus 24W more when running external backup.

Looks like @mikrotik have got problems... Trying to work out why some of my home kit wasn't accessible and I've just been called by a customer with the same problem. The forum's generating a 500, so no help there...
Turns out their dynamic DNS service is broken. A quick fix to hard code the external IPs in DNS and we're both running again.
#itsalwaysdns #mikrotik #routeros

Continued thread

Just got this #mikrotik CRS304-4XG-IN 4x10G copper switch. It’s the only reasonably priced multi 10G switch I’m aware of. While 2.5G soho switches are cheap now, 10G is still a rarity. This has no active cooling but most of the case is a massive heatsink.
It will connect a 10G uplink, 10G thunderbolt notebook nic and 2x2.5G on board nics in a n100 microserver. #homelab #networking

Continued thread

It will be interesting to see which of these two rule sets end up doing more. I already had this portscanner ruleset. Basically, if you come to my router and try to make a TCP connection on some well-known port that I don't support, then BANG! instant block. If you're trying port 3306 (MySQL) over the WAN, I know you're not one of my legit users, you're just probing for stuff. So an instant 7-day ban. I reset the stats on that rule about the same time I installed the Mikrotik block rule. It's blocking more.

There's the list of ports I test and block on.
#router #mikrotik #selfhost #selfhosting #networking #firewall