28 Jul
2021
28 Jul
'21
10:41 a.m.
On 28 Jul 2021, at 13:45, Tony Langdon via 44Net
<44net(a)mailman.ampr.org> wrote:
On 28/7/21 9:18 pm, Antonios Chariton (daknob) via 44Net wrote:
That’s great! We are of the opinion that people should have a choice of how they create
their own networks and be able to do what works for them! This is what we want to achieve
with this proposal. You can do what works for you and what you like, I can do something
different, and a new user can do something completely different as well!
Thanks for the message,
Antonis
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.
For me, the router's capabilities are actually irrelevant. Talking
about my tunneled /24, I use static IPs for hosts that I want on this
network, and these have a single static route (2 actually) to route
44net IPs to the Pi that runs as an IPIP mesh router, which makes the
final decision as to where to send the packet.
Other hosts on the LAN don't know about these addresses or routing, and
ill attempt to use the ISP (as appropriate), where only those ranges
announced via BGP can be reached.
So for me, the static routing capabilities of the ISP router are
irrelevant, I've designed my network to ensure that's the case.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com