Mike, the problem is that the n8lrf gateway has an address on the subnet instead of a commercial IP address and is therefore not reachable. - Brian

On Wed, Apr 05, 2017 at 07:43:15AM -0400, Michael Wolthuis wrote:

Rob, I have managed that subnet since early 90's. What is your concern? You are welcome to be assigned ips on it in Kent County. I have several other subnets for our HamWan project and even an IPv6 assignment from ARIN.

How can I help meet your goals?

Feel free to call me at 616-422-5412 or on the 145.27 Lowell repeater

Mike KB8ZGL

Sent from my iPhone

...

On Apr 5, 2017, at 6:13 AM, Brian Kantor Brian@UCSD.Edu wrote:

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