I have installed the 1.16 on our gateway (without the safeguard for now) and it appears to be doing its thing. I can ping hosts on those test networks.
But there also is a network 44.102.128.0/24 and it does not work. Is that one okay or is it another config mistake? I suppose so, as its gateway 44.102.128.1 is routed to amprgw.
I'm afraid we need better directions and/or safeguards in the portal.
Rob
I think it's a mistake. It's confusing. The gateway belongs to n8lrf@comcast.net but the subnet belongs to kb8zgl@kb8zgl.net. I'm guessing that n8lrf entered a gateway hostname that belongs to the ampr side of the gateway rather than the commercial IP. - Brian
On Wed, Apr 05, 2017 at 11:53:40AM +0200, Rob Janssen wrote:
But there also is a network 44.102.128.0/24 and it does not work. Is that one okay or is it another config mistake? I suppose so, as its gateway 44.102.128.1 is routed to amprgw.
I'm afraid we need better directions and/or safeguards in the portal.
Rob _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Brian Kantor -
Rob Janssen