0 Persons are tagged with #wan

#wan

memo@pod.mv2k.com
Memo

Vor einigen Tagen, so eine Bestellung aus den USA kann ja schon eine Weile dauern, kam das GehĂ€use fĂŒr meinen Meshtastic RAK5005, und ich konnte es zusammenbauen.

Es ist wirklich eine sehr schöne Arbeit - von der Entwicklung, bis hin zum 3D-Druck: https://www.etsy.com/de-en/listing/1158237722/rak5005-case-for-meshtastic

Schön, dass es Menschen gibt, die sich in ihrer Freizeit damit beschĂ€ftigen 👍

(Bild 1: Das fertig zusammengebaute GehĂ€use fĂŒr den RAK5005 und noch einigen anderen kleineren Erweiterungen. Bild 2: Das RAK5005 GehĂ€use und das zukĂŒnftige Innenleben noch in ihren Einzelteilen. Bild 3: Provisorischer Aufbau meines Meshtastic Clients mit dem RAK5005, RAK4630, RAK13002, einem Lithium Polymer Akku 3,7 V 1200mAh, ein SSD1306 Display und einem Antennenadapter (Pigtail) fĂŒr die Eightwood 868 MHz Antenne.))

#LoRa #Meshtastic #Mesh #WAN

RAK5005 Case for Meshtastic - Etsy.de

This Gadgets item by QuantumShadow3D has 48 favorites from Etsy shoppers. Ships from United States. Listed on Sep 1, 2023

4 Likes
carstenraddatz@pluspora.com
DEFUNCT Raddatz (ćŠ‰æ„·æ©) -> now at nerdica

When I upgraded my cable ISP tier to 1000/50 I quickly noticed the old 2011 OpenWrt router wasn't up to it, downstream consistently maxed out at around 260mbps. That said, its nearly always TCP offloading, and needs beefier hardware if you can't use that. I went to a downstream north of 420mbps and often go into the 600mbps region even with ac wifi. Upload otoh hasn't improved, meh.

Over at the OpenWrt forum there's a posting to answer all postings on how el cheapo CPUs fail:

Let's take a look at the math: At 1Gbps using 1500 byte packets, you need to send/receive 83333 packets per second. The packets need to be received by an interrupt, go through the firewall, be inspected, maybe have NAT applied, sent into a queue, the queue calculates rates to avoid over-sending on the link and causing buffers, and then hardware interrupts are serviced to actually send the packet along...
At 1 GHz processing rate, each packet gets 12000 clock cycles of calculation if the CPU is maxed out doing nothing but processing packets.
Evidently in an ideal world, we should have maybe 1.2GHz processors or better, and maybe have two cores at least one can handle interrupts on the receive interface, and one can handle interrupts on the send interface, and they can share the firewall and queueing duties.

(https://forum.openwrt.org/t/so-you-have-500mbps-1gbps-fiber-and-need-a-router-read-this-first/90305/45)

Still, because DOCSIS cable is a shared medium and oversubscribed ISP-wise, the throughput is wonky and inconsistent. But at least I know not my own CPU is to blame so I can point fingers at my provider vodafone. And I'd totally want to go 500/100 if only I could mix and match features. Sigh.

TL;DR Going cheap, stick with proprietary firmware to keep the TCP offloading feature, or gear up. A Turris Omnia should be fine, or any of the suggestions in the thread. I went with OPNsense on a small x86 box.

#openwrt #gigabit #throughput #docsis #docsis3.1 #docsis4 #wan #networking

So you have 500Mbps-1Gbps fiber and need a router READ THIS FIRST

Also there are: the dslreports speedtest (read this first) waveform's new bufferbloat test both of these can be run from a browser @richb-hanover-priv : maybe we could/should add these to the Tests_for_Bufferbloat page?

2 Likes
6 Comments