You need to make one of them something else, like 192.168.1/24 or perhaps subnet down the 192.168.0.xxx to make distinct networks.
- Bruce
On Fri, 2002-05-03 at 13:21, Harry Putnam wrote:
[NOTE Windbag ALERT.. what follows seemed necessary to
give enough detail for a helpfull reply..sorry]
Setup: RH 7.1 (two nics
RealTek RTl8029
(NETGEAR) Lite-On 82c168 PNIC)
Home network DSL connected.
Hardware router/gateway at DSL MODEM
Background info:
I've been running with only one of the above nics activated for a
very long time. The Realtek My setup looked like
INTERNET
|
dsl modem
|
ROUTER (gateway) NETGEAR FR314
|
---------------------------------
| | | | |
m1 m2 m3 m4 m5
I'm working machine 5 in the picture.
I wanted to do some experimenting with iptables and ipmasquerade.
Something I had going before installing the hardware router about 1
yr ago. So don't remember all the config problems etc.
What I've run into is that after configuring the second nic and being
able to ping it from the machine it is located on. I'm not able to
ping the machines I hooked up to it. Machines 1-4 in the picture
below. Thru a simple hub
INTERNET
|
dsl modem (Static IP)
|
ROUTER (gateway) NETGEAR FR314 192.168.0.1
|--eth0 192.168.0.5
--M5--
|--eth1 192.168.0.10
-----Simple hub (Netgear DS108)--------
| | | |
m1 m2 m3 m4
On a reboot, the messages say eth0 and eth1 came up ok.
Dmesg shows them on the same IRQ (9) (I remember that being the
case before too, so don't think that is a problem)
Tail of dmesg:
[...]
ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker
http://www.scyld.com/network/ne2k-pci.html
PCI: Assigned IRQ 9 for device 00:08.0
eth0: RealTek RTL-8029 found at 0xd800, IRQ 9, 00:00:E8:90:99:20.
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
PCI: Found IRQ 9 for device 00:09.0
tulip0: MII transceiver #1 config 3000 status 7809 advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 32 at 0xc8838000, 00:A0:CC:59:6B:FC,
IRQ 9.
Ifconfig shows them both up:
[...]
eth0 Link encap:Ethernet HWaddr 00:00:E8:90:99:20
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:858 errors:0 dropped:0 overruns:0 frame:0
TX packets:989 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xd800
eth1 Link encap:Ethernet HWaddr 00:A0:CC:59:6B:FC
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0x8000
[...]
Netstat -nr shows this picture:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Win irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
192.168.0.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
0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0
Can't remember if I have to do something tricky about the gateway.
Trying to ping any of the connected local machines fails:
reader $ ping 192.168.0.4
PING 192.168.0.4 (192.168.0.4) from 192.168.0.5 : 56(84) bytes of data.
From 192.168.0.5: Destination Host Unreachable
[...]
Looks like I may be pinging thru the wrong nic. 192.168.0.5 is the
internet side (eth0). But shouldn't 192.168.0.10 (local eth1) carry
the ball in that case?
If I shut down 192.168.0.5 then the 192.168.0.10 nic tries:
root # ping 192.168.0.4
PING 192.168.0.4 (192.168.0.4) from 192.168.0.10 : 56(84) bytes of
data.
From 192.168.0.10: Destination Host Unreachable
[...]
what fundamental thing am I forgetting here?
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
