My Turris Omnia arrived today! LED colors based on Network Traffic Video of it in action: https://youtu.be/bMkGp54xWqQ Forum post: https://forum.turris.cz/t/led-color-based-on-bandwidth-usage/1262 Blinky Lights The RGB LEDs can be controlled by sysfs, the "A" and "B" ones are available as: /sys/class/leds/
I threw together some hardware I had on hand to make a PC-based router. IPv4 Getting IPv4 working was easy, I just needed to set ZONE=external and ZONE=trusted on the wan/lan interface ifcfg-* files. I threw net.ipv4.ip_forward=1 in /etc/sysctl.conf as well.
See also: SB6183 dropping IPv6 traffic [https://blog.dan.drown.org/sb6183-dropping-ipv6-traffic/] Comparing latency in cable modems: SB6183 (16 channel DOCSIS 3 modem only) vs DG1670A (16 channel DOCSIS 3 modem+router combo, in bridge mode) Arris DG1670A Average latency of 100 ICMP echo replies to the default gateway: 20.
See also: Comparison of the Arris SB6183 vs Arris DG1670A [https://blog.dan.drown.org/sb6183-vs-dg1670a-latency/], and SB6183 dropping IPv6 traffic [https://blog.dan.drown.org/sb6183-dropping-ipv6-traffic/] As part of TWC's upgraded speeds (300M/20M coming in August), I needed a 16x4 channel DOCSIS 3.0 modem. Since the Arris
The goal for this project is 300mbit/s forwarding with full size packets and nat enabled. There's problems with this hardware: see "Problems" section below. test setup Router hardware: Utilite Standard [http://utilite-computer.com/web/utilite-models] (note: see the Problems section) Network eth0 - "inside" - 10.1.6.1/
This hardware has problems - see the Problems section [https://blog.dan.drown.org/arm-router-forwarding-rates/] on the follow-up page. I have an arm system with two gige ports that I want to turn into a router that can forward at least 300Mbit/s (with 1500 byte packets). It's a dual-core