Introducing the LEDE project – A reboot of the OpenWrt community
21–30 of 82 posts
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#22While I'm excited about OpenWrt, why wouldn't the ecosystem move to Raspberry Pi at this point, considering that a Pi and multiple wireless NICs can be purchased for much less than a typical access point?
But, the idea that it can run on a variety of platforms is one of the benefits. Rpi, for example, would be an odd choice as a base for a commercial hardware product, due to availability in volume, form factor, etc.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#23Re: Introducing the LEDE project – A reboot of the OpenWrt community
#24oh boy more fragmentation! I wish the devs behind OpenWrt, dd-wrt, and LEDE would just work together for god's sake. OpenWrt is far from complete. the documentation alone is terrible.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#25[1] https://www.lede-project.org/about.html [2] https://dev.openwrt.org/wiki/people
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#26Earlier quoted context omitted.
What about the Pi 3?
Looks like the rpi3 may have onboard ethernet and wifi, but it's still just one ethernet (100Mbit to boot) and single band wifi. The point still stands that a $30 router blows away a rpi in terms of network connectivity (which should matter for a router).
> The Raspberry Pi 3 shares the same SMSC LAN9514 chip as its predecessor, the Raspberry Pi 2, adding 10/100 Ethernet connectivity and four USB channels to the board. As before, the SMSC chip connects to the SoC via a single USB channel, acting as a USB-to-Ethernet adaptor and USB hub.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#27Now if they could just get rid of Linux underneath and use something with better security. L4, maybe. After all, this is for embedded devices which basically run one program.
But maybe an operating system is too large in scope. You're right that these devices only run one application, why use a tool (operating system) that can run many applications?
It's a bit like running a hypervisor for only one operating system. There are benefits, true.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#28Now if they could just get rid of Linux underneath and use something with better security. L4, maybe. After all, this is for embedded devices which basically run one program.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#29It is a real pity that the lack of developers is compensated by splitting developer focus on two different forks. If the reasons stated are true, let's hope it works out and strengthens embedded Linux, maybe even leading to a reunion like egcs/gcc.
This announcement comes as a surprise to all the other developers, myself included. - mbm (openwrt founder)
It's always disappointing to see a project you use and rely upon face this kind of challenge. With technical forks, you can usually at least appreciate the motivations, but with political forks it can be difficult to understand what or how things will be improved (especially for users who only see events from the outside).
Best of luck to you and the rest of the team in resolving whatever issues are at play here.
Re: Introducing the LEDE project – A reboot of the OpenWrt community
#30While I'm excited about OpenWrt, why wouldn't the ecosystem move to Raspberry Pi at this point, considering that a Pi and multiple wireless NICs can be purchased for much less than a typical access point?
However, it would be great if the *wrt projects could adopt the standardized update mechanism that OSMC has leveraged. It's made upgrading so much less painful.
Personally, I use ddwrt and would like to see that project take the charge up on this.