28 Jul
2021
28 Jul
'21
6:18 a.m.
Hello, thank you for your comment. Please see my reply below:
On 28 Jul 2021, at 12:57, g4ugm via 44Net
<44net(a)mailman.ampr.org> wrote:
Fellow Hams,
I don't see how this helps amateurs with ISP provided routers. All the ones I have
encountered supply a single gateway via DHCP and do not permit additional routing
options.
So anything on the routers ring fenced LAN will route any "routable" packet,
and all packets starting 44.x.x.x are routable to the ISPs router.
So if you start splitting the 44 range then you are you going to have to manually add
routing entries to each device on your network?
Surely routing should be done in a router not spread round individual devices?
If you want to get involved in networking you should get a decent router.
Dave
G4UGM
Currently the people that reached out told us that their routers support static routing.
It could be limited, e.g. 8 or 32 entry limit, but they support it. For reference, they
are FritzBox, ZTE, TP-Link, etc. By splitting the space they can add a single entry,
44.128/10 to their radio or to their Raspberry Pi VPN server and keep the rest of the
traffic to their ISP’s default gateway.
It is entirely possible that some routers will not support static routing at all. I can
imagine this could be the case for similar models. If they do not have this capability,
then unfortunately there’s nothing we can do with this equipment to provide access to
44.128/10. However, since 44.0/10 is on the Internet, users can still access this network
just fine.
Users that fall under this category will probably have to have a VPN set up on their
devices or opt-in for a better router. The reason the split is still beneficial is that
although we can’t support these users due to technical limitations, we can at least
support all the others whose equipment supports the configuration of static routes.
I hope this addresses your concerns.
Antonis