1832085 Members
2844 Online
110037 Solutions
New Discussion

IP Restrictions on HPUX

 
rbk
New Member

IP Restrictions on HPUX

We are using HPUX on a Unix machine which communicates with wifi devices. The devices send data to the server trough several VLAN's with different subnets.

Because we need to expand we need to add another VLAN with wifi clients, however, will this server accept new DHCP clients from another subnet? Routing them from the switch to the server is no problem I've been told, unless there is a IP restriction on the server. Since I am new on administrating a HPUX machine I would like to know how I can find out what if there are any IP restrictions.
2 REPLIES 2
Jonathan Fife
Honored Contributor

Re: IP Restrictions on HPUX

What protocol do these clients use communicate with HPUX? Telnet/SSH/something proprietary?

Theoretically there shouldn't be any problem with communicating to these new devices as long as your default router has a valid route to them. If the default router does not, you'll have to add a new route to a new router for the new subnet.

If you are using tcp wrappers on your server (/etc/hosts.allow and /etc/hosts.deny) you may have to add the new IPs to those files.

One way to know for sure if you will have a communication problem is to set one of the devices up on the new subnet and try to ping it from the server.

Yes, there are quite a few variables here. If you can be more specific about protocols and your server setup we can eliminate some of those.
Decay is inherent in all compounded things. Strive on with diligence
Mike Keighley
Frequent Advisor

Re: IP Restrictions on HPUX

DHCP can be a problem, in conjunction with routers and VLANs, because DHCP uses a broadcast packet, and broadcasts are not usually forwarded by a router.

This can be dealt with either by configuring "udp forwarding" on your router, or adding a DHCP relay agent.

This isn't really an HP-UX subject. I suggest you consult your router documentation instead.

For a slightly tongue-in-cheek explanation (from a Cisco perspective) you might try http://www.routergod.com/trinity/
nil illegitimi root-andum