Before I used to do NAT on a Linux, but nowadays I have (as have others) gotten lazy and just got a cheap ADSL/Cable router that does the NAT. The one I was using died recently, I had to replace it.
You'd think it's quite simple, route some packets, provide some web interface to configure the router, but how come vendors find it so hard to get it right? One which I replaced it with (which ran VXWorks) would pick up everything except for the ISP's default gateway via DHCP, rendering it completely useless as a router. The current one would not allow me to initiate any connection, except for anything on port 80, when I get home from work. I plug it in, I just want it to work. But it doesn't, everytime I have to login and pretend to configure the router, and press apply, then mysteriously the ability to initiate new connections come back to life. Oh, and the old one wasn't very good either. Whenever I configure the router it would behave as if it required a reboot, because it would drop all my existing connections regardless of how trivial the change may be and whether it was actually necessary. Seriously, the next one has to run Linux or BSD of some kind, instead of whatever useless garbage firmware is sitting in the flash ...
回應
Yeah, flash it with
Yeah, flash it with something like OpenWRT if you could
or buy one that lets you to