[OpenAFS] AFS-Client behind masquerading firewall

Derek Atkins warlord@MIT.EDU
04 Jan 2001 21:47:06 -0500


Sascha Silbe <sascha-ml-openafs-info@progbbs.staticky.com> writes:

>  DA> All output from the client cache manager exits via UDP port 7001, and=
> =20
>  DA> all responses to the cache manager (including callbacks) return via UDP
>  DA> port 7001.
> Fine. How about the source port of the callback packets? Is it the same as
> the destination port of the original request?

Yes.

>  DA> Callbacks can pretty much occur at any time. HOWEVER, the client
>  DA> cache manager 'pings' each server periodically to make sure it is
>  DA> still there.
> Wonderful. Does it use the same destination ports for both requests and pin=
> gs?

Yes.

>  DA> 	1) stop AFS
> Did that.
> 
>  DA> 	2) remove the AFS module
> /etc/init.d/afs seems to already do that for me.
> 
>  DA> 	3) restart AFS
> Did that, but no effect. :(

Hrm.. That's WEIRD.. When you restart AFS it should build new
connections to the AFS Servers, which should re-initialize any NAT
mappings.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available