ifconfig : socket : Operation not supported

[Stephen Keane]

I have a system that is a test-bed, so it can get in all sorts of weird states. At the moment it's refusing to allow a socket creation of any description. Any network command that creates a socket fails with the 'Operation not supported' message. But commands that don't need a socket work OK.

e.g. lanscan, linkloop, lanadmin, netstat work, but ifconfig, ping don't work.

I've tried deleting and recreating the whole of /dev to no avail.

I've run SAM against the running kernel and all the subsystems seem OK, the kernel appears to support networking.

I've checked /usr /var /sbin and /etc (well recovered them off backup actually).

Any other ideas? (It's not a hardware issue BTW).

[RAC_1]

Do you have enough space in /tmp and /var/tmp??

Anil

[Steven E. Protter]

Restart the network after checking /etc/rc.config.d/netconf for anamalies

Make sure netfilter firewall isn't running.

SEP

[Stephen Keane]

/tmp and /var/tmp aren't full. Quite how much space is required to create a simple socket I don't know. /tmp in particular has plenty of space.

SEP - What do you mean by restart the network?

[RAC_1]

perms on /var/tmp and /tmp?? Are they correct?? Check /tmp and /var/tmp, can everybody write there?? (perms should 1777)

Does lanscan show all nics??

Anil

[Steven E. Protter]

/sbin/init.d/net stop
/sbin/init.d/net start

That resets the network.

Sorry for not provideing the detail. This sometimes clears this issue.

Also, go to the sd/ux database and install every network patch thats two or three stars with deps. This sometimes helps with this issue. Original suggestion is probably more practical.

SEP

[Stephen Keane]

/tmp and /var/tmp are both 777 owner bin, group bin. Both have at least 60MBytes free.

lanscan shows all NICs (there is only one)

Hardware Path = 10/0/12/0 = correct
Station Address is correct
Crd Instance = 0 = correct
Hdw State = UP = correct
Net-Interface/NamePPa = lan0 snap0 = correct
NMId = 1 = correct
MAC/Type = ETHER = correct
HP-DLPI Support = Yes = correct
DLPI Mjr# = 119 = correct

SAM seems happy except when it tries to run

/usr/sam/lbin/laninfo

which also gets the socket error.

[Stephen Keane]

SEP -

# /sbin/init.d/net stop
# /sbin/init.d/net start
ERROR: lan0 interface: ifconfig: socket: Operation not supported
ERROR: Failed to add route entry because its interface is not
yet initialized. May need to add this route entry with
a route commad [sic] after the interface is up:
add net default: gateway X.X.X.X: Network is unreachable.

BTW O/S is hpux 11.11 on a B1000

[RAC_1]

From ifconfig man page : "Messages indicate if the specified interface does not exist, the requested address is unknown, or the user is not privileged and tried to alter an interface's configuration."

Check if you have all the above or not.

[Stephen Keane]

requested address is unknown - What address?

I am trying to run (logged in as root)

# ifconfig lan0

I have

crw-rw-rw- 1 bin bin 14 0x000000 /dev/lan0
crw-rw-rw- 1 bin bin 14 0x000001 /dev/ether0
crw-rw-rw- 1 bin bin 14 0x000080 /dev/diag/lan0

ioscan -Clan -fn gives

lan 0 10/0/12/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0 /dev/lan0

[RAC_1]

lanadmin
reset lan
lanadmin and display
is operational status up??
Is /etc/rc.config.d/hpbtlanconf file OK??

And last but not least, network patches.

Anil

[Stephen Keane]

The machine is patched fully up to date.

landamin -> lan -> reset

lanadmin -> lan -> display

Administration Status (value) = up(1)
Operation Status (value) = down(2)

Take your pick as to whether it is up or down!

[Stephen Keane]

/etc/rc.config.d/hpbtlanconf is identical to another machine I have, not that there's a lot in it anyway if you ignore the comments.

[Stephen Keane]

Administration Status (value) = up(1)
Operation Status (value) = up(2)

I guess it's finished its self-test then.

[Stephen Keane]

Is there any way of checking whether the kernel itself supports sockets/UDP/TCP?

I ran SAM and looked at subsystems and they all seemed to be configured in OK.

CD-ROM/9000 In/In
DLPI/9000 In/In
FCT1 FCMS In/In
LAN/9000 In/In
NFS/9000 In/In
SIO DIAGNOSTIC SUBSYSTEM Out/Out
STREAMS/9000 In/In
WSIO DIAGNOSTIC SUBSYSTEM In/In

[Craig Gilmore]

The lan0 interface looks OK, from the information you have detailed, and my off-the-top memory.

Question, What does the loopback interface look like?

Netstat -in should list both the lan0 interface and the loopback.

Netstat -rn would also help in looking at what could be wrong on the system.

Thanks!

[Ermin Borovac · Accepted solution]

What happens when you do

# sh -x /sbin/init.d/net.init start

[Stephen Keane]

Ermin gave me the clue I needed.

What needed to be done was

autopush -f /tmp/stcp.conf

where /tmp/stcp.conf contained

-----------------------
tcp -1 0 tcpm
udp -1 0 udpm
rawip -1 0 rawipm
arp -1 0 arpm
-----------------------