Announcement

Collapse
No announcement yet.

nics renamed?!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    nics renamed?!

    I have 2 nics (eth0 and eth1). From dmesg:

    4294687.286000] eth0: Identified chip type is 'RTL8169s/8110s'.
    [4294687.286000] eth0: RTL8169 at 0xe0a54000, 00:0f:b5:fb:c0:88, IRQ 201

    That's fine. I've been using eth1, which is a card I installed last year when eth0 wouldn't play right. Any how, here's the output of ifconfig:

    eth2 Link encap:Ethernet HWaddr 00:133:1D6:63
    UP BROADCAST 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:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:193 Base address:0xa000

    eth3 Link encap:Ethernet HWaddr 00:0F:B5:FB:C0:88
    inet addr:192.168.15.101 Bcast:192.168.15.255 Mask:255.255.255.0
    inet6 addr: fe80::20f:b5ff:fefb:c088/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4252 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3131 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:5778288 (5.5 MiB) TX bytes:318233 (310.7 KiB)
    Interrupt:201 Base address:0x4000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)


    I thought it quite odd to have eth2 and eth3. This is causing some problems. Just upgraded from Breezy by changing the sources.list. Any thoughts?


    Oh, btw, I can enable either (eth2 & eth3), but must re-enable each time I reboot (and leaving the machine on all the time is not necessarily an option). Also, at least firestarter has taken issue with this arrangement. Perhaps other apps as well?

    #2
    Re: nics renamed?!

    Edit /etc/iftab, eg:

    eth0 mac 00:133:1D6:63 arp 1
    eth1 mac 00:0F:B5:FB:C0:88 arp 1

    will make them eth0 and eth1 instead of 2 and 3.

    Comment


      #3
      Re: nics renamed?!

      Kewl. I'll give that a shot when I can get back home on my machine. I'm currently doing 2wks USAR duty. Maybe I can get these stupid military computers to allow me to access my own machine remotely. . . .

      Look for a post in a couple of weeks.

      Tnx.

      ~JC

      Comment


        #4
        Re: nics renamed?!

        Originally posted by marble
        Edit /etc/iftab, eg:

        eth0 mac 00:133:1D6:63 arp 1
        eth1 mac 00:0F:B5:FB:C0:88 arp 1

        will make them eth0 and eth1 instead of 2 and 3.
        Here's the current output to /etc/iftab:

        # This file assigns persistent names to network interfaces. See iftab(5).
        eth0 mac 00:40:05:8c:c5:db
        eth1 mac 00:20:ed:68:23:f7


        Looks like this should be good. Any other ideas?

        Comment


          #5
          Re: nics renamed?!

          Originally posted by jchammin
          Originally posted by marble
          Edit /etc/iftab, eg:

          eth0 mac 00:133:1D6:63 arp 1
          eth1 mac 00:0F:B5:FB:C0:88 arp 1

          will make them eth0 and eth1 instead of 2 and 3.
          Here's the current output to /etc/iftab:

          # This file assigns persistent names to network interfaces.  See iftab(5).
          eth0 mac 00:40:05:8c:c5:db
          eth1 mac 00:20:ed:68:23:f7


          Looks like this should be good.  Any other ideas?
          How is that good? The mac addresses in your file don't match the ones your cards have (according to the ifconfig output above). It's also missing the 'arp 1' points, which could make your bootup slower than it needs to be, IIRC.

          Comment

          Working...
          X