DHCP on HPUX 10.2

[mhess_1]

We just switched over to AT&T Uverse for our Internet connectivity. They modem (two wire gateway) supposedly cannot perform route mapping for the static IP assigned to my HPUX 10.2 machine. According to AT&T we can assign the machine a statid IP, but will have to use DHCP. I have changed the IP in /etc/rc.config.d/netconf and set DHCP to 1, but I can still not access the outside world form this machine. What else can I check or configure to get Internet connectivity on this machine. I'm sure you'll need more details, so please let me know what info I can provide to help you help me. Thanks. Mark

[Steven Schweda]

> [...] They modem [...]

Not a very complete description. Is this
thing an IP router (what's its IP address?)
or a bridge (to what), or what? Can you talk
directly to it in some way?

> [...] According to AT&T we can assign the
> machine a statid IP, but will have to use
> DHCP.

Huh?

What is the system's IP address? Default
route?

Do you have other systems on your LAN which
do work? What are their addresses and
routes?

[Michael Steele_2]

a) you should be talking to ATT
b) Run 'set_parms initial' to configure your HP-UX networking environment.

In preparation, record your current environment with netstat -rn, lanscans, cat /etc/rc.config.d/netconf, etc. Refer to the man pages of set_parms and gather the information ahead of time before executing.

[mhess_1]

My apologies. Let me try and clarify. First off newbie here. We are a small outfit and do not have an IT person, so must fight through networking issue with the limited resources we have.

1) We've contacted AT&T several times (Their Uverse support and ConnecTech support). They have no answer for us as they claim they are unfamilir with UNIX. Beedn through several rounds with them and have gotten no where. They do say, that their modem, does support static IPs, but not IP mapping or port forwarding.

2) The gateway is a "Two Wire" AT&T calls it the Two Wire Gateway. It is bascially their modem. Their is a switch behind that, but no router.

3) We have several PCs hooked up to this new network using DHCP and their connectiviry is fine.

4) We have one PC acting as a server on the network (IP: 75.60.238.33). It is set to DCHP. Once we set that PC to DCHP our "Two Wire Gateway" sees the machine and we can then reasign the internal IP (192.168.x.x) to the static IP 75.60.238.33.

5) On the HPUX 10.2 machines I have changed the IP address to the static IP of 75.60.238.36 The output of netstat -rn is:

Routing Tables
Dest/Netmask
127.0.0.1
75.60.238.36
75.60.238.32
127.0.0.0
default

Gateway
127.0.0.1
75.60.238.36
75.60.238.36
127.0.0.1
75.60.238.46

Flags
UH
UH
U
U
UG

Refs
0
0
2
0
0

Use
412
32
0
0
0

Interface
lo0
lan0
lan0
lo0
lan0

In /etc/rc/config.d/netconf I have set the IP address we want (75.60.238.36) and also set DHCP=1. When we reboot the system, however, the DHCP setting goes back to 0.

Accoring to AT&T once we set the HP machine to DHCP and all is working wel, the Two Wire Gateway" will see the mahine and we can tell it to use the static IP.

Problem now is that I do not know how to set the machine to use DHCP....and stay that way after reboot. My HPUX 11.0 machines allows this to be set using SAM, but I can not find how to do this on my 10.2 machine.

I hope this provides more usefule information.

[Michael Steele_2]

For you to use a static ip you need to log into the ATT modem and configure that ip into the modem.

Again, call ATT for there should be a way for you to access the modem.

For example, via an internet browser with an ip address of the modem -

[mhess_1]

We can access the modem for configuration, but it does not see the HPUX machine unless the machine is using DHCP. This is all AT&T can tell us. We've been through several rounds with AT&T support personnel, and they say the client machine must be set for DHCP...and apparently then we can tell the modem to use the static IP. They also say that this modem does not support IP mapping or routing (inbound and outbound IP mapping services - not sure about the correct teminology for this). Confusing, I know. Unfortunately, AT&T states anything beyond that is out of their support capability. Go figure.

Is there anyway to make the DHCP=1 setting stick in the /etc/rc.config.d/netconf file - even after rebooting? It goes back to 0 each time aftger reboot.

[Michael Steele_2]

http://docs.hp.com/en/5969-7067/ch04s03.html

[Steven Schweda]

Disclaimer: I generally avoid using DHCP
with my serious computers, and I haven't
touched an HP-UX 10.20 system for many years.

> 3) We have several PCs hooked up to this
> new network using DHCP and their
> connectiviry is fine.

Ok.

> What are their addresses and routes?

Still wondering. Isn't there a Network
Control Panel if an ipconfig program or
something which might reveal these things?

> [...] their modem, does support static IPs,
> but not IP mapping or port forwarding.

