27 May
2017
27 May
'17
4:23 a.m.
Hi guys,
I tried to set up my router so match the current situation, so here are
the steps to get it working:
1. 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.
2. Change your endpoint in the current ucsd-gw interface from
169.228.66.251 to 169.228.34.84
3. Delete the interface ampr-169.228.34.84 in Interfaces
4. 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:
3. Add a new IPIP interface, lets say 'ucsd-gw-old' with endpoint
169.228.66.251 (like the old one)
4. Add an unused 44 local ip other than your gateway IP witm mask /32 to
the 'ucsd-gw-old' interface in IP->Addresses
5. Add similar connection marks as the ones for ucsd-gw for uscd-gw-old
under IP->filter->mangle
6. 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
27 May
27 May
4:30 a.m.
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:
1. 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.
2. Change your endpoint in the current ucsd-gw interface from
169.228.66.251 to 169.228.34.84
3. Delete the interface ampr-169.228.34.84 in Interfaces
4. 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:
3. Add a new IPIP interface, lets say 'ucsd-gw-old' with endpoint
169.228.66.251 (like the old one)
4. Add an unused 44 local ip other than your gateway IP witm mask /32
to the 'ucsd-gw-old' interface in IP->Addresses
5. Add similar connection marks as the ones for ucsd-gw for
uscd-gw-old under IP->filter->mangle
6. 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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
8:07 p.m.
Things like this need to be in a searchable wiki.
Personally, I really like the groups.io platform, it can support the
mailing lists, a wiki, and a file store.
On Sat, May 27, 2017 at 1:23 AM, Marius Petrescu <marius(a)yo2loj.ro> 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:
1. 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.
2. Change your endpoint in the current ucsd-gw interface from
169.228.66.251 to 169.228.34.84
3. Delete the interface ampr-169.228.34.84 in Interfaces
4. 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:
3. Add a new IPIP interface, lets say 'ucsd-gw-old' with endpoint
169.228.66.251 (like the old one)
4. Add an unused 44 local ip other than your gateway IP witm mask /32 to
the 'ucsd-gw-old' interface in IP->Addresses
5. Add similar connection marks as the ones for ucsd-gw for uscd-gw-old
under IP->filter->mangle
6. 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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
--
------------------------------
John D. Hays
K7VE
PO Box 1223, Edmonds, WA 98020-1223
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
8:17 p.m.
John,
This is an momentary fix for those who like testing. For the others, the
old setup still works.
After the migration, this will not be necessary anymore and the old
setup steps will apply, as described in the setup documentation, except
of the change of the IP.
So there's really no need for it to land in a wiki because it will
become obsolete in a short while.
Marius
On 28.05.2017 03:07, K7VE - John wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Things like this need to be in a searchable wiki.
Personally, I really like the groups.io platform, it can support the
mailing lists, a wiki, and a file store.
On Sat, May 27, 2017 at 1:23 AM, Marius Petrescu <marius(a)yo2loj.ro> 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:
1. 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.
2. Change your endpoint in the current ucsd-gw interface from
169.228.66.251 to 169.228.34.84
3. Delete the interface ampr-169.228.34.84 in Interfaces
4. 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:
3. Add a new IPIP interface, lets say 'ucsd-gw-old' with endpoint
169.228.66.251 (like the old one)
4. Add an unused 44 local ip other than your gateway IP witm mask /32 to
the 'ucsd-gw-old' interface in IP->Addresses
5. Add similar connection marks as the ones for ucsd-gw for uscd-gw-old
under IP->filter->mangle
6. 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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2734
days inactive
2735
days old
3 comments
2 participants
participants (2)
-
K7VE - John -
Marius Petrescu