3 ms·

It's a good list. I just hate those things now. I worked as a wireless router firmware developer for a while and as a result... I don't use them anymore. The w

by zxcmx 9y ago

It's a good list. I just hate those things now. I worked as a wireless router firmware developer for a while and as a result... I don't use them anymore. The whole industry is just producing unfixable tire-fires. Different level of caring, but if security is important to you, put cable/dsl/fiber ntu in bridge mode. Get a pcengines apu (or your favourite sbc), install your favourite os (ubuntu or debian for me). Don't bother with ui, just use a few nftables rules. It actually worked out cheaper for me than the netgear thing shaped like a stealth fighter. The other thing which really annoyed me was my ISP periodically updating settings on their stock router. Yeah, they can do that remotely if you use their unit and there's usually no good way to turn it off.

drakenot 9y ago
Can you expand on this a little bit? What does it buy you? Is this setup (the linux APU in bridge mode) so that the NTU could get hacked but your internal network would still be secure behind the APU? What protects the APU from getting hacked like a traditional router would? Just easier to secure yourself? Did you just purchase wireless access points separately? Did you buy a seperate switch? I've wanted to do something like this for awhile but I wasn't sure what all was involved, or if it was that much more secure.
- zxcmx 9y ago
  The short answer is that if you build an x86 box based on crappy linux and updates then your security is based, fundamentally on the primitives which secure eveything else in the world. It doesn't mean that it's the best. An x86/x64 ssh bug hurts everyone. But it means that everyone in the world gets fucked, more or less, and you don't have to worry as much. Relying on random companies to secure your gateway puts you in the hands of random companies who not only do not care but also do not make theor own stuff and now lack the basic competence to do so.

by zxcmx 9y ago

drakenot 9y ago

Can you expand on this a little bit? What does it buy you? Is this setup (the linux APU in bridge mode) so that the NTU could get hacked but your internal network would still be secure behind the APU? What protects the APU from getting hacked like a traditional router would? Just easier to secure yourself? Did you just purchase wireless access points separately? Did you buy a seperate switch? I've wanted to do something like this for awhile but I wasn't sure what all was involved, or if it was that much more secure.

zxcmx 9y ago
The short answer is that if you build an x86 box based on crappy linux and updates then your security is based, fundamentally on the primitives which secure eveything else in the world. It doesn't mean that it's the best. An x86/x64 ssh bug hurts everyone. But it means that everyone in the world gets fucked, more or less, and you don't have to worry as much. Relying on random companies to secure your gateway puts you in the hands of random companies who not only do not care but also do not make theor own stuff and now lack the basic competence to do so.