If I can trust "http://ws.arin.net/whois",
then you'd seem to have the block of
addresses from 75.60.238.32 - .47. Which of
those addresses are available for DHCP, and
which (if any) are available as static
addresses? (Ask AT&T?)

> 4) We have one PC acting as a server on the
> network (IP: 75.60.238.33). It is set to
> DCHP.

Ok. I can see a Web server at that address.
(Does it make any sense to run a server with
a dynamic address, or has its address been
fixed in some way, so that it'll always be
the same, even though it's assigned by a DHCP
server?)

> Once we set that PC to DCHP our "Two
> Wire Gateway" sees the machine

Whatever that means.

> and we can
> then reasign the internal IP (192.168.x.x)
> to the static IP 75.60.238.33.

Now I'm mystified. Who's reassigning what
where? Who has a 192.168.x.x address?

> [...] The output of netstat -rn is:

... not formatted in any convenient way.
(How'd you do that?)

I tentatively read that as having an address
of 75.60.238.36, and a default route gateway
of 75.60.238.46. Is that what the PCs
(Windows?) are using as their default route
gateway?

> Dest/Netmask

I don't see any netmasks? What is the
netmask on that 75.60.238.36 address?

> In /etc/rc/config.d/netconf I have set
> [...]

Seeing the actual file might be more helpful
than seeing only your interpretation of the
highlights.

> Accoring to AT&T once we set the HP machine
> to DHCP and all is working wel, the Two
> Wire Gateway" will see the mahine and we
> can tell it to use the static IP.

I don't know what that means.

> [...] I do not know how [...]

See "10.20" section of the disclaimer, above.

[Steven Schweda]

> [...] (two wire gateway) [...]

> [...] "Two Wire" AT&T calls it the Two Wire
> Gateway. [...]

Do you mean a "2Wire 3800HGV-B Residential
Gateway" (as in "2wire.com")?

If the user guide for the 2701HG:

http://www.2wire.com/pages/pdfs/2701HG_user_guide.pdf

applies to your gizmo, then it would seem to
have a Web interface (by default at
192.168.0.1), with access to all kinds of
configuration options, including some related
to a "Public Network", and some to a "Bridge
Network", either of which might be what you
want. ("Management and Diagnostic Console" >
"Local Network" > "Status".)

Or, if your goal is simply to let the HP-UX
system get to the Internet for client access,
then I'd guess that you could assign it a
static IP address in the same subnet as the
DHCP addresses (but outside the DHCP range
offered by the gizmo), and use the gizmo's
gateway address as the default route gateway
for the HP-UX system.

Knowing what the working PCs are doing would
still be useful.

It's hard to be sure of anything without
knowing more about the way the gizmo is
configured.

[Dennis Handly]

>Their is a switch behind that, but no router.

You didn't get a wireless router with it?
If not, AT&T just gives you a small ADSL modem. Business gets the 2wire.

>Steven: Not a very complete description.

It is if you actually have one. :-) But there may be several models. Mine is an ADSL modem and wireless router.

>Michael: call ATT for there should be a way for you to access the modem.

You just use your windows browser to configure it. As Steven said, http://192.168.0.1

[mhess_1]

Guys,

First of all thanks for your patience and help given my incomplete descriptions of the hardware and situation. You are dealing with a couple of oceanographers who hack away at our network and probably do more harm than good. I'll try and answer some the recent questions. I get the feeling you are getting us close to a solution.

The gizmo is in fact a "2Wire" modem provided to us (a business) by AT&T. I don't know the exact model number due to the fact that I am 1000 miles away from the physical unit. But when my partner in hacking gets in, I'll get that info and forward it along.

No AT&T did not provide a wireless router with it.

