26 May
2017
26 May
'17
4:07 p.m.
I have a concern that many gateway operators won't get the notification
that the amprgw gateway is changing address. If you know someone who
operates a gateway and DOESN'T subscribe to this mailing list, please
let them know about the upcoming change.
And it would be really cool if someone could browse the wiki and
update the information on amprgw. I'm afraid that its address may
be hardcoded in some of the 'how-to' pages.
- Brian
On Fri, May 26, 2017 at 11:28:51AM -0700, Brian Kantor wrote:
I've installed the routing software on the new
amprgw machine and tested
it, and it's working properly. In anticipation of moving the inbound
route for 44/8 from the old amprgw to the new one, it is time for people
to start using the AMPRGW.UCSD.EDU (169.228.34.84) address for their
outgoing tunnel endpoint.
That will require people who have a firewall to adjust their firewall rules
and any default routes they're using.
However, it is still necessary to allow the old amprgw.SYSNET.ucsd.edu
(169.228.66.251) in past your firewalls, as up until the moment that
we switch the 44/8 route from old to new, inbound traffic from the
Internet will still be coming from that old address.
Please make the change and test it as soon as practical so that you don't
get caught by the switch. Be sure to let me know if you lose connectivity
when you switch over to using the new machine for outbound traffic, and
we'll try to figure out what went wrong.
I anticipate a week or so before we can make the switch, so please keep
it in mind.
Thank you!
- Brian