5 Apr
2017
5 Apr
'17
6:13 a.m.
I think it's a mistake. It's confusing. The gateway belongs to
n8lrf(a)comcast.net but the subnet belongs to kb8zgl(a)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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net