6 Jun
2017
6 Jun
'17
1:21 p.m.
I didn't remove the 44.0.0.2/32 route until this morning - sorry, had
other things on my mind. But it shouldn't have caused any difficulties
while it was there.
All services and routing have been moved to the new amprgw on 169.228.34.84.
- Brian
On Tue, Jun 06, 2017 at 08:36:04AM -0400, lleachii--- via 44Net wrote:
Can someone explain exactly how the 44.0.0.2/32 route
is causing an issue on
the tiks?
Because that route could have been removed Monday anyway, as it would no
longer be needed if the migration was completed.
Did all services and routing move to New_AMPRGW yesterday?
73,
- Lynwood
KB3VWG