Brian,
root@router:~# ip route get 44.128.0.0/16 from 44.60.44.1 44.128.0.0 from 44.60.44.1 via 169.228.34.84 dev tunl0 table 44 cache window 840
Cool, then as long as we have uptime on that day, we should at least continue to get routes and talk to AMPRNet. At any case, OPs will need to change any scripts that seed the Old_AMPRGW IP to 169.228.34.8.
- KB3VWG
Your gateways and firewalls can start learning it, and I can use it to debug the new installation. What we'll do is change the routing at the UCSD border to direct traffic for that one /16 subnet to the new amprgw instead of the old one right away, and after everything appears to be working properly, we'll change the route for the entire 44.0.0.0/8. Both systems already have a secondary address of 44.0.0.1, so that changeover will be automatic.