3 ms·
I second getting away from embedded land, and moving to a full-capability machine. I've come full circle to just running an i5 with Linux/nftables (my first ro
by mindslight 7y ago
I second getting away from embedded land, and moving to a full-capability machine.
I've come full circle to just running an i5 with Linux/nftables (my first router was a k5 with ipfwadm). I already had the i5, and gigabit VPN can use the horsepower.
I wanted to like pfSense, but I didn't want to learn a whole new net stack to debug firewall rules. Not that you have to dig that deep to simply use pfSense, but I ran into some config problem and missed the insight I take for granted on Linux.
Reading the comments on the OP is kind of funny, too: ESR regarding an "old PC" as a router:
> and use what for ports? Even newer ones tend to have only two. That's poor fanout.
The ports you see on an embedded router are actually just a tagged switch. A good CPU has two internal ports connected to that switch, but many have only one. Some switch chips can eg accelerate NAT, but OpenWRT is going to erase that. So embedded router bandwidth is actually quite poor, meanwhile you can essentially stick as many true 1Gb/10Gb ports in a PC router as you desire.