[OpenAFS] OpenAFS Fileserver Behind NAT

Ken Elkabany Ken@Elkabany.com
Wed, 22 Apr 2009 17:25:16 -0700

Thanks for the quick reply. Unfortunately, on my server installation,
the NetInfo solution is not working. The server is once again running
openafs 1.4.7 on debian 5.0.

"lsof | grep NetInfo" shows that the file is being opened by the
fileserver. However, we have found that our openafs client machines
are still attempting to send request packets to the internal IP,
rather than the external, globally accessible one. The file is saved
in /var/lib/openafs/local/NetInfo. Could this at all be related to the
missing sysid file? This would be much easier to debug as well if I
could see the "vos listaddrs" output. Any other ideas?


On Wed, Apr 22, 2009 at 5:23 AM, Derrick Brashear <shadow@gmail.com> wrote:
> On Wed, Apr 22, 2009 at 6:32 AM, Ken Elkabany <Ken@elkabany.com> wrote:
>> Hello,
>> I am running OpenAFS 1.4.7 servers on Debian 5.0. I had initially been
>> having trouble accessing my OpenAFS Fileserver that was behind a NAT.
>> The VLDB was reporting the local IP of the fileserver to machines
>> outside the NAT group, resulting in connection failures. Adding both
>> the internal and external IPs to the NetInfo file did not seem to
>> yield any results or alter the server's behavior in any way (anyone
>> know why?).
> sure. the external IP doesn't appear on any interface on the machine,
> so it won't get advertised solely because it's in that file.
> nor is vos changeaddr correct, because, no, the server doesn't have
> that address.
> undo vos changeaddr; then, instead, modify the NetInfo file so the
> external address is prefixed with
> "f "
> e.g.
> f
> if the external address were; and restart the fileserver.
>>The solution that did work was to use the command "vos
>> changeaddr -oldaddr internalip -newaddr externalip". However, now all
>> of our OpenAFS clients are using the external ip, even though we would
>> prefer those within the NAT group to be using the internal ip. Any
>> suggestions?
>> Also, any explanations as to why 1. No sysid file is being created
>> would be appreciated, and 2. "vos listaddrs" returns blank?
> see if it's still true after the server is correctly configured.
> --
> Derrick