Problems setting Static IP

action_owl · 2010-06-11 19:53:35

I am trying to install an Arch box with a couple of existing SLES9 Servers. Getting the system configured and Apache working correctly are the easy parts, the confusing part is the networking.

The SLES boxes have an internal address (192.168.0.x) but they also have an external address that can be reached from the internet, I have my local IP address set-up and I can ping the SLES boxes so the internal IP addresses are set up correctly and I have an external IP address to use, but I don't know how/where to put this external IP address so that I can use it with the internal one.

I can look at the SLES boxes for reference but I'm not familiar with suse and I really don't know what I'm looking for, can anyone give me any ideas?

Thanks

Last edited by action_owl (2010-06-11 20:28:42)

Sin.citadel · 2010-06-13 17:36:35

i m guessing that the SLES boxes are configured with two interfaces, one connects to the external network, and one to an internal network. you will need to plug in your system with those two separate networks and assign the ip addresses to them.

pyther · 2010-06-13 21:56:24

It is hard to determine what is going on. Is this a home network or a business network? If it is a home network I would likely agree with Sin.citadel in that there are two interfaces with different ip addresses.

However, if this is a business environment is is likely that nat is in place. NAT maps a public address to a private address at the router level.

action_owl · 2010-06-17 12:53:23

@pyther, It is a business network, and I believe NAT is in place, if it is how would this effect my settings on the arch box or should it be transparent to me?

@Sin.citadel you are correct there are 2 Ethernet interfaces (eth0 and eth1) but only one is "up" the other one seems to be unused.
To make things more difficult I cannot physically get to the machine to see if indeed 2 Ethernet cables are going to the box. I can only SSH into the SLES boxes and I'm using some HP Java interface to set up Arch for the time being.

Can the settings I describe be configured with only one interface? or should I focus on using 2 interfaces (the arch box has 2 as well)?

Thank you for your help

Last edited by action_owl (2010-06-17 13:01:50)

pyther · 2010-06-17 12:55:59

It sounds like NAT is in place. This means the machine has a private lan address on the network, but when it hits the router it gets changed to a public address that is mapped to the private one.

If this is indeed the case you'll have to talk to the Network guys at said business to help you out.

action_owl · 2010-06-17 13:08:25

Thank you very much pyther,
I'm a developer and FOSS/Linux enthusiast and I'm trying my hardest to prevent the company from migrating to .net development, poor server configuration, sloppy programming, and lack of documentation has made the DBAs hate Linux and I have no interest developing in a proprietary environment. However I lack in-depth routing/networking knowledge and the networking guys lack in-depth linux knowledge so it makes things difficult.

Thanks again your assistance

pyther · 2010-06-17 13:12:56

This shouldn't be a linux vs windows type of deal. The network guys should be able to do a static nat entry regardless of the OS you are using.

NAT Example:
209.60.60.51 - 192.168.1.5 - 192.168.1.50 Shared Address that everyone shares to get out on the network (sorta like a home dsl/cable network)
209.60.60.53 - 192.168.1.55 Server 1 (Static Map)
209.60.60.54 - 192.168.1.56 Server 2 (Static Map)

The above all gets done on the router. The only thing needed on the host would be the private/internal (192.168.1.x) address to be set.

Arch Linux

#1 2010-06-11 19:53:35

Problems setting Static IP

#2 2010-06-13 17:36:35

Re: Problems setting Static IP

#3 2010-06-13 21:56:24

Re: Problems setting Static IP

#4 2010-06-17 12:53:23

Re: Problems setting Static IP

#5 2010-06-17 12:55:59

Re: Problems setting Static IP

#6 2010-06-17 13:08:25

Re: Problems setting Static IP

#7 2010-06-17 13:12:56

Re: Problems setting Static IP

Board footer