- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ifconfig: bad value
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 06:12 AM
09-26-2001 06:12 AM
I'm having problems to configure a lan card (100BT) in a HP-9000 L2000 running HP-UX 11.0.
The fact is that it refuses to set a specific netmask value of 255.255.255.192 but in the other hand it accepts masks such as 255.255.255.0 or 255.255.255.240.
The command I'm using is:
ifconfig lan1 192.168.31.39 netmask 255.255.255.192 up
Any suggestion?
Thanks in advance!
Juan Carlos
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 06:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 06:28 AM
09-26-2001 06:28 AM
Re: Ifconfig: bad value
If disabling subnet mask checking works
dont forget to edit your
/etc/rc.config.d/netconf file
it will look like this
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=your.info.here
SUBNET_MASK[0]=your.info.here
BROADCAST_ADDRESS[0]=your.info.here
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 06:51 AM
09-26-2001 06:51 AM
Re: Ifconfig: bad value
doing in this may work
#ifconfig lan1 ip_addr netmask x.x.x.x broadcast x.x.x.x
#ifconfig lan1 up
and also make the entry in file /etc/rc.config.d/netconf as suggested by richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 07:17 AM
09-26-2001 07:17 AM
Re: Ifconfig: bad value
Have you tried it through SAM.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 08:01 AM
09-26-2001 08:01 AM
Re: Ifconfig: bad value
The only way around is ignoring the subnet mask check by setting ip_check_subnet_addr to 0 using ndd.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 10:18 AM
09-26-2001 10:18 AM
Re: Ifconfig: bad value
the ip_check_subnet_addr as mentioned will cause the mask/ip combinations to be interpreted under the newer classless rules. that becomes the default in 11i.
don't forget to put ip_check_subnet_addr in the nddconf file...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2001 12:26 PM
09-26-2001 12:26 PM
Re: Ifconfig: bad value
So in other words, you are trying to split up your network into 4 subnets using 255.255.255.192 however the first and the last are illegal according to RFC1122 because the first has 00 as its subnet bits and the last have 11 as its subnet bits.
The reason why 255.255.255.0 works is because its a standard subnet mask and the reason that 255.255.255.240 works is that 192.168.31.39 is now in the third subnet which does not contain all zeros or all ones. In other words, the third subnet is 0011 and that is legal because it does not break the RFC1122 rule.
Tony