RB3011 as home router

I want to replace the old TP-LINK router for a RB3011.

The setup is simple:

  1. ether1 is WAN
  2. ether2 is internet connection for solarpanels
  3. ether3 and ether4 not used
  4. ether5 is for management
  5. ether6 - ether10 is bridged for home network

IPv6 and all services except winbox are disabled. Default firewall.

With this setup I can make this a drop-in replacement for the current router.

Is there anything I can do to make this setup better/saver?

There is a firewall rule to drop all input not from LAN. If I want to use ether5 for management can I then remove the bridge from this LAN?

There is a lot of information to use VLAN's for IPv4. If I setup VLAN's using IPv4 how difficult is it to add IPv6?

Thanks

rb3011.rsc (7.3 KB)

The rb3011 has two switch chips; one for ports 1-5 and the other for 6-10. Any traffic going from ports 6-10 to your WAN on port 1 will have to go via the CPU, potentially limiting speeds (though with fasttrack enabled that shouldn't be an issue). Something to consider when planning ports at least.

Well again, as always i'd recommend u buy a rb5009ug and buy a rack-mount kit, because its a newer architecture, its faster, it has a 10gig pipe to the cpu, 1 gigabyte of flash so the updates will last forever, and its passively cooled and it has a 10gig sfp+ cage on it built in (instead of the rb3011 1.25gigabit sfp cage), the rb3011 should be the same price but worse in every single aspect unless you specifically need 10 ports.

If its not too late buy a rb5009ug, Rb3011 will get the job done but there's downsides, not a lot of flash storage, it will suffice for a while but don't count on doing containers on it, two cores = people complain about it bottle necking a gigabit connection (https://www.reddit.com/r/mikrotik/comments/ylmaw9/mirkotik_rb3011_in_2022/), it has a screen which i don't think as of ROS7 don't work (*need to make sure about that one i read somewhere on the forum here that touchscreens support got discontinued and don't work anymore).

That is true, but if this is for a home with a single ip address, won't all traffic to/from the WAN have to go through the CPU anyway?

I think that putting the LAN on the second switch chip at least gives the possibility of allowing L2 stuff on ether6-10 to be handled by the switch chip. However, the QCA8337 switch chip isn't supported by ROS vlan-aware bridge if you want HW switching, you will need to use the /iterface ethernet switch section (see Other devices with a built-in switch chip) And that will make supporting vlans a bit more complex (well at least less general) than on newer hardware.

I assume that hanshendriks didn't buy the RB3011 new recently.

As far as vlans on ipv6 I am not aware of anything that vlans that would require different than having multiple individual interfaces (per port) would require. E.g. you will probably need a /64 for each LAN subnet/broadcast domain reguardless of whether vlans or separate port based interfaces are used. See IPv6 on only one vlan?, IPv6 routing using VLANs and IPV6 and vlans (note this last link was on an RB5009 which does have HW support when using vlan-aware bridge (vlan-filtering=yes).

It's not WAN2LAN traffic, it's LAN2LAN traffic if communicating devices are connected to different ether port blocks (one being ether1-ether5 and the other one being ether6-ether10). Yes, if one cares to connect devices which communicate with each other more frequently to same ether port block, then this is not a problem.

Plain untagged single LAN gets offloaded just fine. So for plain flat LAN this is not an issue.

Hi,

Connect as many devices that need highspeed, highpriority connections to ports 2-5 and the rest to eth6-eth10. I do not see the reason to have solar panels on the first switch if they need generate low priority traffic. Same as management.

In my offices, we've had a 100M/100M WAN and an RB3011 since 31 may 2018.
We haven't felt the need to replace it yet...

Maybe useful, maybe not:
The RB3011 is almost 10 years old

Mikrotik dates - A little exercise in futility

Only ports 6-10 are included in the bridge (see attached rb3011.rsc in OP). ether1 (WAN), ether2 and ether5 are layer 3 interfaces, so traffic between the bridge and those ports will already need to be routed.

And the part about no HW support was referring to vlan support for the QCA8337 using vlan-filtering=yes

That was in response to "If I setup VLAN's" in the last sentence of first topic post.

I bought the RB3011 and 2 CAP AC's second hand.

I have a 300/30 Mb internet connection so I think that the RB3011 should be able to handle this.

Today I tried to connect everything to the RB3011 and got a problem. On ether8 (on the bridge) I have a RB260GSP which is connected using POE to a CAP ac. Most of the devices worked but I could not connect using Winbox to the Cap ac.

On this Cap ac I have a bridge with ether1, ether2 and the wifi's. On this bridge I have set a DHCP client, so the bridge gets a IP adres from my router and so does everything that connects to the wifi's.

If I setup another Cap ac using ' Quick set' there is a bridge for ether2 and the wifi's. Ether1 is seperate and has a DHCP client and gets a IP adress from the router, while the bridge has the IP adress set to 192.168.88.1.

What is the best way to setup the Cap ac? What adres is used in Winbox (the bridge/ether).

I run my CAPs in pure AP mode, let the bridge get a static IP assignment from my router, and let the router also handle client DHCP . . . IE, the CAP is basically nothing more than a dumb wired to wifi bridge, with all the intelligence on the router. This has ether1, ether2, wifi1 and wifi2 on the bridge, a dhcp client, and no firewall. Connect to the static IP to admin the CAP (or setup CapsMan).

What I personally do (not necessarily "right").

To me devices that are ethernet connected are "fixed" or - in other words they are "static" (they don't move) and are usually connected 24/7, it makes little sense to have their addresses "dynamic" and renewed every x hours.

So I make on the "main" router a DHCP server (say 192.168.1.1/24) with a pool for addresses 192.168.1.10-192.168.1.254, this way I use:
192.168.1.1 for main router
192.168.1.2 for main switch (if any)
192.168.1.3 for first AP
192.168.1.4 for second AP
192.168.1.5 for third AP
...

This way one gets rid of DHCP clients on all router/switch/AP devices.

Usually... on small office
DHCP 101...199 only...
Router 1
Various servers/nas/printer from 11
SW and AP start from 21, following the linked order
VoIP from 41 (following internal number)
NVR on 80 and various cam from 81
part 200...254 remains free for needs to collaborate with other companies that provide other services,
then other LAN for guests according to needs.

On CPEs
DHCP 101...199 only...
VoIP from 91
CPE .1
SW and AP from 11