Live data from Hacker News

OpenWrt 23.05

openwrt.org

51–60 of 84 posts

Re: OpenWrt 23.05

#51

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…

I've run virtualized network applications before, and have always had trouble with the container mapping addresses into a new private IP subnet. Is this able to be worked around?

Don't use container.

Use qemu and bridge networking or pass through a physical network device.

Re: OpenWrt 23.05

#52

Earlier quoted context omitted.

I use an old Asus RT-N56U for great (Gigabit) switching performance. Wifi is only N, and you have to be careful, there are two HW revisions, that are indistinguishable from the outside. An alternative could be different TP Link devices, but I never tested these. For more modern purposes I use a Linksys WRT32X with divested[1] image, but you could also go for the 1900 or even 1200, depending on your needs... Maybe als…

I can't recommend the WRT3200 devices, the wifi stability is horrible

running a 1900ACS2 with divested for a couple of years and it has been rock solid

Re: OpenWrt 23.05

#53

Also note, that there is DD-WRT, which is a similar, but different project. Some routers might be supported by one, but not the other. I have a Netgear Nighthawk, for example, which is not supported by OpenWRT, but by DD-WRT.

I gave up on DD-WRT years ago when they started obfuscating parts of the WebUI to not have to comply with FOSS requirements (from foggy memory), moved to OpenWRT and never looked back. Trying to turn into a proprietary product something that was built by the community? Yeah no.

Re: OpenWrt 23.05

#54

Earlier quoted context omitted.

I can't recommend the WRT3200 devices, the wifi stability is horrible

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 have my hopes up...

[1] https://openwrt.org/toh/linksys/wrt3200acm

[2] https://openwrt.org/toh/linksys/wrt32x?datasrt=ethernet%20gb...

[3] https://github.com/kaloz/mwlwifi/commits/master

Re: OpenWrt 23.05

#55

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…

Hey, I do this as well with a Qotom mini PC and it is utterly fantastic. Home Assistant runs in a VM and the OpenWRT part handles WireGuard for remote access.

One problem that I have with it is that I'm running qemu-system-x86_64 in an init script which creates a tap0 interface and adds it to the br-lan interface. If I ever restart the networking these interfaces are removed from the bridge. I briefly looked for some sort of hook to run on network restart but didn't find one. I'd love to be able to run brctl after a network restart to add the interfaces back into the bridge.

Re: OpenWrt 23.05

#56
post #45

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…

> Could be wrong but don’t think you can upgrade with a command like Debian. Have to save config and reflash again. Hope not. I think most people upgrade via reflashing through the admin interface (GUI). Read [1], "Can you keep settings?" My experience is old, so I won't comment on the rest of the points. [1]: https://openwrt.org/docs/guide-user/installation/generic.sys...

You can do over the command line and even automate it (https://openwrt.org/docs/guide-user/installation/attended.sy...)

Re: OpenWrt 23.05

#57

Also note, that there is DD-WRT, which is a similar, but different project. Some routers might be supported by one, but not the other. I have a Netgear Nighthawk, for example, which is not supported by OpenWRT, but by DD-WRT.

I gave up on DD-WRT years ago when they started obfuscating parts of the WebUI to not have to comply with FOSS requirements (from foggy memory), moved to OpenWRT and never looked back. Trying to turn into a proprietary product something that was built by the community? Yeah no.

I once asked the main dev how to generate images for Buffalo routers, since I wanted to build from source. That particular component was not available and only he could build an image capable of being uploaded through the stock admin interface.

It wasn't the end of the world since a standard openwrt image could be loaded over tftp, but it was annoying that it was impossible to recreate the images available for download.

Re: OpenWrt 23.05

#58
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.

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

Re: OpenWrt 23.05

#59

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…

oh, one other thing.. upgrading openwrt on x86 isn't as nice as other devices with a squashfs root. I can upgrade packages, but I don't think that I can really upgrade it without re-installing everything.

Re: OpenWrt 23.05

#60

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…

oh, one other thing.. upgrading openwrt on x86 isn't as nice as other devices with a squashfs root. I can upgrade packages, but I don't think that I can really upgrade it without re-installing everything.

You can actually if you didn't expand your partition and keep the default layout. Use the firmware builder to build a customized image with your needed packages.

Edit: ah I didn't see that you run openwrt on baremetal...

Post reply on HN