Description
RB411L has one miniPCI slot and one Ethernet port.
Use this device in an outdoor case for a CPE device, or a point to point wireless link installation. The miniPCI slot allows you to choose your own preferred wireless card model.
It’s powered by an Atheros 300MHz CPU and has 32MB of RAM and a Level3 RouterOS license.
Differences between RB411 and RB411L can be seen in the file (RB400L differences) which you can download in the left side menu.
Product specifications
| Details |
|---|
| Product code |
RB411L |
| CPU nominal frequency |
300 MHz |
| CPU core count |
1 |
| Size of RAM |
32 MB |
| Architecture |
MIPS-BE |
| 10/100 Ethernet ports |
1 |
| 10/100/1000 Ethernet ports |
0 |
| MiniPCI slots |
1 |
| MiniPCI-e slots |
0 |
| Number of USB ports |
0 |
| Memory Cards |
0 |
| Power Jack |
No |
| 802.3af support |
No |
| PoE |
10-28V |
| Voltage Monitor |
No |
| PCB temperature monitor |
No |
| CPU temperature monitor |
No |
| Dimensions |
105x105mm |
| Operating System |
RouterOS |
| Operating temperature range |
-30C to +60C |
| License level |
Level3 |
| Current Monitor |
No |
| CPU |
AR7130-BC1A |
| SFP ports |
0 |
| SFP+ ports |
0 |
| Number of chains |
0 |
| |
|
Performance test results
| RB411L (300Mhz) |
One 100M port test |
RouterOS |
| Mode |
Configuration |
64 byte |
512 byte |
1518 byte |
| kpps |
Mbps |
kpps |
Mbps |
kpps |
Mbps |
| Bridging |
none |
97.3 |
63.8 |
23.5 |
99.6 |
8.1 |
99.8 |
| Bridging |
25 bridge filter rules |
41.0 |
26.9 |
23.5 |
99.6 |
8.1 |
99.8 |
| Routing |
none |
79.4 |
52.1 |
23.5 |
99.6 |
8.1 |
99.8 |
| Routing |
25 simple queues |
67.8 |
44.5 |
23.5 |
99.6 |
8.1 |
99.8 |
| Routing |
25 ip filter rules |
24.7 |
16.2 |
23.5 |
99.6 |
8.1 |
99.8 |
- All tests are done with Xena Networks specialized test equipment (XenaBay),and done according to RFC2544 (Xena2544)
- Max throughput is determined with 30+ second attempts with 0,1% packet loss tolerance in 64, 512, 1518 byte packet sizes
- Values in Italic indicate that max throughput was reached without maxing out CPU, but because board interface configuration was maxed out
- Test results show device maximum performance, and are reached using mentioned hardware and software configuration, different configurations most likely will result in lower results
