Hi Jeremy On Mon, Nov 17, 2025 at 04:27:03PM +0000, Jeremy Stanley wrote: :On 2025-11-17 09:44:20 -0500 (-0500), Jonathan Proulx wrote: :> CERN may be the only other people doing anything with AFS hopefully this :> catches someone's eye who will just know.... :[...] : :The OpenDev Collaboratory (in which OpenStack itself is developed) relies :heavily on AFS and has for around a decade run OpenAFS clients and servers on :OpenStack Nova instances. Sadly I don't have an answer for your dilemma, but :am similarly interested. How did I not know this, probably I forgot :) :In our case, our OpenAFS servers all have interfaces on directly-connected :provider networks. The only cases where we do AFS through floating IP are :OpenAFS clients. While I haven't observed performance degradation related :specifically to this, because we distribute our servers and clients globally :the latency is fairly debilitating to throughput already. This is encouraging that it is some configuration issue. So you do have clients with "private" network addreses using floating ip that access your AFS cell normally? For a long time we've used provider networks for our fixed ips and not used floating ips and all has been well. Using a private network with a neutron router doing NAT I can log in on the VNC console and things seem normal. When I attach the floating ip everything breaks. AFS isn't great with ip changes but this stays broken across soft reboots so I don't *think* it's an issue of connectign via the NAT IP first then trying to talk through the Floating IP. I'm currently trying to map out the actual packet flow and going a bit cross eyed with the the redundant network nodes and the dvr but I'll get there... -Jon -- Jonathan Proulx (he/him) Sr. Technical Architect The Infrastructure Group MIT CSAIL