On 12/9/2013 1:47 PM, Harald Barth wrote: >>> Not in the listaddrs list but will it go away from the volume location >>> list? >> >> I don't understand this sentence. > > Is the 127.0.1.1 deleted or replaced as a replication site location if > the server registers as 129.89.38.124 when previously known as > 127.0.1.1.
In OpenAFS volume locations are tracked by file server UUID not by ip-address. At startup the file server registers it active address list with the vldb. These addresses are the ones that reported to clients that query the VLDB for the addresses belonging to a particular server. The VL_GetEntryByNameU RPC returns the list of volume locations by server UUID and partition. The VL_GetAddrsU RPC returns the list of addresses for a specified server UUID. >> No, OpenAFS 1.6.5 detects 127/16; that is, 127.0.x.x. See src/rx/rx.h, >> rx_IsLoopbackAddr (in this specific case, called from GetServer in >> src/volser/vos.c). This is a kind of balance (or an argument >> compromise :) between trying to catch all loopback addresses an >> administrator is likely to accidentally specify, but allowing a range of >> 127/8 addresses if you actually do want to use loopback for testing or >> something. > > Then something in the server startup should probably check the same range. The file server constructs the address list either by calling rx_getAllAddr() or afsconf_ParseNetFiles(). Both paths filter the address list for loopback addresses. It is of course possible that there is a bug in one of these code paths. All interested members of the community are welcome to read the source code or debug a machine that is actively advertising a loopback address to the VLDB. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
