Last month I posted a question to this group about getting an ATMworks 351
board usable under Digital UNIX. A few folks suggested upgrading to DUNIX
4.0D, which has better ATM support, and that has done the trick. I now have
an ethernet (built-in TP) and an ATM (using an ELAN) interface out on the
net under two different IP addresses. What I'd like to do is make the ATM
interface the primary one, but fall back to the Ethernet in case of problems
with the ATM network (I'd do this in a cron job that would fire off
periodically and attempt to ping the gateway router). We are a fully
bridged network, so this is in theory possible.
I've tried using `ifconfig` to down the ethernet interface and the `route`
command to delete the associated routes. Next, I use `ifconfig` to up the
ATM interface with the IP address from the ethernet side. When I go to add
routes again, though, the `netstat -rn` command show that they are still
using the "tu0" ethernet interface, not the "elan0" ATM interface. Any
thoughts on how to get the internal route tables to use the "elan0"
interface?
Thanks in advance...
Peter
--
Peter Murray, Library Systems Manager pem_at_po.cwru.edu
Digital Media Services http://www.cwru.edu/home/pem.html
Case Western Reserve University, Cleveland, Ohio W:216-368-5888
Received on Tue Apr 14 1998 - 20:11:14 NZST