Bob, following your reply I remembered that that the gateway (44.98.7.1) is setup to not respond to pings and that, for now, the 44.98.7.2 is assigned to the WAN interface of a virtual router running Untangle which also does not respond to pings. I though the management interface of the hypervisor was connected and using that IP but that was a confusion on my side, it’s using my ISP’s IP. I’ll be changing that later on.
Now the issue is that the virtual machines on the LAN side of the virtual Router do browse the internet fine when the WAN is connected to the VLAN that correspond to my ISP, but when connected to the 44/8 network most sites load well but some don’t, I can ping them though. The issue is the same using my personal computer when connected to the 44/8 network.
Anyways, I just wanted to comment on my experience as a new user. I think that it could help improve the site. The browsing issue could be addressed in a different thread.
Eloy W5ERP
On Apr 7, 2019, at 5:54 PM, Marius Petrescu marius@yo2loj.ro wrote:
That is to be expected, since the ER instruction only tell the reader how to set up a point to point tunnel to the ampr-gw.
There is nothing related to the mesh network, and there is no way for it to function with that setup.
I will try to find some time to do a complete rework for the EdgeRouter in the Wiki.
Marius, YO2LOJ
On 08.04.2019 00:23, Boudewijn (Bob) Tenty via 44Net wrote: Eloy,
I can reach your commercial address with https but not 44.98.7.1 or 44.98.7.2 with ping/http, etc. I tried your 44 addresses from 44.135.85.151 near Toronto.
73,
Bob VE3TOK
On 2019-04-07 3:26 p.m., eritter via 44Net wrote: 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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net