Re: [44net] Can't add redundant AMPR gateway to portal

AMPR IPIP tunnels are currently broken for our network, 44.24.240.0/20. 44.24.240.0/20 is multi-homed. We have two edge routers. We originate IPIP tunnels from both routers, but other AMPR systems only accept IPIP traffic from one of the routers. Why? The second gateway IP is not in the encap file. The portal will not let us add a second gateway IP for 44.24.240.0/20, because one already exists. Can we get this restriction lifted? Second issue: Something changed with the encap file download process. The script that builds our IPIP tunnels uses "curl https://portal.ampr.org/getdata.php" to download the encap data. A few days ago this was working just fine. Now the returned file is empty. Loading that url with a web browser also returns an empty page. However, if I click the "download encap" link at https://portal.ampr.org/gateways_list.php, it works fine. Some funky session bug, I assume. Please fix this issue, or point me towards the documentation that explains a better way to get the encap data. Tom KD7LXL On Tue, Mar 25, 2014 at 11:40 AM, Bart Kus <me(a)bartk.us> wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > Screenshot > > This network (44.24.240.0/20) is available via both 209.189.196.68 and > 198.178.136.80. However, I'm unable to list more than one point of contact. > I realize this was probably a design decision at some point, but it doesn't > seem like a good idea from a redundancy perspective. > > --Bart > > PS: If you're wondering why the image looks like crap, it's to satisfy the > puny 32kB message size limit of the list. >