On Mon, 2 Dec 2002, Smitty wrote:
>
> Here is a error message I get when I run ifconfig on my workstation:
> Error while executing:
> command 'ip route replace to 192.168.100.0/24 via 192.168.100.1 dev eth0
> returned:
> RTNETWORK answers: Invalid argument
> Configuration line: 192.168.100.0 192.168.100.1 255.255.240.0 eth0
> recieve packet failed network is down.
>
> The eth1 card on the firewall box has no lights on, while the eth0
> card does. (eth0 is the internet interface while eth1 is the lan
> interface.) I did a lsmod and found that the drivers are loaded for both
> cards.
kudos on the lsmod. You must have looked at your etc/modules.conf and
noted the aliases?
> Eth0 is
> a linksys card using a tulip driver and eth1 is a netgear card using a
> natsemi driver. Basically, eth1 is dead to the world and I don't know why.
> Any insight here?
I've never used a natsemi driver, but if they load and find their cards
you're probably using the right drivers. Maybe search the Ethernet HOWTO
for a string resembling your NIC models if you wanted to double-check.
No lights on the card is a problem. It usually indicates a layer-1
cabling issue. (Unless, as Levi suggested, the lights are burnt out;
nifty curve ball that would be.) Make sure you're not using a cross-over
cable. Make sure you don't have it plugged into an up-link/cross-over
port on the hub. Try taking the cable out of your workstation NIC where,
presumably, LEDs are flashing merrily, and sticking it into your dark
card just to see if you can light it up.
I'm going to try to do a little ASCII network diagram to make sure
we're all playing from the same sheet of music here. (You'll need a
fixed-width font to see this right.) This is just to make sure I
understand what you have, or are trying to get.
--------------
| Internet |
--------------
|
|
--------------
| your ISP |
--------------
|
|
______________
| your cable | Should light up LEDs indicating
| modem or | connectivity/traffic to both
| DSL router | sides
--------------
|
|<--- Might need to be cross-over cable.
| Try using the cable that came with
| the equipment from your provider.
| Alternatively, put a hub and 2 normal
| cables between these devices.
| If you don't light up LEDs at both ends
| you probably have the wrong cable.
-------- |
| --------------- eth0
| | The WAN NIC | IP=DHCP from your ISP
Y | on your | Tulip driver,
O | firewall | Linksys card.
U ---------------
R |
| |
F |
I ---------------
R | Your router | echo '1' > /proc/sys/net/ipv4/ip_forward
E | core, | The iptables configuration script.
W | iptables, | Other firewall config issues.
A | NAT magic, | (This is the hard part.)
L | and more |
L ---------------
| |
I |
S |
| --------------- eth1
H | The LAN NIC | IP=192.168.100.1
E | on your | MASK=255.255.255.0
R | firewall | natsemi driver,
E --------------- Netgear card.
| |
------- |
|<--- Normal, not cross-over, cable unless you
| plug into an uplink port on the hub.
| If you don't light up LEDs at both ends
| of the cable you probably have a
| cabling issue.
|
----------------
| Ethernet hub |
| or switch |
----------------
| |
| |<--- Repeat immediately above cable note.
| | Turn on the LEDs.
| |
| |---------------------------------
| |
| |
----------------------- ----------------------
| workstation | | workstation 2 |
| eth0 | | eth0 |
| IP=192.168.100.2 | | IP=192.168.100.3 |
| MASK=255.255.255.0 | | MASK=255.255.255.0 |
| GATE=192.168.100.1 | | GATE=192.168.100.1 |
| Don't forget DNS | | |
----------------------- ----------------------
|
|
|
_____
/ \
/ o o \
| ' | <--- Smitty surfing the web.
\ \___/ /
\_____/
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:23:35 EDT