RE: [leafnode-list] Leafnode Daemon cannot be connected to

["Bulgrien, Kevin" <Kevin.Bulgrien@xxxxxxxxxxxxxxxxxx>]

192.*.*.* addresses are usually class C addresses with a net mask of 
255.255.255.0.  His example follows conventional use of a locally
administered network IP address.  FYI:

Private addressing conventions:

NET_ID					RFC 1918 PRIVATE ADDRESSES
0-127		Class A			10.0.0.0-10.255.255.255
128-191	Class B			172.16.0.0-172.31.255.255
192-223	Class C			192.168.0.0-192.168.255.255
224-239	Class D (multicast)     -
240-255	Class E (experimental)  -

--- 
Kevin R. Bulgrien, Product Engineer
Mailto:kevin.bulgrien@xxxxxxxxxxxxxxxxxx

Vertex RSI, A TriPoint Global Company         http://www.tripointglobal.com/
Controls & Structures Division 
1915 Harrison Road                                    Tel: 903-295-1480 x288
Longview, TX 75604-5438                               Fax: 903-295-1479

> -----Original Message-----
> From: Clemens Fischer [mailto:ino-waiting@xxxxxxx]
> Sent: Saturday, November 16, 2002 10:32 AM
> To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [leafnode-list] Leafnode Daemon cannot be connected to

> i think the netmask for a 192.168.x.y IP is supposed to be
> 255.255.0.0, but as you did not post the clients IPs, this might not
> be the solution.  and i think you don't need entries in hosts.deny, so
> you could concentrate on hosts.allow.  if you're using inetd, it too
> has logging!
> 
> clemens

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list