eth0 and eth1 interfaces using eth0 NIC

eth0 and eth1 interfaces using eth0 NIC

Post by rnb.. » Mon, 07 Aug 2000 04:00:00



Hi

Im running RH6.2 with two nics (nic0 is a digital de500 and nic1 is a
3c905-tx)

Both interfaces come up with seperate ip addresses but eth1 is using the
nic0 card, e.g. on eth1 my dsl line will dialup pppoe but nic1 isn't
connected to the modem and nic0 is. Also, from win98 I can ping eth1
when nic1 isn't connected to the network.

below are conf.modules and lilo.conf.

conf.modules:
****
alias eth0 de4x5
alias eth1 3c59x
options de4x5 io=0xfc00 irq=11
options 3c59x io=0xfcc0 irq=10
****

lilo.conf
****
boot=/dev/hda
map=/boot/map
prompt
timeout=50
linear
default=linux
append="ether=10,fcc0-fcff,eth1 ether=11,fc00-fc7f,eth0"
****

Without the append= in lilo.conf I couldn't get both interfaces to come
up but Im wondering if I have a syntax error or something.  I've been
through /proc/interrupts and /proc/ioports but dont see any conflicts
and I've used the 3com config disk to set up the 3com nic.

ifconfig looks like this with dsl dialedup.  Ipaddresses x'd to protect
the innocent.  Note that eth1 has no ip address since dsl ppp0 is using
it.

eth0      Link encap:Ethernet  HWaddr 00:00:F8:06:01:0D
          inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1214 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1255 errors:2 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0xfc00

eth1      Link encap:Ethernet  HWaddr 00:60:08:42:12:B0
          UP BROADCAST RUNNING NOARP 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:0xfcc0

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:XXX.XXX.XXX.XXX  P-t-P:XXX.XXX.XXX.XXX
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:436 errors:0 dropped:0 overruns:0 frame:0
          TX packets:444 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10

Any hints/tips/detailed instructions (cause Im not too bright) would be
appreciated. - Rusty

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

eth0 and eth1 interfaces using eth0 NIC

Post by Donald Beck » Wed, 09 Aug 2000 04:00:00



>Im running RH6.2 with two nics (nic0 is a digital de500 and nic1 is a
>3c905-tx)
>conf.modules:
>****
>alias eth0 de4x5
>alias eth1 3c59x
>options de4x5 io=0xfc00 irq=11
>options 3c59x io=0xfcc0 irq=10

This won't work.  The "io=" and "irq=" options are only for ISA drivers.
Passing unknown options will prevent a driver module from loading.

Quote:>lilo.conf
..
>append="ether=10,fcc0-fcff,eth1 ether=11,fc00-fc7f,eth0"

This is also wrong, although harmless.  The driver will just ignore these
settings.  The syntax would be
  append="ether=10,0xfcc0,eth1 ether=11,0xfc00,eth0"

Quote:>Without the append= in lilo.conf I couldn't get both interfaces to come
>up but Im wondering if I have a syntax error or something.  I've been

You must have the drivers built into your kernel.
The syntax error was harmless -- the IRQ and I/O base settings are ignored.

Quote:>through /proc/interrupts and /proc/ioports but dont see any conflicts
>and I've used the 3com config disk to set up the 3com nic.

Ackk!! You shouldn't have needed to do that.  In some cases newer 3Com setup
programs will leave the EEPROM settings in a state that older Linux drivers
will not work with.  (We can't predict what format 3Com will use in the
future!)  The default setting should always work.

Quote:>ifconfig looks like this with dsl dialedup.  Ipaddresses x'd to protect
>the innocent.  Note that eth1 has no ip address since dsl ppp0 is using
>it.
..
>eth1      Link encap:Ethernet  HWaddr 00:60:08:42:12:B0
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
...
>ppp0      Link encap:Point-to-Point Protocol
>          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>          RX packets:436 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:444 errors:0 dropped:0 overruns:0 carrier:0

This looks like a PPPoE configuration problem, not a driver problem.

--

Scyld Computing Corporation             http://www.scyld.com
410 Severn Ave. Suite 210               Beowulf Clusters / Linux Installations
Annapolis MD 21403

 
 
 

1. eth0 and eth1 "Delaying eth0 Initialization" and "Delaying eth1 Initialization" errors

Hello, I am a linux newbie, and have run into a problem.

I am using RH 7.1 with kernel 2.4.2.  I built a new kernel (to be used for
firewall purposes).  The kernel built fine and it booted successfully except
that with both eth0 and eth1, the errors "Delaying eth0 Initialization" and
"Delaying eth0 Initialization" come up.  I did not have this problem with
the original kernel.

Both NICs are Linksys LNE100TXs using the 169 chip.  The ipcfg-eth0 and 1
are set to activate on boot.

Any ideas?

Thank you,

Alan

2. Can "make" work in ELF-default environment to produce a.out binaries?

3. eth0 default interface - eth1 can't be used

4. grep: subdirectories

5. eth1 problems - eth0:LAN:tulip eth1:DSL:3c509 w/ipmasq (static IP)

6. Intelligent Serial Boards -- Reccomendations/Horror Stories

7. nics eth0 and eth1 got swapped in ifconfig

8. HELP: Soundscape PnP configuration

9. Help with assigning eth0/eth1 to proper NICs

10. Interface confusion eth0 wired eth1 wireless

11. Fixed interfaces (eth0 and eth1)

12. typical 2 NIC LAN config -- help connecting eth0 to eth1

13. socket programming using either eth0 or eth1