[44net] question regarding amprgw.sysnet.ucsd.edu

Hi all, I've just set up my net44 gateway using a Debian machine running in the cloud with a static IP. My plan is to use this machine as an IPIP-to-OpenVPN adapter so that I can run my subnet from home via my LTE connection, with will not support IPIP. I set up the machine with Debian linux and rip44d. I'm currently receiving the routing table from 44.0.0.1, and I'm able to ping several net44 machines in my area (44.4.2.153 and 44.4.50.1 for example), however, my linux machine is not able to ping 44.0.0.1. At first I assumed that this was a security policy, however, I'm also not able to access the ampr.org website from that machine now. in addition, I'm unable to ping my machine's net44 address from the internet. Is this a result of gw.ampr.org not updating it's gateway list, and thus not knowing how to route to me, or have I missed something obvious? Also, if anyone with a properly maintained gateway list could ping me at 44.4.36.1 and let me know the result, I'd appreciate it. Thank you, Blaine -- Blaine Forbort, K1QV Vallejo California