Very Computer

I created a local network between two machines that were connected via
a 200ft cable.

I used the following on the machines to set it up:

Machine 1:

/sbin/ifconfig eth0 192.168.1.1 netmask 255.255.255.0

Machine 2:

/sbin/ifconfig eth0 192.168.1.2 netmask 255.255.255.0

When I start a ping from machien 1 to machine 2 it works for a while
and then all of a sudden the host is no longer reachable

When I go over to machine 2 the ip address has been lost

Is this normal?  Should I have a background process which checks ifdown
and if the network is down it attempts to reestablish?

I am trying to get some useful network latency statistics out of this
whole exercise.

Thanks,

Ryan Burgess.

do a
 ifconfig -a
 both before and after that problem occured.

poly-p man

First thing to check is the cable.  Make sure it's properly wired, with
correct pairing maintained.  Since you're going directly from one computer
to another, you'll probably need a cross over cable.  Look up EIA/TIA 568.
Use 568A on one end and 568B on the other, to make a crossover.  With a
properly constructed cable, you should be good for up to 100 M (328 feet).

Distribution? Release?  What else is running on the systems?

Quote:>When I start a ping from machien 1 to machine 2 it works for a while
>and then all of a sudden the host is no longer reachable

>When I go over to machine 2 the ip address has been lost

Why?

Quote:>Is this normal?

No, but then you are not providing enough information.  For example,
what do the "network" configurations scripts/files contain? Have you
got a DHCP client or some such crap?

Quote:>Should I have a background process which checks ifdown
>and if the network is down it attempts to reestablish?

Not enough information. Assuming you are not running to wonderful
helper programs, when you bring the network up manually, it should
stay up.

        Old guy

Right now I am configuring with netconfig so that the ip addresses are
static local
192.168.0.1 and 192.168.0.2
with a netmask of 255.255.255.0

This is running on Redhat 8

There is nothing else running

Ok, I think I found the issue

dhclient was actually still running and that appears to have been
*ing things up.