[Cialug] How is this possible?

Tom Sellers tsellers2009 at gmail.com
Mon Apr 3 12:44:47 CDT 2017


In reply to David's question about the output of ifconfig here is the
information finally.
Sorry for the delay!

root at Olive:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:01:03:dd:e3:6d
          inet addr:192.168.1.59  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::201:3ff:fedd:e36d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16331 errors:0 dropped:3 overruns:1 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1932792 (1.8 MiB)  TX bytes:3076 (3.0 KiB)
          Interrupt:16

eth1      Link encap:Ethernet  HWaddr 00:0c:76:be:b9:a9
          inet addr:192.168.9.254  Bcast:192.168.9.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:76ff:febe:b9a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3447 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3403 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:341784 (333.7 KiB)  TX bytes:333405 (325.5 KiB)
          Interrupt:23 Base address:0xe800

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:64 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9446 (9.2 KiB)  TX bytes:9446 (9.2 KiB)

root at Olive:~ #

The problem is that based on the MAC addresses the built-in network adapter
is 00:0c:76:be:b9:a9 which shows up above as eth1 not eth0.

I tried removing the added 3com card and booting with a cd version and it
sees the built in adapter as eth0 with 00.0c.76.be.b9.a9 as correct.  I
don't seem to be able to make it boot up with both adapters installed
without the adapters being reversed as shown in the ifconfig above.

On Thu, Mar 30, 2017 at 3:58 PM, David Champion <dchamp1337 at gmail.com>
wrote:

> What's the output of "ifconfig" on that system?
>
> -dc
>
> On Thu, Mar 30, 2017 at 3:37 PM, Tom Sellers <tsellers2009 at gmail.com>
> wrote:
>
> > I have a small desktop computer with two wired network connections.  One
> is
> > built into the motherboard and the other is a 3com network card that I
> have
> > added.
> >
> > The built in network card should be eth0 and the added card should be
> > eth1.  The eth0 wired connection is set to use dhcp while the eth1 wired
> > network card is assigned an IP.
> >
> > When I boot the system up with no network cable connected to eth0 and a
> > cable to my dhcp network on eth1and run ifconfig. I get a display that
> > indicates eth0 has an IP on my dhcp network and eth1 shows the assigned
> ip
> > given it.
> >
> >  When I ping the dhcp network address I get a response and when I ping
> the
> > assigned IP I also get a response.  Both appear to be using the added
> > network card (eth1) even though the two network connections show separate
> > hardware addresses.
> >
> > Can anyone explain how this is possible?
> >
> > This all started when I was unable to get linux to get a dhcp address on
> > eth0 with both network jacks cabled to their respective networks.  I
> didn't
> > think the same card could have two separate IP addresses.
> >
> > Not that familiar with linux!
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> >
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>


More information about the Cialug mailing list