I can't answer you question for sure, but have a vaguely similar
question about two network cards in the same server.
We have (2) nics in our main server. One faces our internal network runs
samba & the like, the other faces the outside world and runs apache and
the like.
The internal network has a separate NAT gateway on a completely different
machine.
To get this setup to work we needed a:
route add default gw 129.63.24.254
...which is in /etc/init.d/rc.local
Putting the gateway in /etc/network/interfaces didn't work.
When we reboot, everything is fine. When people do a ifup eth1, things
don't work unless they also do a rc.local People have a habit of
forgetting the rc.local bit...
We could easily wrap ifup with something like:
#!/bin/sh
# this ifup is in path before /sbin/ifup
route add default gw 129.63.24.254
/sbin/ifup $1
...but I am concerned that we will then forget this information.
1) In general does it make some to avoid hiding too config details?
2) Is there a better way to do this than in rc.local?
################
On Wed, 8 Oct 2003, Leonardo Boselli wrote:
> I have a server that has two network addresses.
> According the network of origin of the call could be accessible one or
> the other or both the address.
> How should i arrange in the DNS the two addresses so a client if does
> not found the first one, would try on the second ? (i do not need load
> balancing but just increase availability, 2nd channel is very slow ...)
> --
> Leonardo Boselli
> Nucleo Informatico e Telematico del Dipartimento Ingegneria Civile
> Universita` di Firenze , V. S. Marta 3 - I-50139 Firenze
> tel +39 0554796431 cell +39 3488605348 fax +39 055495333
> http://www.dicea.unifi.it/~leo
>
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
