|
Home > Archive > Linux Debian support > May 2007 > Networking; strange MAC address
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Networking; strange MAC address
|
|
| Hans Poppe 2007-04-26, 7:12 am |
| Hi,
I've just installed Etch on my laptop (Fujitsu Siemens Amilo Pro) and
everything is working fine. However something is a bit strange.
The laptop has two ethernet cards, an onboard cable connection and a
wireless card (Intel 2200). The wireless card was not automagically
installed, and I had to modprobe ipw2200 and download and copy firmware. It
went very well, and the WiFi is now working just fine. The strange part is
the output from ifconfig:
eth0 Link encap:UNSPEC HWaddr
06-E4-0A-00-BB-03-10-05-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:6816 dropped:6816 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth1 Link encap:Ethernet HWaddr 00:0A:E4:B5:15:28
inet addr:10.1.1.34 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:feb5:1528/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1159 (1.1 KiB) TX bytes:4419 (4.3 KiB)
Interrupt:233 Base address:0x2000
eth2 Link encap:Ethernet HWaddr 00:13:CE:C2:B3:13
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:7 errors:3686 dropped:3686 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14408910 (13.7 MiB) TX bytes:1865441 (1.7 MiB)
Interrupt:233 Base address:0x4000 Memory:b8006000-b8006fff
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:11824 errors:0 dropped:0 overruns:0 frame:0
TX packets:11824 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2257618 (2.1 MiB) TX bytes:2257618 (2.1 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
What is this eth0 thing? Where did this (illegal) MAC address come from?
I suspect that it's a result of the WiFi not being detected correctly under
installation (even though it showed up when using lshw). (Maybe since it's
Debian there was an issue with the proprietary firmware?)
Shouls I be worried about this? Is there a way to correct this so that eth0
becomes what now is eth1 (onboard cabled card) and the WiFi becomes eth1
and no eth2 exist?
Any ideas?
Regards
Hans Poppe
Oslo, Norway
--
"As we enjoy great advantages from the inventions of others, we should be
glad of an opportunity to serve others with any invention of ours, and this
we should do freely and generously."
-- Benjamin Franklin
| |
| Ben Peddell 2007-04-29, 1:11 pm |
| Hans Poppe wrote:
>
> eth0 Link encap:UNSPEC HWaddr
> 06-E4-0A-00-BB-03-10-05-00-00-00-00-00-00-00-00
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:6816 dropped:6816 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
This is Ethernet over IEEE1394. Try removing eth1394 from the kernel.
>
> eth1 Link encap:Ethernet HWaddr 00:0A:E4:B5:15:28
> inet addr:10.1.1.34 Bcast:10.1.1.255 Mask:255.255.255.0
> inet6 addr: fe80::20a:e4ff:feb5:1528/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1159 (1.1 KiB) TX bytes:4419 (4.3 KiB)
> Interrupt:233 Base address:0x2000
Standard ethernet.
>
> eth2 Link encap:Ethernet HWaddr 00:13:CE:C2:B3:13
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:7 errors:3686 dropped:3686 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:14408910 (13.7 MiB) TX bytes:1865441 (1.7 MiB)
> Interrupt:233 Base address:0x4000 Memory:b8006000-b8006fff
WiFi
| |
| Hans Poppe 2007-05-07, 7:11 am |
| Ben Peddell wisely stated:
> Hans Poppe wrote:
>
> This is Ethernet over IEEE1394. Try removing eth1394 from the kernel.
>
>
> Standard ethernet.
>
>
> WiFi
Hi, thanks for the suggestion. I've tried to remove eth1394 and reboot, no
change. This is a laptop that doesn't have FireWire, and thus this should
not have been "dicovered" during installation(?).
Anyway, is there a reason for FireWire to use this, obviously, incorrect MAC
address? If it were in a network using ieee1394, would ARP-ing for this
machine work?
Regards
Hans Poppe
--
"As we enjoy great advantages from the inventions of others, we should be
glad of an opportunity to serve others with any invention of ours, and this
we should do freely and generously."
-- Benjamin Franklin
| |
| AJackson 2007-05-08, 1:13 pm |
| On May 7, 10:08 am, Hans Poppe <hpo...@online.no> wrote:
> Hi, thanks for the suggestion. I've tried to remove eth1394 and reboot, no
> change. This is a laptop that doesn't have FireWire, and thus this should
> not have been "dicovered" during installation(?).
I guess it is discovered during boot, prob. It isn't in "lsmod" list,
is it?
I would guess that it is not the problem that your WiFi wasn't
discovered during installation. I guess that it's becouse Debian
can't distribute the firmware for it. So the WiFi didn't (couldn't)
work during installation. But this is speculation, as I don't have any
laptop with ipw22000 to test on.
Any way, it shouldn't be any problems with having eth0 like this. I
have this in my laptop, and have no problems with it, what so ever. I
plug and play with both wired and wireless lan without that disturbing
anything (unless you try to start eth0 from /etc/network/interfaces
which obvious is wrong in this case). I am running Etch on HP
Pavillion zd8000 model.
> Anyway, is there a reason for FireWire to use this, obviously, incorrect MAC
> address? If it were in a network using ieee1394, would ARP-ing for this
> machine work?
Don't know. I have not tried to use FIreWire net, no cabel or other
computer to test on. But that should beat the crap out of USB2 for
file transfer any way (if it works :-) )
I have READ that it exists a profile that should work like a network
over FireWire (or am I mixing this up with bluetooth :-) )
> Regards
>
> Hans Poppe
Anyway, IF you want to rename your interfaces, you can do that in "/
etc/udev/rules.d/z25_persistent-net.rules", which is the Debian way.
(search in http://wiki.debian.org/)
But be carefull! Wrong naming and/or not updating your configurations
(like /etc/network/interfaces or /etc/ethers), you will have problems
starting networks on your machine.
I would recommend naming your wired ethernet (now eth2) to "lan" and
your wireless to (now eth1) "wlan" and your FireWire (now eth0) to
"firewire" or something like that. So you can easy identify them in
logs and so on.
By the way, if you are running true portable (different nets now and
then) and using Gnome (ro KDE, but not tested), you rather get network-
manager set up your network for you, works REALY smooth. You need
package network-manager-gnome or network-manager-kde for this to work.
On stational machines and servers you should NOT install this package,
as it needs a user to be logged in to start a connection. And that
would be bad in those cases, as with a webserver :-)
Good luck
| |
| AJackson 2007-05-10, 7:13 pm |
| On May 8, 5:16 pm, AJackson <anders.jack...@gmail.com> wrote:
>
> By the way, if you are running true portable (different nets now and
> then) and using Gnome (ro KDE, but not tested), you rather get network-
> manager set up your network for you, works REALY smooth. You need
> package network-manager-gnome or network-manager-kde for this to work.
Sorry to comment on my own post, but to make network-manager to work,
you need to remove all network interfaces EXCEPT lo from /etc/network/
interfaces. Any interface managed by /etc/networks/interfaces will
not be managed by n-m.
Good luck
|
|
|
|
|