Yes, we can get into the modem and do some configuration, but according to my partner and the less than knowledgeable folks at AT&T, it does not allow us to map an external IP address to an internal IP. (I apologize if I'm using improper lingo). As far as my partner can see, there are no options to perform that task. AT&T tells us that the 2Wire must first see a DHCP connection and then we can go in and reset the IP address to the static IP - in this case 75.60.238.36. Not sure I fully understand that, but that is what they are telling usâ ¦..BUT given your explanations and links to the 2Wire Users Guide, perhaps we can go back in and find the tools we are looking for. I will get my partner on this Forum weâ ll work from there. Weâ ll get that model number too.

RE Disclaimer: I would prefer not to use DHCP too on these machines, but again, that is what the AT&T â techsâ are telling us to do.

Address and routes:
The static IP we want on this machine is 75.60.238.36
Like Steve figured out, the block of IPs we are assigned is 75.60.238.32 through 75.60.238.47
The broadcast address is: 75.60.238.47
The gateway is: 75.60.238.46 (not 100% but fairly sure about that as well
The static IPs we want to use are 34, 35 & 36
Subnet mask=255.255.255.240
The result of netstat on the machine in question (in the exact format given ) is:
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 1890 lo0 4136
192.168.0.120 192.168.0.120 UH 0 13277 lan0 4136
192.168.0.0 192.168.0.120 U 2 0 lan0 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 192.168.0.1 UG 0 0 lan0 1500
-now that you have all this, Iâ m sure our next step will be to upgrade our system security ;-)

The web server on .33 is set for DHCP on the PCâ s side, but then we tell the 2Wire to make that internal IP the static â ¦33 IP. Iâ m mystified as to how the IPs are reassigned too, but Iâ ll get more info on that config for you soon.

Again â weâ ve both (myself and partner) have contacted AT&T support many times and all we get is â we canâ t help you because we only support PCsâ or you canâ t map the IP route using this modem, but they all seem to not really know what they are talking about. I could be wrong.

Hoping we can get the modem (2wire) to see this machine, I have tried to set DHCP=1 in /etc/rc.config.d/netconf, but every time that machine is rebooted, the setting goes back to 1. Most likely operator error again on my side.

Thanks again for all your time and patience. Sorry about the verbose response, but I wanted to be as clear as possible. Iâ ll get that 2Wire model number soon, get it posted, but also see if we can dig into the manual to figure this out.

Mark

[mhess_1]

Modem is a 2Wire Gateway as in 2wire.com
3800HGV-B Gateway

[Steven Schweda]

> > 3) We have several PCs [...]

> > What are their addresses and routes?

> Still wondering. Isn't there a Network
> Control Panel [or] an ipconfig program or
> something which might reveal these things?

Still wondering. [...]

> AT&T tells us that the 2Wire must first see
> a DHCP connection [...]

Knowing nothing, I wouldn't rule out that
possibility, but I wouldn't necessarily
believe it, either. They may be assuming
that every system will be using DHCP, and so
they want to re-jigger the DHCP server to
hand out the desired address to a particular
system (with a now-known MAC address). This
may be easier for them to explain than
configuring a static IP address.

> [...] but then we tell the 2Wire to make
> that internal IP the static â ¦33 IP.

How you tell the gizmo to do that would be
good to know. (Guesswork reduction here
would be a good thing.)

> The static IP we want on this machine is
> 75.60.238.36

Ok. So, you want this thing to have direct
access to the outside world at this address.
I'd guess that that means that you'd want to
assign it that address, and tell it to use
75.60.238.46 as its default route gateway.
All the "Public Network" and "Bridge Network"
stuff I see in the manual says "without
Network Address Translation (NAT)", so if
the outside-world address is 75.60.238.36,
then I'd guess that the actual address on the
system (interface) also must be 75.60.238.36.

An IP subnet of 75.60.238.32/28 should give
you a block of 16 addresses, not 8, so I'm
guessing that they over-reserved, giving you
some room for future expansion.

With an IP subnet of 75.60.238.32/29 (as
suggested by that "NetRange: 75.60.238.32 -
75.60.238.47"), you toss out the ends (.32
and .47) for broadcast, and one of the
remaining six must be used for the router
(and .46 is plausible), which leaves you with
(the usual) five usable addresses for a block
like this. So some of this makes some sense.

> Address and routes: [...]

Again, it would be reassuring to see how that
PC with the Web server is configured, and
more of the gizmo configuration associated
with that system. From what I've read, it's
not absolutely clear whether you should be
trying to use a real-world address like
75.60.238.36 and a default route gateway of
75.60.238.46, or some more internal-looking
(192.168.x.y) stuff. (But my money's on a
real-world address.) The "Public Network"
and/or "Bridge Network" stuff looks as if it
might be involved here.


> [...] we only support PCs [...]

I run VMS on my primary home system, so I
know _exactly_ how that feels.

"Do you have a PC or a Mac?"

"No."

[Long pause]

But I have a Cisco 678 DSL router which,
while now obsolete, has good documentation,
and was not crippled to make it more
"user-friendly". I also have a non-Telco
ISP, which helps considerably. I gather that
in other parts of the country, things are far
less satisfying.

> -now that you have all this, Iâ  m sure our
> next step will be to upgrade our system
> security ;-)

The villains will find you soon enough
without needing any info from here.

[Dennis Handly]

>The gizmo is in fact a "2Wire" modem provided to us (a business) by AT&T.

We got wireless support with ours.

>Modem is a 2Wire Gateway as in 2wire.com 3800HGV-B Gateway

It says wireless to me, unless -B means removed?
http://www.2wire.com/index.php?p=106
Wi-Fi 802.11g ... HyperG

This may be what you want?
http://www.dslreports.com/forum/r22441586-How-to-add-static-routes-to-2Wire-3800HGVB