News for hackers. Stuff that matters.
Re:OpenWrt 24.10.0 – First Stable Release by arjvik on Thursday February 06, 2025 @01:25AM (#42959631)
What hardware do you use for your router?
Re:OpenWrt 24.10.0 – First Stable Release by choobacker on Thursday February 06, 2025 @01:36AM (#42959689)
I use a https://www.pcengines.ch/apu2.htm with a separate wifi access point.

That's EOL now, so nowadays I'd look to ARM e.g. https://radxa.com/products/network-computer/e52c

Re:OpenWrt 24.10.0 – First Stable Release by Piraty on Thursday February 06, 2025 @04:47AM (#42960764)
I use ancient+cheap netgear SOHO routers (WNDR3700 v1 and v2 from ~2012) which can route 940Mbps on ethernet (with software flow offloading enabled).

For wireless AP i have an Mediatek MT7621 device, they are very well supported and provide proper wifi throuput

Re:OpenWrt 24.10.0 – First Stable Release by Firefishy on Thursday February 06, 2025 @08:04AM (#42961919)
https://protectli.com/ Good quality devices. Real serial consoles to allow recovery when you make a networking configuration mistake ;-)
Re:OpenWrt 24.10.0 – First Stable Release by LinuxBender on Thursday February 06, 2025 @10:35AM (#42963343)
Same here. Alpine Linux on top of that + Unbound DNS, dnsmasq for DHCP, netfilter, chronyd for time. I've never been able to make them break a sweat.
Re:OpenWrt 24.10.0 – First Stable Release by nicolas314 on Thursday February 06, 2025 @04:23PM (#42966634)
Curious: how did you set up firewall (nftables?), IPv6 delegation both ULA and public prefix? Happy to read if you have a write-up somewhere.
Re:OpenWrt 24.10.0 – First Stable Release by LinuxBender on Thursday February 06, 2025 @06:57PM (#42967747)
I disabled IPv6 as my little ISP has not yet figured out how they want to bill for or assign/segment it out for static assignment. I have multiple static IPv4 addresses. I only use static IP's but that is a requirement specific to me. The firewall is very simple and just forwards packets and uses a simple IPv4 SNAT. The only time I've had it set up more complicated was when a guest was abusing P2P so I had to block it using string matches on the unencrypted commands.

My setup is honestly simple enough that a write-up would not benefit many. My Unbound setup to block many malicious sites is also fairly well documented by others. The null routing of commonly used DoH servers is straight forward. My Chrony setup would just annoy people as I only use stratum-1 servers and the options would just look like cargo-culting to some.

About the only thing not commonly discussed is the combination of thc_cake and some sysctl options to keep buffer bloat low but OpenWRT has their own take on that topic already.