HP-UX 10.2 to LINKSYS Router???

[David Edwards]

How can I get a Unix workstation to access the web when connected to my home PC network (via Linksys router)
What do I need to set in SAM?
I hope someone can help, I've tried and given up several times.
Thanks!!
...Dave kd2e@comcast.net

[Ron Kinner]

Most likely your Linksys is set up as a DHCP server so all you should have to do is use SAM to turn on DHCP.

Enabling DHCP on a System Not Initially Configured with DHCP
If a system has been set up without using DHCP, but you would like to start using it, the following steps may be taken.

The system's hostname and IP address may change based on what the DHCP server assigns to it the first time it boots.

There are two methods for enabling DHCP on a system that is not currently using it:


The first method is to use SAM.

As root, run sam.
Double-click [Networking and Communications].
Double-click [Network Interface Cards].
Highlight the card you wish to enable DHCP on, go to the [Actions] pull-down menu and select [Configure].
Single click the [Enable DHCP] button. If [Enable DHCP] appears grayed-out, you will need to use the alternate method for enabling DHCP described below.
Single click [OK] and exit SAM.
Your system will now begin using DHCP after the next reboot. Please note that all of the current networking parameters will be overridden with new values supplied by the DHCP server. If for some reason the system cannot contact a DHCP server during the next reboot, it will continue to use its current networking parameters.

If you suspect that your system had problem contacting the DHCP server, you can examine the auto_parms log file (/etc/auto_parms.log) to determine if the lease request was successful.

The second method for enabling DHCP over a particular network interface is use a text editor (such as vi or emacs) to edit the /etc/rc.config.d/netconf file. In the header of this file, you will find some brief instructions regarding a variable named DHCP_ENABLE. This variable is tied by an index number to an individual network interface. For example, in the following block:
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=15.1.50.76
SUBNET_MASK[0]=255.255.248.0
BROADCAST_ADDRESS[0]=""
DHCP_ENABLE[0]=1

Here, the variables are instructing the system to use the lan0 interface when attempting to contact a DHCP server. Similarly, if the lease request is successful, the above IP_ADDRESS variable would be updated to reflect the new value supplied by the DHCP server.

If the DHCP_ENABLE variable was set to 0 or if the variable did not exist, no DHCP operations would be attempted over the corresponding network interface.

As noted in the first method of enabling DHCP, if the variable DHCP_ENABLE does not exist for a particular interface, the SAM tool will display a grayed out [DHCP enable] button.

In this case, you will need to add the variable definition to a specific interface variable block. As an example, you would need to add DHCP_ENABLE[2]=1 to the following interface variable block in order to enable DHCP on the lan1 interface:

INTERFACE_NAME[2]=lan1
IP_ADDRESS[2]=15.1.50.89
SUBNET_MASK[2]=255.255.248.0
BROADCAST_ADDRESS[2]=""

The contents of /etc/rc.config.d/netconf for this definition block should now look like the following:


INTERFACE_NAME[2]=lan1
IP_ADDRESS[2]=15.1.50.89
SUBNET_MASK[2]=255.255.248.0
BROADCAST_ADDRESS[2]=""
DHCP_ENABLE[2]=1

Correspondingly, you could disable DHCP over a particular interface by setting the variable to "0".

Again, as in the first method, the system will only begin using DHCP after the next reboot.



From:

http://sequoia.ict.pwr.wroc.pl/~iro/hp/hp_install/APPXA.HTM

Ron

PS What model Linksys router do you have?

[David Edwards_1]

Ron... I am not sure this is the correct way to reply to you, but I am new to this forum thing.
From within SAM, I can enable DHCP, but then it wants an 'Internet Address' I suspect that is the IP address that the DHCP will change on the next boot?
It also says I need at least one alias. I dunno what that is about. I will try the vi editor and check the rc.config.d file.
Can I email you direct on this?
...Dave

[Ron Kinner]

This is fine. If we keep it here one of the gurus will jump in and set me straight if I tell you something wrong.

Besides if I email you I can't earn any points and I'm trying to get my pointy hat. ;-)

As I understand it the alias is just a label to be used to refer to the NIC (Network Interface Card - the Ethernet connection) you have highlighted in the previous step, assuming you only have one NIC, then lan0 will do. The ip address is something you have to have but which will be changed as soon as we hear from the router.
I would use 192.168.0.150. That should work and shouldn't conflict with the router which is probably 192.168.0.1.

Once you get that set up verify that you have the correct cable. Suspect you may need a crossover cable between the router and the PC unless you have a hub in between. Might depend on which LinkSys you have tho.

Do
lanadmin
lan
display
and verify that it says you are up up.

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

If you don't see that then you probably have the wrong cable. There should be a link light on the router that goes out when you unplug the cable.



Ron

[John Bolene]

This is actually so simple that you will shoot yourself.

Linksys has a range of static IP's, normally 192.168.1.2 thru 192.168.1.99 or what is left after you tell the Linksys where to start with the DHCP addresses.

Just use the router address 192.168.1.1 as the gateway, use one of the static IP's with 255.255.255.0 netmask, setup DNS to point to the DNS that the Linksys is given from the braodband provider, also put all your 192.168 addresses in the host file with resolv.conf configured to look at files first, DNS second.