[OpenAFS] multiple network interfaces in AFS

[Warren.Yenson@morganstanley.com]

(Hi Todd).

Note that the NetInfo and NetRestrict files will limit the interfaces
advertised in the VLDB, and in the UUID of the fileserver.  That is, the
clients should not try to connect to eth0 as that interface won't be
listed in any service.

In practise (on Solaris fileservers), we've seen that when although a
client will connect to qfe1:0, the return packets from the fileserver
have the source address of qfe1, which can fool the RX driver on the
client to continue the rest of the RX exchange to qfe1.  This is despite
using any combination of NetInfo and NetRestrict on the server.

It would be nice to have the fileserver limit the ports that it opens to
the ones listed in NetInfo / NetRestrict, rather than open them all and
rely on VLDB and UUID information doing the correct thing.

              - Warren

On Fri, 6 Dec 2002 Todd_DeSantis@transarc.com wrote:

> Hi -
>
> > What about the server side?
> > I'm thinking about a fileserver failover setup, where I have eth0
> > and eth0:0 on the active machine. Ideally, the clients should not
> > see eth0 but eth0:0 only.
>
> The AFS servers use the NetInfo and NetRestrict files from
>
> 	/usr/afs/local
>
> So you can define which interfaces the fileserver should use or
> restrict here.  This will then change the way the fileserver registers
> its IP addresses in the VLDB.
>
> # vos listaddrs
>
> can show the addresses advertised by each fileserver machine.
>
> Thanks
>
> Todd
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>