Where the RFC and IANA define Class C in 1996, the 'HP 3000/ix Network Planning and Configuration Guide' (36922-90031) references "ARPA" in the 1992 edition.

Someone pre-defined Class C in the range of 192.0.0.x through 223.255.255.x (anything starting with bits 110# ####). These appear to only be valid with a last octet from 1 to 254.

FWIW - I checked 224.168.168.16 and got "E 224.168.168.016"

Brief checks in @.NET.SYS did not have a configuration file pop out. There may be one if someone has time to look deeply.  (maybe posix shell)

One workaround is by using a 172 based address if more than 254 devices are needed in a private space.  

Mark's thought to put a firewall between the 3000 and the rest of the network and NAT the ports to be used would be quicker to implement.

Neal Kazmi
800-682-0200
360-568-7771
(Mon-Fri, 8-5 Pacific)


-----Original Message-----
From: HP-3000 Systems Discussion <[log in to unmask]> On Behalf Of Mark Ranft
Sent: Thursday, May 11, 2023 8:17 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] NMMGR - VALIDATION ERROR

You are correct 192.168.0.1 doesn't work.  This appears to me to be a bug.  Anything outside of 192.168.111.1 to 192.168.111.254 doesn't work.  I am not a network person, but perhaps setting up a NAT for 192.168.111.1 to 192.168.0.1.

Mark Ranft
Pro 3K
(612)804-2774

-----Original Message-----
From: James B. Byrne <[log in to unmask]>
Sent: Thursday, May 11, 2023 10:18 AM
To: Mark Ranft <[log in to unmask]>
Cc: [log in to unmask]
Subject: RE: [HP3000-L] NMMGR - VALIDATION ERROR

On Thu, May 11, 2023 09:57, Mark Ranft wrote:
> Hi James,
>
> NMMGR and the HP3000 is correct 192.168.0.x is a class C network 
> subnet.  I copied the below information from a internet search.
>
> Address ranges to be use by private networks are:
> Class A: 10.0. 0.0 to 10.255. 255.255.
> Class B: 172.16. 0.0 to 172.31. 255.255.
> Class C: 192.168. 0.0 to 192.168. 255.255  <-- This is class C by 
> name, but it has a 255.255.0.0 range.  Weird!
>

The C class determination for 192.168.0.0/16 was a curiosity and I appreciate the clarification.  I checked the RFC and found this:

RFC 1918        Address Allocation for Private Internets   February 1996


3. Private Address Space

   The Internet Assigned Numbers Authority (IANA) has reserved the
   following three blocks of the IP address space for private internets:

     10.0.0.0        -   10.255.255.255  (10/8 prefix)
     172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
     192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

   We will refer to the first block as "24-bit block", the second as
   "20-bit block", and to the third as "16-bit" block. Note that (in
   pre-CIDR notation) the first block is nothing but a single class A
   network number, while the second block is a set of 16 contiguous
   class B network numbers, and third block is a set of 256 contiguous
   class C network numbers.

The problem remains that while NMMGR will validate 192.168.216.1 as a gateway it will not validate 192.168.0.1 despite the IP net-mask being 255.255.0.0.

-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
   Unencrypted messages have no legal claim to privacy  Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[log in to unmask]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *