[EMAIL PROTECTED] writes:
> I am trying to set up a firewall, however I have hit a snag that I
> cannot seem to get around.  I am trying to run two ethernet cards,
> both of them are Netgear FA310TX cards, and both are supposed to run
> on the tulip driver.  When I install the OS, and I set up eth0, it
> works fine, right from the get go.  However, when I try to get eth1
> to work, it will not do so.  First, I gave both different static ips
> on the same network, and I unplugged one and pinged them.  eth0
> would respons to both ips, but eth1 would respond to neither.  Next
> I put them both on seperate networks.  eth0 worked fine, no matter
> if it was the cable modem or a lan.  eth1 will not take a ping.

Dumb question, I know, but just to cover the basics:

Does the NIC you are using for eth1 work at all if the other NIC
(eth0) is not in the box/conntected?

> the two cards are on seperate ips, eth0 has a DHCP server on it's
> side.  I type ifconfig and I get this (I took out lo)

> eth0      Link encap:Ethernet  HWaddr 00:A0:CC:53:66:08
>           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING  MTU:1500  Metric:1
>           RX packets:680 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:391 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:11 Base address:0xe800
> 
> eth1      Link encap:Ethernet  HWaddr 00:A0:CC:61:E9:65
>           inet addr:192.168.1.20  Bcast:192.168.1.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:10 Base address:0xec00

> No major problem here except that eth1 appears to be getting no
> traffic.

> I type in "modprobe eth0", and get nothing, but when I type in
> "modprobe eth1" I get "modprobe: Can't locate module eth1"

> when I type in "dmesg | tail" I get a big list of stuff, I believe
> the last three lines are the most pertinant, they are as follows:

> eth0: Lite-On 82c168 PNIC rev 32 at 0xe800, 00:A0:CC:53:66:08, IRQ 11.
> eth0:  MII transceiver #1 config 3000 status 7829 advertising 01e1.
> eth1: Lite-On 82c168 PNIC rev 32 at 0xec00, 00:A0:CC:61:E9:65, IRQ 10.

> Someone told me that it was a routing issue, but I have no idea if
> that's true or not.  I really don't know what the problem here is,
> least of all how to fix it.  Obviously I cannot get my NAT server to
> work if it can only use one ethernet card.  I really hope someone
> can help me with this because I was really hopeing to replace my
> Win2k server.  If you need any more information, please tell me.

The routing issue may be in relation to the system having to choose
the best interface to send out packets. Perhaps it's using a
"first-come, first-served" method in that it's sending packets onto
the same network; that is, the system logic may be, "oh, this packet
goes to 192.168.1.0 network. I need to reply, so which interface goes
to this network. Here's a list that begins with eth0; what network is
it on? 192.168.1.0. Ok! What's it's metric? 1. That's the lowest it
can go, so out the packet goes on eth0."

Have you tried tcpdump while watching eth0 and eth1 respond to pings?
Is it possible that eth1 is receiving pings but eth0 is doing the
reply?

As for "modprobe eth1". From the man-page:

       modprobe  [  -adnqv  ] [ -C config ] module [ symbol=value ... ]
       modprobe [ -adnqv ] [ -C config ] [ -t type ] pattern
       modprobe -l [ -C config ] [ -t type ] pattern
       modprobe -c [ -C config ]
       modprobe -r [ -dnv ] [ -C config ] [ module ...]
       modprobe -V

It's expecting a module name and not an interface name, *although* one
can set up aliases in /etc/modutils/aliases. Even if eth1 is set up as
an alias to "82c168" (or whatever the correct module name is), it
wouldn't really matter in regards to the interfaces themselves because
it is the same module (it's like typing in "modprobe 82c168" for
"modprobe eth0" or "modprobe eth1").

Since you're able to "ifconfig eth1 192.168.1.20 up", the modutil
problem doesn't seem related - the system recognizes eth1 as a valid
interface and isn't throwing a "DEVICE NOT FOUND" (or something to
that effect) error.

Elizabeth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to