28 Jul
2021
28 Jul
'21
5:56 p.m.
Hello everyone,
Rob PE1CHL via 44Net je 28. 07. 21 ob 11:33 napisal:
However, what we have here in the Netherlands is a
combination of the two. It is a radio
network, with additional internet tunnels to join areas without radio links between them
(at least
as an interim measure), but also it is internet routed and announced as a /16. We do
not
want to become an intranet!
I think that use case has to remain, and has to be detailed more in the proposal.
We in S5-Slovenia are also going the similar way as Netherlands - to use
an 44.150/16 mostly as 'Intranet' but few of those IPs will be
reachable from public Internet. By BGP announcing the whole /16, then
selectively filtering traffic on the firewall.
We see this way the simplest for both ARDC and our end users, who make
their allocated IPs publicly accessible by a simple click on the
forthcoming web application.
Antonios Chariton (daknob) via 44Net je 28. 07. 21 ob 12:24 napisal:
If you determine that you need to be connected to both
networks, and
connection to the Intranet is not simply enough, you can request a
matching allocation (I think /17?) in 44.0/10, and then set up a
“netmap”. This is an iptables target (also available in RouterOS)
that >
replaces the first bits of an IPv4 address. With this, you can leave
all the IPs intact so you can communicate with
Germany, and on the
single point that you connect to the Internet you can advertise the
new prefix, and perform “netmap” of the entire old /17 to the entire
new /17. So the Internet will see you as 44.0/10 and the “radio
network” / Intranet will see you as 44.128/10.
Avoiding NAT in any form is one of the biggest advantages of using 44
addresses. I think we need to stick with that goal.
Best 73
Janko S57NK