How to add route for 2nd WAN interface

[beatdown]

We have an 1841 router, with a serial interface currently connected to a T1. The default route is setup to be this serial interface.

Tomorrow, we're getting a 2nd internet line (Verizon FIOS), which will connect to an Ethernet interface.

Eventually, we'll decommission the T1, and setup the FIOS interface to be the default route. But for now, I just want to be able to test out the FIOS interface by connecting to it via Telnet, and testing if it's ping-able from the internet.

However, I'm not sure how to setup the routing to do this?

Since the default route will remain the serial interface, how do I set up a route so I can ping/telnet the new FIOS Ethernet interface?

Thanks for your help!

 

[unclerico]

I would just console into the 1841 and ping the next hop of the FIOS service. If you can get to your next hop then you'll be fine.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[beatdown]

Unfortunately, I'm not onsite where the router is, so connecting via console isn't an option.

My only connection option is telnet/ssh

Also, if I ping the next hop, wouldn't it still use the default route, and send the ping traffic out the serial interface?

 

[unclerico]

Ok, then I would add a static route for the ip address you'll be sourcing the telnet/ssh traffic from and pointing to the FIOS next hop. If you are sourcing ssh traffic from 1.1.1.1 then your static route would be ip route 1.1.1.1 255.255.255.255 <exit-interface> <next-hop-ip>

As for your second question, the router will choose the interface that is closest. Say your FIOS has an IP of 2.2.2.1 and your next-hop is 2.2.2.2, when you end up pinging 2.2.2.2 it will source the ping from 2.2.2.1.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)