Red Hat ES with isolated network and hub.

I have a problem that I know is at the tip of my tounge and cant spit it
out.

I needed to set up a Red Hat server 192.168.2.1/255.255.255.0 on an isolated
network. 192.168.2.0

I will have 10 pc's connected to it thru a hub.
Back to networking 101...

I have the crossover switch on for the port on the server to the hub. Light
is on.

I then hooked up the test pc and gave it an address of
192.168.2.11/255.255.255.0

I am assuming that I dont need a default gateway, because it is on the same
subnet. And no traffic should be going out anyway.


The files that I changed were...
[root@backgate sysconfig]$ more network
NETWORKING=yes
HOSTNAME=backgate


[root@backgate network-scripts]# more ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.2.255
IPADDR=192.168.2.1
NETMASK=255.255.255.0
NETWORK=192.168.2.0
ONBOOT=yes

The /etc/hosts file remained the same since the only entry was ...
[root@lnxgate etc]# more hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost


Did a restarted the server and when I try to ping 192.168.2.11
I get
Destination Host Unreachable


What am I missing?

In comp.os.linux.networking LHradowy <(E-Mail Removed)> wrote:
>
> Did a restarted the server and when I try to ping 192.168.2.11
> I get
> Destination Host Unreachable

On 192.168.2.1 run "ping -b -n 192.168.2.255" command. It will
send ICMP echo requests to the broadcast address, so you should
see smth like this:

# ping -nb 192.168.2.255
WARNING: pinging broadcast address
PING 192.168.2.255 (192.168.2.255) from 192.168.2.1 : 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=290 usec
64 bytes from 192.168.2.11: icmp_seq=0 ttl=64 time=618 usec (DUP!)
[...]


On another host, 192.168.2.11, run "tcpdump -n icmp".

# tcpdump -n icmp
tcpdump: listening on eth0
14:44:00.057607 192.168.2.1 > 192.168.2.255: icmp: echo request (DF)
14:44:00.057627 192.168.2.11 > 192.168.2.1: icmp: echo reply
[...]

The '-n' option will prevent both ping and tcpdump from resolving
IP addresses into domain names. If you won't see similar picture,
check cables and hub ports.

--
andrei

["Followup-To:" header set to comp.os.linux.misc.]
On Wed, 16 Jun 2004 16:04:15 -0500, LHradowy
<(E-Mail Removed)> wrote:
> I have a problem that I know is at the tip of my tounge and cant spit it
> out.
>
> I needed to set up a Red Hat server 192.168.2.1/255.255.255.0 on an isolated
> network. 192.168.2.0
>
> I will have 10 pc's connected to it thru a hub.
> Back to networking 101...
>
> I have the crossover switch on for the port on the server to the hub. Light
> is on.
>
Crossover switch? I think that is for connecting two hubs together.
A hub doesn't care which PC is "the server".


--
Simulations are like miniskirts, they show a lot and hide the essentials.
-- Hubert Kirrman