Mailing List Archive

Support open source code!


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Routing problems



I think this misses the point that he was trying to route between the two PCs using the redhat box.  I am making an assumption here that the two boxes are not plugged into the same hub/switch.  And even if they are, that he wants them to talk through the "router".  Besides, isn't 255.255.0.0 a little bit excessive?  

Michael

The pun was unintentional.

-----Original Message-----
From: Scott Stone [mailto:SStone@example.com]
Sent: 13"N6OEZ28"ú 4:47
To: 'tlug@example.com'
Subject: RE: Routing problems



the problem is the netmask.

192.1.1.230 and 192.1.2.230, each with a 255.255.255.0 netmask, cannot talk
to each other.
Change the second pc to 192.1.1.231, or change the netmask to 255.255.0.0 on
both boxes.

-----------------------------------------------------
Scott M. Stone <sstone@example.com>
Senior Technical Consultant - UNIX and Networking
Taos, the Sysadmin Company - Santa Clara, CA


-----Original Message-----
From: Doughty, Michael [mailto:Doughty_Michael@example.com]
Sent: Wednesday, June 27, 2001 1:10 AM
To: 'tlug@example.com'
Subject: RE: Routing problems


I'm thinking the obvious question here is:  Did you set your redhat box as
the gateway for these PCs?  You through out a lot of information on your
server setup, but then complained about client connectivity issues.  I would
first look at the clients to verify that they are setup properly.

Michael

-----Original Message-----
From: Brett Robson [mailto:brettr@example.com]
Sent: 13"N6OEZ27"ú 16:53
To: tlug@example.com
Subject: Routing problems



I'm at a loss, here.

My RedHat 7.1 box has two eth cards, 192.1.2.248 and 192.1.1.231 (not their
real names),
each with netmasks 255.255.255.0 and has Apache running on it.

On both eth cards are PCs.
  PC1,  192.1.1.230   has Apache running
  PC2,  192.1.2.230

The RedHat box and PC1 can happily browse each others webservers and ping
each other.
The RedHat box and PC2 can ping each other.

But the PCs can not see each other. Ping-ing each other gives "Destination
host unreachable"

This is the config stuff
Note that in the routing table I have added the host 192.1.1.230 to see if
that would help, it didn't.

I must be missing something, there must be a magic switch somewhere I
haven't turned on?

mouiya
Brett

------------------------------------------------------------------------
netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.1.1.230     0.0.0.0         255.255.255.255 UH       40 0          0
eth1
192.1.2.0       0.0.0.0         255.255.255.0   U        40 0          0
eth0
192.1.1.0       0.0.0.0         255.255.255.0   U        40 0          0
eth1
127.0.0.0       0.0.0.0         255.0.0.0       U        40 0          0 lo

ifconfig
eth0      Link encap:Ethernet  HWaddr 00:A0:CC:5E:C9:5C
          inet addr:192.1.2.248  Bcast:192.1.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:9808 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10392 errors:0 dropped:0 overruns:0 carrier:0
          collisions:71 txqueuelen:100
          Interrupt:10 Base address:0xc000
eth1      Link encap:Ethernet  HWaddr 00:A0:CC:5D:90:85
          inet addr:192.1.1.231  Bcast:192.1.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1328 errors:0 dropped:0 overruns:0 frame:0
          TX packets:746 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0xc400
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10300 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10300 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ipchains -L
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):

cat /proc/sys/net/ipv4/ip_forward
1

------------------------------------------------------------------------


-----------------------------------------------------------------------
Next Technical Meeting:  Sat, July 14 13:30- 
Next Nomikai Meeting:    Fri, Aug  10 19:30-  Tengu Tokyo Eki-Mae
-----------------------------------------------------------------------
more info: http://www.tlug.gr.jp           Sponsor: Global Online Japan

-----------------------------------------------------------------------
Next Technical Meeting:  Sat, July 14 13:30- 
Next Nomikai Meeting:    Fri, Aug  10 19:30-  Tengu Tokyo Eki-Mae
-----------------------------------------------------------------------
more info: http://www.tlug.gr.jp           Sponsor: Global Online Japan

-----------------------------------------------------------------------
Next Technical Meeting:  Sat, July 14 13:30- 
Next Nomikai Meeting:    Fri, Aug  10 19:30-  Tengu Tokyo Eki-Mae
-----------------------------------------------------------------------
more info: http://www.tlug.gr.jp           Sponsor: Global Online Japan


Home | Main Index | Thread Index

Home Page Mailing List Linux and Japan TLUG Members Links