Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
The last router I configured through a serial port was a cisco 2621. I much prefer doing it over the network - it's a pain in the arse to locate or build a serial cable to use one time for 20 minutes...
The "routers" I'm using at home and at the office are just linux systems. Way more functionality than any off-the-shelf router, even those running 3rd party firmware, and any old/obsolete (for windows) PC can do the job. The one at the office is also running our PBX, several monitoring tools and some other odds and ends, and it's being done with a 6 watt mini PC that's bolted to the back of the monitor I have in the rack.
There's a somewhat obvious problem with configuring a network interface over the network, but if you don't mind the pain that is is, you go ahead.
I just keep a serial cable around, I have one at the office, and one at home, the type where you can detach the DB9 connector and use the RJ45 instead on the router end. The things are probably 10 years old and still work, so long as I don't lose them I'm fine.
Besides, I apparently do it more often than you since one of my job responsibilities is pre-configuring routers and APs to go out to customer sites. Especially in the case of the APs I have to configure them for a LAN segment that I don't actually have in my office.
There's a somewhat obvious problem with configuring a network interface over the network
I once forgot to remove an ACL from an interface before clearing the list. Oops. This was on a router that was in production. I think everyone in the company called to tell me that their internet had gone down. I cobbled together a cable in record time that day...
Of course there are advantages to using a serial cable, but I don't have to leave my desk to work on something via the network, and I don't have a serial cable long enough to reach from San Diego or Los Angeles to Las Vegas, so sometimes working across the network is the only real option.
The "routers" I'm using at home and at the office are just linux systems. Way more functionality than any off-the-shelf router, even those running 3rd party firmware, and any old/obsolete (for windows) PC can do the job. The one at the office is also running our PBX, several monitoring tools and some other odds and ends, and it's being done with a 6 watt mini PC that's bolted to the back of the monitor I have in the rack.
Many, if not most, routers run Linux as their OS. I can login to my router via ssh and with Entware, I can install and run software directly on it. Everything from ftp, mail, and web servers all the way to video processing, image manipulation, even games like tetris and chess. I still have not found a practical application to a lot of that software running on a router, but nonetheless, the option is there if needed. Attached is the complete list of software provided by Entware.
Many, if not most, routers run Linux as their OS. I can login to my router via ssh and with Entware, I can install and run software directly on it. Everything from ftp, mail, and web servers all the way to video processing, image manipulation, even games like tetris and chess. I still have not found a practical application to a lot of that software running on a router, but nonetheless, the option is there if needed. Attached is the complete list of software provided by Entware.
I've used 3rd party firmware (the WRT54G I just replaced was running dd-wrt). There's just not much point (for me) in messing with it any more. I don't have the time or inclination to screw around with these kinds of things these days, and besides, I have a large pile of retired desktop machines that I'm always trying to find uses for. It's a lot easier to install debian and setup what I want on it, knowing it's going to work, than it is to mess around with 3rd party firmware images, determine whether or not the software I want to run will work with it, etc. Horsepower and storage space are also a significant factor - I wouldn't ever try using a router as an X11 client, for instance.
I had fun tinkering with 3rd party firmware, and it allowed me to do things that I couldn't do with the native firmware, but I have no need for it anymore, and my tinkering-for-the-sake-of-tinkering days are pretty much over.
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
