26 May
2017
26 May
'17
4:23 p.m.
We do not send outgoing traffic via amprgw so no change is necessary, but I updated
the address on our info page (that says "use our address instead of 169.228.66.251 as
your default gw").
It would probably be a good idea to change the route for 44.0.0.1 before the incoming
routes
are switched over, so it can be tested from the inside.
Rob
26 May
26 May
4:57 p.m.
New subject: Good News! and some changes coming
Thanks for making the change. That will help.
I've already tested the 44.0.0.1 address using loopback and it
works ok, and I've tested inbound using 44.128.0.1, and it
works ok too. I think things will be ok.
I don't like to bother the campus networking people more than I have to.
- Brian
On Fri, May 26, 2017 at 10:23:47PM +0200, Rob Janssen wrote:
We do not send outgoing traffic via amprgw so no
change is necessary, but I updated
the address on our info page (that says "use our address instead of 169.228.66.251
as your default gw").
It would probably be a good idea to change the route for 44.0.0.1 before the incoming
routes
are switched over, so it can be tested from the inside.
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2737
days inactive
2737
days old
1 comments
2 participants
participants (2)
-
Brian Kantor -
Rob Janssen