HP3000-L Archives

August 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Mon, 4 Aug 1997 11:20:46 -0700
Content-Type:
text/plain
Parts/Attachments:
Re: (23 lines)
Denys writes:
> Er Jim, remember that for TCP/IP address 010.xxx.xxx.xxx is NOT the same
> as 10.xxx.xxx.xxx.  010 is interpreted as an octal address, in this case
> a decimal value of 8.  I doubt this is your problem, but be aware.

Except in NMMGR, which I believe does not do the octal interpretation,
and in fact pads everything out to three digits with zeros.  But Denys is
right that just about every UNIX/C derived networking config file (such
as bootptab, etc., which means just about everything *except* NMMGR)
uses the C library to read the number in, so you get the standard C
behavior that a leading 0 means that the number is octal.  This is a
rude surprise the first time you learn about it (probably the hard way).

In reference to the original problem, probably the easiest solution is to
change the 10.x.x.x address to one compatible with the existing 192.x.x.x
network for testing purposes.  Then when you move the system, you'll
change the address back, and you'll have to debug all of the router stuff,
but all of the NetBase config and all the other testing you do should
still be valid.  Once you get the machines to PING each other, all the
other stuff you did before should start working again.

G.

ATOM RSS1 RSS2