Find the answer to your Linux question:
Results 1 to 3 of 3
Hello and a very good day to everyone. i'd like to hear any suggestions regarding my problem in setting up this two network card to work on my kanotix 2006-easter ...
  1. #1
    Just Joined!
    Join Date
    Jun 2006
    Posts
    1

    Problematic scenarios in installing two ethernet cards on kanotix

    Hello and a very good day to everyone. i'd like to hear any suggestions regarding my problem in setting up this two network card to work on my kanotix 2006-easter RC4

    - The problem here is - i can't have two ethernet card installed in my kanotix. the first card (eth0) is built-in card on motherboard, and the second problematic card (eth1) is plugged to the PCI slot.

    - To save everybody's time, I've already confirmed that my kernel supports both ethernet card, and both are identical card (or at least identical chipsets), Realtek RTL8139(A/B/C/D)/810X)- verified by both BIOS and Windows XP.

    - The problem is, if I have only one eth0 installed (and eth1 is not plugged to the machine)... i will have access to my network without any problem (and connect to the jaring SOMA to access to the internet)

    - But if I have the eth1 plugged to the machine.. although eth0 is up and running...but i cannot access to the network (and the internet) via eth0 ! i have to remove the eth1 from PCI slot and restart the machine in order to get access. And worse, I can't enable eth1 via KDE control center

    This is the default content of #cat /etc/network/interfaces (which is configured as a different subnet on static route)

    #this is loopbackip
    auto lo
    iface lo inet loopback
    address 127.0.0.1
    netmask 255.0.0.0


    #this is my eth0 card, built in mobo
    iface eth0 inet static
    address 192.168.0.148
    netmask 255.255.255.0
    gateway 192.168.0.1


    auto eth0

    #this is the problematic one
    iface eth1_rena inet static
    address 172.16.1.143
    netmask 255.255.0.0
    gateway 172.16.0.1


    - I was wondering what is the eth1_rena stands for? But anyway this is part of my solutions (WHICH IS OBVIOUSLY DOESN'T WORK):

    1. put aliases to the /etc/modules.conf

    alias eth0 eth0
    alias eth1 eth1_rena
    (I've tried every possible aliases, but maybe anybody could suggest me one)

    2. I've tried to play around the /etc/networks/interfaces file for eth1 with every possible configurations including dhcp configuration (maybe somebody could suggest any, since I am terrible in networking =P )

    3. I've tried to modconf and install the driver, but honestly i'm going blindly on this.


    I've read somewhere about IRQ configuration, but since i'm terrible in networking... could someone suggest me what to do regarding this matter?

    NOTE: My kernel support module bonding.ko, if it is got anything to do with this problem... and yes, i do restart the networking service everytime i changed my configuration.

    Thanks in advanced.

  2. #2
    Just Joined!
    Join Date
    Oct 2006
    Posts
    1
    Hi Electroboy,

    Faced the same issue this afternoon and came accross your post while searching for a solution.

    Actually it appear to be debian which is the cause ... It apparently assigns the firewire ethernet to eth1 instead of the classic ethernet interface as I was expecting.
    result is the actual name of the interface is not eth1, nor eth1_rena as the later is just a part of the real name (the rest is not shown).

    So find out the actual name of you ethernet interface and reconfigure everything accordingly. To find out the name, use 'ip' instead of 'ifconfig' :

    @server:~$ ip link show
    1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:d0:b7:29:ad:33 brd ff:ff:ff:ff:ff:ff

    3: eth1_rename_ren: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:17:31:f6:4d:6a brd ff:ff:ff:ff:ff:ff

    4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ieee1394 00:11:d8:00:00:c2:84:70 brd ff:ff:ff:ff:ff:ff:ff:ff
    5: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0



    In my case the real name was eth1_rename_ren ...

    Hope this help !

    To.

  3. #3
    Just Joined!
    Join Date
    Jan 2007
    Posts
    1

    second ethernet card issue

    Thanks.
    The name eth1_rename_ren worked for me. I use Debian etch. I am a common user and not a developer.

    I also explored into /etc/udev/init.d files. A file named z25_persistent-net .rules was there. It showed Mac ids and names for the same. I could see that I had two ethernet MAC ids with same name as eth0. Further I also had a ethernet MAC ID due to a card I attempted earlier, which had eth1 link.
    So I commented the old card entry and changed the name for one of the present cards to eth1.

    Now I have the names eth1 and eth0 for the two cards.

    I edited the /etc/network/interfaces files accordingly for eth0 and eth1, instead of eth0 and eth1_rename_ren.

    Now both cards are working.
    That was some fun. thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •