Hello all, my name is Eloy and I’m new to the mailing list and to the 44/8 network.
As a new user I can tell what my experience has been so far.
-First is that most of the information needed is available in the Wiki, I spent a few
hours reading before doing anything else.
I was lucky enough that the configuration for Ubiquiti’s Edgerouter was in the Wiki as I
own one.
-I felt that I had enough information and proceeded to create an account in the portal,
and then asked for some IPs.
The answer took only two days.
-Adding the gateway was easy, but It seemed weird that I could have selected other
networks not assigned to me.
-I then created the IPIP tunnel in one of the interfaces of my router using the
instructions provided. I’m not scared of CLI but usually prefer GUI. It’s fine, no big
deal.
Instructions are well written and easy to follow, It did NOT work. I understood was I was
doing to the router and knew that It should have been working, but still, I did not work.
- Then I remembered that I read in the Wiki that I had register the IPs in the DNS.
-I could not find a way of contacting my coordinator directly from the portal, which
forced me to google his callsign and send him a direct email.
He answered very fast and added my IPs.
-After that everything has been working fine. Except that I can reach some servers from my
ISP but not from the tunnel, they respond to pings though.
If anyone could check that I did well, I would appreciate It. My network is 44.98.7.0/28,
right now only the gateway (44.98.7.1) and one server (44.98.7.2) are online.
All the process I described took little more than a week, I found the information I needed
or deduced It from some other.
Eloy
W4ERP
On Apr 7, 2019, at 2:28 PM, David Ranch
<amprgw(a)trinnet.net> wrote:
I hope the RFC1918 check is already made. If not
it could be added.
As I wrote before, there have been reasonable checks in place but people here
have asked them to be removed because they wanted to do what the checks prevented.
(like setting up a gateway with external address in net-44)
Maybe if the portal can flags specific issues, it could can then display additional
options like say:
- RFC1918 address space (10.x.x.x/8, 172.16.x.x/12, 192.168.x.x/16) is not an allowed
gateway address as it's non-routable over the Internet
- Specifying a 44.x.x.x address for a gateway is illegal except for very limited
situations (this 44.x.x.x gateways address is BGP hosted and you still want access to the
IP-IP tunneled system)
- IPv6 address space is not supported today
- etc
then under all that, offer a "bypass checks" option to let them do things
anyway?
--David
KI6ZHD
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net