Hello,

I remember this once mentioned on this list, but my recent experience
shows this problem is still open:

I have a server that usually has only one IP addres, a public one. Due
to various outside conditions, I had to plug a crossover cable to
another interface in that machine and assign it a private IP; I have not
intended it to be used for AFS. 
However, even despite no fs server restarts, it somehow picked up the
new address and put it into vldb. 

Noticing that, I have put NetRestrict files all over the /etc/openafs,
with following contents:

10.255.255.255

and happily restarted fs process (using bos restart method). To my
surprise, the private ip (10.10.10.11, to be exact) showed right back up
in vos listaddr output, and while I can suppress it by using vos
changeaddr, it's only a temporary kludge. 

I have put NetRestrict in following locations:
/etc/openafs
/etc/openafs/server
/etc/openafs/server-local

All of the above files are identical.
The fs server in question runs OpenAFS 1.4.1-2 from Debian (Ubuntu)
package.

Any suggestions?

Jakub Witkowski.

Attachment: signature.asc
Description: To jest część listu podpisana cyfrowo

Reply via email to