As an addendum:
If everything is up and running, cleanup any "unknown" interfaces in your Interface->interface lists
On 27.05.2017 11:23, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hi guys,
I tried to set up my router so match the current situation, so here are the steps to get it working:
- add a filter to Routing->prefix lists to drop 44.128.0.0/16, prefix
length 16-32, similar to the one for 44.0.0.1
(IMPORTANT - the dynamic created ampr-169.228.34.84 would interfere with our tunnel base interface , having the same IP endpoint and taking precedence over it being newer)
For the RIP protocol, you should now have drops on 44.0.0.1 pref len 32, 44.128.0.0 pref. len 16-32 and your local subnets (if any are there), accept the rest.
- Change your endpoint in the current ucsd-gw interface from
169.228.66.251 to 169.228.34.84
Delete the interface ampr-169.228.34.84 in Interfaces
Delete the now invalid route to 44.128.0.0 in IP->Routes
Wait a while for the first RIP update. Mesh access should work fully now and you should see RIP updates in Routing->RIP->Routes
If you need access from internet to your 44net hosts, these are the additional steps:
- Add a new IPIP interface, lets say 'ucsd-gw-old' with endpoint
169.228.66.251 (like the old one)
- Add an unused 44 local ip other than your gateway IP witm mask /32
to the 'ucsd-gw-old' interface in IP->Addresses
- Add similar connection marks as the ones for ucsd-gw for
uscd-gw-old under IP->filter->mangle
- Check your firewall filters to allow incoming connections from
ucsd-gw-old like tho ones from ucsd-gw (input and forward)
These latter changes will be removed after full switch to the new gateway.
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net