Unable to connect to network

[Kevin_107]

I have just cold installed V11. My netconf file is the same as before the upgrade.
Attached is my current netconf file. Do I need a patch due to the split in my sub-network ???

[melvyn burnard]

what does
ifconfig lan0
ifconfig lan1
netstat -in
netstat -rn
give you?
do they match what you want?

[Vincent Stedema]

if i'm correct, the ip address assigned to the second interface is in the zero subnet. By default, hp-ux doesn't like ip addresses that are not RFC-compliant.

Take a look at the "ndd" man page and especially the "ip_check_subnet_addr" parameter. You might need to install patches in order to make ndd work.

Regards,

Vincent

[Berlene Herren]

My thoughts exactly. Check your /etc/rc.log for error messages.

Berlene

[Vincent Stedema]

Here's a more detailed explanation of the steps you might take:

# ndd -set /dev/ip ip_check_subnet_addr 0
# ifconfig lan1 135.196.66.22 netmask 255.255.255.192 up

If this actually works, you should add the "ip_check_subnet_addr" parameter to /etc/rc.config.d/nddconf so it will be set to 0 at boot time.

Regards,

Vincent

[Ron Kinner · Accepted solution]

Your 192 mask gives you a subnet zero problem with any address in the 0-63 range. For some reason 11.0 started following the RFC just as it became obsolete.

run : ndd -set /dev/ip ip_check_subnet_addr 0

to make it happy with subnet zero.

You will want to edit /etc/rc.config.d/nddconf to permanently disable it:

TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_check_subnet_addr
NDD_VALUE[0]=0

If it still doesn't work you need to get the NDD and ARPA patches:

PHNE_26125 for NDD
PHNE_21767 or 27886

Ron

[Ravi_8]

Hi, kevin

there is a conflict in tour question,
if you did the cold install you wouldn't get any file of the previous ones. You are saying file is same as before the upgrade, i.e you have done the upgrade not the cold installation. As per this forum opinion cold installation is prefered over upgrade which gives you the cleaner environment

[Kevin_107]

No I carried out a cold install and then modified my netconf file to the same as it was before..I also have to problem of when it now boots up it does not recognize my hostname. when typing in hostname it issues "unknown". would the netconf problem be causing this ?!?!

[Darrell Allen]

I don't think your netconf is the problem with hostname returning "unknown". It looks to be specified correctly:
HOSTNAME=unix1

/sbin/rc1.d/S320hostname sets your hostname to that specified in netconf when you boot. Verify the symlink exists and points to /sbin/init.d/hostname.

Darrell

[Berlene Herren]

Again, check your /etc/rc.log. If there are other errors in there that need the correct hostname to start, make sure you do not have any misc files under /etc/rc.config.d

Berlene

[Ron Kinner]

I see that our netconf file uses double quotes around the hostname so perhaps you should try:
HOSTNAME="unix1"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1

If it still doesn't work:

See what the DNS thinks about your hostname:

nslookup unix1

perhaps there is another machine with the same name?

You might try a different name say "unix1a" or something like that just to see if that works.

/sbin/init.d/hostname
is what normally sets it based on what it finds in the /etc/rc.config and in the files in the rc.config.d directory. You could probably do:
/sbin/init.d/hostname unix1
or
uname -S unix1

and see what it says. The error message might tell you what's wrong.

There is a binary file at
/usr/bin/hostname which is what responds when you just type
hostname

Don't know how it works.


Ron

[rick jones]

FWIW HP-UX 11 follows the older subnet mask rules because that is what 10.20 did, and TPTB were unwilling to make a change late in the release cycle or with a patch.

However, 11i does default to the contemporary subnetmask conventions.

[Aziz Mamuwala]

Visit http://qixol.blogspot.com/2005/01/how-home-networking-works.html for a complete guide on networking.