This is an informational question - not based on any hardware I will
likely see in the near future... There have been some discussions about
servers with multiple ethernet addresses, but how about clients?
As long as both interfaces are up, I think it just picks one and uses it,
and everything works. I don't know what happens if one file server is
reachable through one interface and another is reachable through a different
interface, but I suspect that works too.
What doesn't work is to start up afsd with one interface active, then shut
it down and bring up a different interface. Not only will callbacks not
reach you, but you won't be able to reach the file server either. I haven't
looked at the code but I suspect it has to do with cacheing rx connections.
We've actually tried this, since our mobile computers can sometimes have two
interfaces, one for the ethernet and one for the cellular modem. It's
something I have on my long list of things to look into. I want to add a
"shutdown interface" call that will give up all callbacks, tear down all rx
connections, and purge all ip addresses from afs. (There used to be a
"shutdown afs" call that did some of this, but it hasn't worked in a long
time.)
