Roger, Thanks for the tip. As a test I changed the MTU in my network card. Everything loaded fine, but wouldn’t want to be doing that to every device that I connect to the network. Instead of doing MSS Clamping I added one line to the tunnel setup in the router to specify the MTU size. That did the trick :D
set interfaces tunnel tun0 mtu 1480
That could be added to the EdgeRouter setup instructions in the wiki.
Eloy W4ERP
On Apr 8, 2019, at 5:44 PM, Roger Andrews va7lbb@rezgas.com wrote:
Eloy, I had the same issue and you need to do MSS Clamping. At least that’s what I was told and it fixed mine. Roger VA7LBB
From: Eloy Ritter de Monredont eritter@me.com Subject: Re: [44net] RIP problems? Date: April 7, 2019 at 3:47:13 PM PDT To: AMPRNet working group 44net@mailman.ampr.org
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net