Live data from Hacker News

OpenWrt 23.05

openwrt.org

71–80 of 84 posts

Re: OpenWrt 23.05

#71

Earlier quoted context omitted.

32X is a real device name (the gaming router)... 3200ACM is another device. But did you try divested? It has patches for wifi...

According to the openwrt wiki the WRT3200 and WRT32X have identical hardware [1][2] I tried several patches but nothing helped. As I understand it it's the closed source abandoned (?) WiFi firmware that's the issue. I suspect it can't handle interference , which which is why it works great for some and horrible for others. I see there are new commits on the driver repository [3], so maybe I'll try again but I don't h…

Mmh thanks, I didn't know that. Seems that the following devices may be a better option (because also supporting wifi 6):

  Netgear WAX202
  Belkin 3200
  Banana Pi BPI-R3
  Nano-Pi R5S
  Cudy X6
While the Cudy is very cheap (40 Bucks here in Germany), I still like the Banana Pi BPI-R3 most. But until it gets really necessary, I'll stick with my 32X... for me it does work but I won't recommend it any more without that note.

Here is some more info about the Banana Pi: https://wiki.junicast.de/en/junicast/review/bananapi-BPI-R3

Re: OpenWrt 23.05

#73

One thing I don't see anyone mentioning here is that OpenWRT allows you to configure your router as code via config files in /etc/. If you straddle the worlds of preferring a "normal" router to a custom built box but also want to keep your configuration history in git I think OpenWRT may be the best option.

This is one of my favorite features. Wasn't able to figure out how to set up my somewhat complicated guest + iot wifi vlan setup through the web interface, but it was pretty straightforward through the config files. And now I have it backed up in case I ever need to set it up again from scratch.

Re: OpenWrt 23.05

#74

OpenWrt is commonly used to breathe new (or better) life into consumer routers, but you can also run it on any x86 machine. I run it on a small, passively-cooled i5 machine* virtualized in Proxmox alongside Home Assistant. I originally ran OPNSense, then VyOS, but eventually went back to OpenWRT since it does everything I want/need with a simple interface. * https://www.reddit.com/r/homelab/comments/hzvfih/new_router…

Running OpenWRT directly on Proxmox on your home server is tempting but the risk to mess up from a security point of view (accidentally or not) is high.

After a quick look on OpenWRT wiki there is unfortunately not much information on what to be attentive to when running in a vm.

Re: OpenWrt 23.05

#75

OpenWrt is commonly used to breathe new (or better) life into consumer routers, but you can also run it on any x86 machine. I run it on a small, passively-cooled i5 machine* virtualized in Proxmox alongside Home Assistant. I originally ran OPNSense, then VyOS, but eventually went back to OpenWRT since it does everything I want/need with a simple interface. * https://www.reddit.com/r/homelab/comments/hzvfih/new_router…

it also works really nice with the raspberry pi 4 and QEMU.

Re: OpenWrt 23.05

#76

I recently became an openwrt user (new Dynalink $79 woot) and am happy, but it isn’t all sunshine and roses as folks tend to rave about it here. First, the distribution is bare bones to the extreme by default. Like Linux in the 90s bones. Understood, some old routers are tiny, but it makes a RasbPi feel positively ergonomic. Lucky you can install packages pretty easily, like htop etc. Have to install the web gui of c…

You can enable ssh in the gui and then login to install packages (using opkg) or edit config files or whatever. opkg is a lot like dpkg but a bit more limited. Unfortunately the login shell is busybox so you're fairly limited in what's available.

All of this is pretty understandable since openwrt is targeted to really low specs . 4MB storage/32MB RAM was the target until 2022. It's now 16MB storage, 128MB RAM which is still pretty low.

Re: OpenWrt 23.05

#77
post #63
post #21

I wish OpenWRT had LTS releases... I'm still on 21.02.7 because they switched to nftables syntax for custom rules ("firewall.user") in 22.03 and I have a pile of them and haven't had the time to rewrite it all. This release means 21.02 will have no more security updates.

nftables has a converter from iftables: https://wiki.nftables.org/wiki-nftables/index.php/Moving_fro... But it might not cover all of your existing iptables rules.

Syntax is the least of the problems. The main problem is the ruleset structure they've chosen which, for example, no longer includes user customizable chains. This means I'll have to rethink my rules to make sure they play nice with the default ruleset.

They seem to be forcing the use of the UI for creating rules, but that doesn't cover some that I have (part of which are generated dynamically).

Worse, I'll have to go through 22.03 because they don't support upgrading from 21.02 to 23.05.

Re: OpenWrt 23.05

#78
post #58

Earlier quoted context omitted.

I'm still on 18. I'll probably switch to 23 sometime. The device is stable and I'm the only one using it so I didn't feel any pressing rush to deal with the hassle since a lot of "security" issues are often from the inside not the outside. So I would say don't stress overmuch about it.

Unfortunately there's some RCE vulnerabilities and other nasty bugs between 18 and 23 that can be exploited remotely. I wouldn't feel safe running an unpatched version if it can be helped. https://openwrt.org/docs/guide-developer/security

I don't advocate staying on an older version, but that depends on the services you have running. If you don't have any external service, you should be OK.

I tend to minimize internal services as well. I don't use OpenWRT as a general purpose server.

Still, an LTS release from time to time would be good (the effort would be the same, as there would still be only two maintained releases: the current stable and the LTS).

Re: OpenWrt 23.05

#79
post #75

OpenWrt is commonly used to breathe new (or better) life into consumer routers, but you can also run it on any x86 machine. I run it on a small, passively-cooled i5 machine* virtualized in Proxmox alongside Home Assistant. I originally ran OPNSense, then VyOS, but eventually went back to OpenWRT since it does everything I want/need with a simple interface. * https://www.reddit.com/r/homelab/comments/hzvfih/new_router…

it also works really nice with the raspberry pi 4 and QEMU.

I was trying to get your idea, but then realised that probably you meant Raspberry Pi or QEMU. Or do you run it on Raspberry Pi with QEMU? If so… why?

Re: OpenWrt 23.05

#80

Earlier quoted context omitted.

If you do want the USG back, most of their failure modes (flash storage, PSU) are fairly easy to resurrect

My Asus router, when using OpenWrt, can't keep up with my internet connection, so I'm putting (admittedly minimal) effort into finding a suitable upgrade with the intent to keep the Asus as a backup. I've also looked at installing OpenWRT on my USG, but only the snapshot version is available and the process is fairly involved[0] so I haven't really explored this. At this point though, I'm not likely to go back to Uni…

The UniFi gear is a massive PITA for services behind reverse proxy,
Post reply on HN