Hi Nathan,
Here's a snippet of a prior discussion I was having with Darrell May on a similar subject. Note : Stay Alive script mentioned below written by Brian K. High.
Begin Excerpt
==========
What I had in mind by extending on the Stay Alive script was to do a similar thing but with a third NIC (say eth2) interface as a WAN side connection. Then if the primary WAN link fails (eth1), we somehow rename eth2 as eth1 and vice versa (so as to avoid breaking all SME scripts which assumes eth1 as the WAN interface) and then bring up the link. Meanwhile, periodically try to bring up eth2 and see if it has come back alive. If it has, switch them back around again. And if we want to get really fancy (read as complicated), if both eth1 and eth2 does not work, fall back to dial up.
My problem basically boils down to lack of knowledge on many fronts (having been a Windows person for too many years and Linux experience is still fairly much in the Growing Pains stage). For example :-
1. Don't know if it is possible to configure another NIC into SME as a WAN side NIC
2. If possible, how.
3. Don't know if Linux allows us to rename an interface (ie swap eth1 and eth2 around).
4. If possible, how and can it be done without needing a server reboot.
5. Not enough experience with bash and perl programming (learning but still infantile - have full time job still supporting Windows environment).
=========
End Excerp
However, if I understand your post correctly, I'm assuming we do not need to rename the interfaces in order for the second WAN interface to work ? If so, will all firewalling rules, etc. still automatically apply to the secondary WAN interface ?
Kelvin