Very Computer

I'm sorry for reposting this article - I realized that I should
have split the questions (IP address change and shutdown
account) into two separate posts.

I'm currently running a pair of web servers, one for internal use
and the other for external use.  The one for external use has
been limited to internal use while the site was being
developed.  Now that it is time to be deployed outside of the
firewall (no ftp, no telnet, no gopher, etc. a royal pain in the
backside to administer!) - I need to find a way to change the
TCP/IP address on the external server.  Both of the servers are
running RedHat 4.1 (Linux 2.0.27).

How do I change the IP address, netmask address, etc.?  If I use
ifconfig, the change is only valid while the system is running,
on reboot, I have to rerun ifconfig.  Internally it has one
address, on the outside, it has to have a different address
outside of the inside addesses ((don't ask me why, I put in what
I was told)

The address I'm trying to use is 164.220.something.53

I have a netmask of 255.255.255.240 (don't ask me why, I put in
what I was told) and now the system boots, but doesn't
communicate with anything except itself.

The two prime suspects are:

 - the ethernet port (unverified yet)
 - On my other, running, system the netmask is 255.255.255.0 -
   should the first (www) be changed to match the second?  If I run
   ifconfig to check the status, there are lot's of TX packets &
   errors, no RX.

Also, on boot-up, the network configuration utility says that
autoprobe shouldn't be used for single ethernet card systems.
How do I specify the card parameters?

I've looked in "Running Linux" & "Practical Internet Security" so far
with no success.  Does anyone have any advice?

--
Take care      |   This clown speaks for himself, his job doesn't
Wayne D.       |   pay for this, etc. (directly anyway)

On 27 Apr 1997 14:04:49 -0400,

I foist it off onto a separate script so it's easy to futz
around with, and just call the script drom rc.inet1.

Quote:>Also, on boot-up, the network configuration utility says that
>autoprobe shouldn't be used for single ethernet card systems.
>How do I specify the card parameters?

However, to be sure of it, add this line to your default stanza
in /etc/lilo.conf:

    append = "ether=X,0xYYY,eth0"

Where X is the irq, and YYY the port address in hex.

: On 27 Apr 1997 14:04:49 -0400,

: >How do I change the IP address, netmask address, etc.?  If I use
: >ifconfig, the change is only valid while the system is running,
: >on reboot, I have to rerun ifconfig.  Internally it has one
: >address, on the outside, it has to have a different address
: >outside of the inside addesses ((don't ask me why, I put in what
: >I was told)

: Look in /etc/rc.d/rc.inet1 - there's where your interfaces are
: set up at boot.  Just change what's relevant and restart.

: I foist it off onto a separate script so it's easy to futz
: around with, and just call the script drom rc.inet1.

Other distributions put the networking stuff in /etc/init.d
(network, netbase, somesuchthing...)  Do a 'grep' for the
first part of your ip address in both /etc and /etc/init.d (if
you have it) to make sure you find the location.  You need
to change the config info used by 'ifconfig' as well as the
entry in /etc/hosts.

Joe
--

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Joe Nardone             | "That's a double play if you're scoring |

| Arlington, VA           |                 - Keith Olbermann, ESPN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

 > On 27 Apr 1997 14:04:49 -0400,

 > >How do I change the IP address, netmask address, etc.?  If I
 > >use ifconfig, the change is only valid while the system is
 > >running, on reboot, I have to rerun ifconfig.  Internally
 > >it has one address, on the outside, it has to have a
 > >different address outside of the inside addesses ((don't
 > >ask me why, I put in what I was told)

 > Look in /etc/rc.d/rc.inet1 - there's where your interfaces
 > are set up at boot.  Just change what's relevant and
 > restart.

I don't see a file called /etc/rc.d/rc.i - I've grepped all of
the directories in /etc/rc.d tree for 206 (the first part of the
current address) and haven't had any luck.

 > I foist it off onto a separate script so it's easy to futz
 > around with, and just call the script drom rc.inet1.

I may end up reinstalling this to clean up the installation -
tossing stuff not needed -- X for example.

I checked with the guy that is supposed to know all about this
stuff and we went over the addresses.  The IP address is
supposed to be 164.220.53.84, netmask 255.255.255.240 (we get a
small piece of this class B space, some for the firewall, etc.)
and a broadcast address of 164.220.53.95.  The link status
lights are on the top of the card and are blinking, the router
says the card is communicating, yet I can't ping anything except
with 127.0.0.1 - everything else gets a network communication
failure.  We re-verified the broadcast address given the IP
address and the netmask.

My next step is to take the system over and plug it into a
"normal" port and check for operation.

 > >Also, on boot-up, the network configuration utility says
 > >that autoprobe shouldn't be used for single ethernet card
 > >systems.  How do I specify the card parameters?

 > If it works okay, you can ignore it.

 > However, to be sure of it, add this line to your default
 > stanza in /etc/lilo.conf:

 >     append = "ether=X,0xYYY,eth0"

 > Where X is the irq, and YYY the port address in hex.

I'll try that.

--
Take care      |   This clown speaks for himself, his job doesn't
Wayne D.       |   pay for this, etc. (directly anyway)

:


:  > On 27 Apr 1997 14:04:49 -0400,
:  > Look in /etc/rc.d/rc.inet1 - there's where your interfaces
:  > are set up at boot.  Just change what's relevant and
:  > restart.
:
: I don't see a file called /etc/rc.d/rc.i - I've grepped all of
: the directories in /etc/rc.d tree for 206 (the first part of the
: current address) and haven't had any luck.
:
I believe you are using RedHat??? In that case you shouldn't be looking in
/etc/rc.d for configuration info.  /etc/rc.d is where the SysVinit scripts
are kept, and the scripts import config info from config files in
/etc/sysconfig as script variables.  I suggest you print out all the files
in /etc/rc.d/init.d and go through them with a red pen and a highlighter,
its a very good way to come to terms with your system initialisation and
configuration.  Also don't forget to checkout the RedHat User's Guide,
especially their section on SysVinit.
http://www.redhat.com/support/docs/rhl/RHL-4.1-Users-Guide-HTML/manua...

(the top of the tree is at http://www.redhat.com/support/docs/rhl/ )

Basically you just edit the config files in /etc/sysconfig/network, and
/etc/sysconfig/network-scripts/ .

:  > I foist it off onto a separate script so it's easy to futz
:  > around with, and just call the script drom rc.inet1.
:
: I may end up reinstalling this to clean up the installation -
: tossing stuff not needed -- X for example.
:
Probably a good idea.  All you will really want to keep, are the base
system utilities, base networking, and rpm (easiest way to apply redhat
security patches).

: I checked with the guy that is supposed to know all about this
: stuff and we went over the addresses.  The IP address is
: supposed to be 164.220.53.84, netmask 255.255.255.240 (we get a
: small piece of this class B space, some for the firewall, etc.)
: and a broadcast address of 164.220.53.95.  The link status
: lights are on the top of the card and are blinking, the router
: says the card is communicating, yet I can't ping anything except
: with 127.0.0.1 - everything else gets a network communication
: failure.  We re-verified the broadcast address given the IP
: address and the netmask.
:
Always easier to think in hex with this stuff (then convert back to dec'
when you need to use it).
IP ADDR: A4.DC.35.54 = 164.220.53.84
NETMASK: FF.FF.FF.F0 = 255.255.255.240
NET ADR: A4.DC.35.50 = 164.220.53.80
HOST AD: 00.00.00.04 = 0.0.0.4
BRD CST: A4.DC.35.5F = 164.220.53.95

See easy :).

The ping problem is hard to diagnose without more info.  It would be of
help if you provided the output of 'ifconfig eth*', and 'route'.  It could
be that the interface isn't configured properly, or it could be that the
routing table is #$^%ed.  Can a system on the same subnet (probably the
firewall) ping it?

: My next step is to take the system over and plug it into a
: "normal" port and check for operation.
:
Try pinging it from another system.

:  > >Also, on boot-up, the network configuration utility says
:  > >that autoprobe shouldn't be used for single ethernet card
:  > >systems.  How do I specify the card parameters?
:
:  > If it works okay, you can ignore it.
:
:  > However, to be sure of it, add this line to your default
:  > stanza in /etc/lilo.conf:
:
:  >     append = "ether=X,0xYYY,eth0"
:
:  > Where X is the irq, and YYY the port address in hex.
:
: I'll try that.
:
Then again if it ain't broke don't fix it.  You might also consider
compiling the ethernet support directly into the kernel.

Andrae Muys

--
===========================================================================

                            |
Andrae Muys                 | Linux... What do you want to DO today?
Centre, Magnetic Resonance. |
University of Queensland.   | Diplomacy is the art of saying "Nice Doggie!"
Australia                   |    till you can find a rock. - Wynn Catlin

 > :


 > :  > On 27 Apr 1997 14:04:49 -0400,
 > :  > Look in /etc/rc.d/rc.inet1 - there's where your interfaces
 > :  > are set up at boot.  Just change what's relevant and
 > :  > restart.
 > :
 > : I don't see a file called /etc/rc.d/rc.i - I've grepped all of
 > : the directories in /etc/rc.d tree for 206 (the first part of the
 > : current address) and haven't had any luck.

 > I believe you are using RedHat??? In that case you shouldn't
 > be looking in /etc/rc.d for configuration info.  /etc/rc.d
 > is where the SysVinit scripts are kept, and the scripts
 > import config info from config files in /etc/sysconfig as
 > script variables.  I suggest you print out all the files in
 > /etc/rc.d/init.d and go through them with a red pen and a
 > highlighter, its a very good way to come to terms with your
 > system initialisation and configuration.  Also don't forget
 > to checkout the RedHat User's Guide, especially their
 > section on SysVinit.
 > http://www.redhat.com/support/docs/rhl/RHL-4.1-Users-Guide-HTML/manua...
 <snip>

 > : I may end up reinstalling this to clean up the installation
 > : - tossing stuff not needed -- X for example.

 > Probably a good idea.  All you will really want to keep, are
 > the base system utilities, base networking, and rpm
 > (easiest way to apply redhat security patches).

That's what I ended up doing (reinstalling) - I went from 350
odd megabytes to a little over 100.  Lots of space for the guy
who dreams the web page up to put stuff (look at
http://www.ih.navy.mil)

 > Always easier to think in hex with this stuff (then convert
 > back to dec' when you need to use it).
 > IP ADDR: A4.DC.35.54 = 164.220.53.84
 > NETMASK: FF.FF.FF.F0 = 255.255.255.240
 > NET ADR: A4.DC.35.50 = 164.220.53.80
 > HOST AD: 00.00.00.04 = 0.0.0.4
 > BRD CST: A4.DC.35.5F = 164.220.53.95

 > See easy :).

I looked up the procedure in the LDP and arrived at the same
answers and then the guy responsibel for the network and I
rechecked each others results.  Once I decided to just do a
reinstall, I stopped looking for the way to change the IP
address.

--
Take care      |   This clown speaks for himself, his job doesn't
Wayne D.       |   pay for this, etc. (directly anyway)