I don’t think temperature is an issue. I have one deployed in a room full of industrial ovens. It’s showing 71C and it’s fine. And no, you can’t touch it because it’s so hot. But it’s been like that for about 6 months, so I think it’s fine. And even if it dies, it’s cheap enough to put another one in.

I’m using the RB4011 with the VM Business Hub but in modem mode it will be the same. If you look in quickset, it should be set to Router and Address Acquisition should be set to Automatic. That should be all you need.

Again, what you suggest ie. the ISP using DHCP to give your router an IP address should work on the default configuration if you plug the RJ45 from the ISP connection (modem etc.) into the WAN port with address acquisition set to automatic. I've done a lot of Mikrotik training and I don't think that...

There is no DHCP server running. So windows is assigning you an APIPA address in the 179.254.x.x range.

It sounds like the AP needs a reboot at the very least. Have you tried powering it down and turning it back on again?

I’m pretty sure you don’t need that DHCP client. You don’t say what device you have but quite literally every Mikrotik device I’ve ever used has just worked straight out of the box with maybe just a PPPoE username and password to get a connection to a modem. So my first advice is put it back to fact...

The firewall on the LHG will stop you doing anything more than pinging it. But I didn’t think you wanted to go from the Draytek to the LHG, you want to pass traffic from the LHG to the Draytek. Does the Draytek know it’s supposed to be using the secondary WAN I.e. the LHG? If it doesn’t, it may neve...

Also, in RouterOS there are DHCP clients and DHCP servers. A DHCP client on its own won’t help in your configuration, as far as I’m aware. In your configuration you can see you have a DHCP server allocation pool from 192.168.88.10-254, but then you’re adding IP addresses and gateways on the 192.168....

I don’t have an LHG but I do have an SXT LTE which is a very similar device. In the factory configuration the RouterOS should have a DHCP server running on IP address 192.168.88.1 and handing out IP addresses from 192.168.88.254 downwards on the 192.168.88.x/24. It should just work once you enter th...

The challenge for most users now is they don’t appreciate the value in the RouterOS licence. The licence is part of the value of the device. It has a cost. Repairing the hardware is fine, and I don’t see any reason why someone shouldn’t repair their own hardware. The software is (and always will be)...

Is it fair to attack Mikrotik support because you repaired a device yourself and now it doesn’t work? I’m not sure how warranty works in the Ukraine but in the UK the moment you significantly modify a device the warranty and support on it is invalidated. If the device was still under warranty you sh...

We have 3 4011’s without WLAN and one with. I’m about to buy another one with WLAN. While they do run a bit hot, the fact is that the metal case is used as a heat sink and it gets warm. Not so hot you can’t touch it, but hotter than most users are used to. I can’t talk about reliability over 3 month...

And if you want something REALLY fast just built your own x86 machine stuffed full of PCIe network cards and install RouterOS on it. One the best, and most under-rated features of Mikrotik is they RouterOS separately so you can install it on your own hardware.

It makes the wired LAN ports act like a single switch, including the wireless LAN ports. So it makes it work the way you would expect if you came from a consumer router.

We have 4 of these in use at the moment. All are running with the cases hot to the touch. They're really hot. But they seem to be running fine. We have ours rack-mounted and this is definitely contributing to the we high temperatures. The RJ45 SFP+ converter is genuinely hot enough to burn skin thou...