Re: different MAC addresses

2.4.29 may be doing things at the network software stack level  that you may not be aware of. So, try it again using 2.4.18. I am using 2.4.18 and I didn't see that problem.

Jernej Porenta wrote:

> Hello!
>
> Maybe this topic was already covered but I cannot find the answer in the
> archives nor on google...
>
> I have server with integrated Intel E100 NIC:
>
> When I load eepro100.o module from 2.4.29 linux kernel built by myself
> from vanilla sources I get (dmesg):
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://www.scyld.com/network/eepro100.html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
> <[email protected]> and others
> PCI: Found IRQ 11 for device 02:08.0
> eth0: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller,
> 00:03:47:F2:1C:A3, IRQ 11.
>    Board assembly 000000-000, Physical connectors present: RJ45
>    Primary interface chip i82555 PHY #1.
>    General self-test: passed.
>    Serial sub-system self-test: passed.
>    Internal registers self-test: passed.
>    ROM checksum self-test: passed (0x04f4518b).
>
> Then I execute:
> ifconfig eth0 10.237.1.100 netmask 255.255.255.0
>
> and this is what I get:
> eth0      Link encap:Ethernet  HWaddr 08:00:46:06:FF:CF
>            inet addr:10.237.1.100  Bcast:10.237.1.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:1196 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:1144 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:157230 (153.5 Kb)  TX bytes:185526 (181.1 Kb)
>            Interrupt:11 Base address:0xa000
>
> Could you please explain to me how can HWaddr (08:00:46:06:FF:CF) differ
> from the MAC address in the dmesg (00:03:47:F2:1C:A3)? The problem is
> because the machine is operating on the network with "dmesg" MAC address
> (00:03:47:F2:1C:A3) not with the HWaddr (08:00:46:06:FF:CF).
>
> When the dhcp client request the IP it sends MAC address from HWaddr
> (08:00:46:06:FF:CF) and the result is that the DHCP server responds to
> new MAC which is non-routable, because nobody doesn't know anything
> about that MAC (08:00:46:06:FF:CF).
>
> I tried changing the MAC address of eth0 with "ifconfig eth0 hw ether
> 00:03:47:F2:1C:A3" but the result was the same...
>
> I even tried e100.o driver, but no success...
>
> Does anyone have a simple solution for my problem...
>
> thanks in advance,
>
> regards,
>
> --
>
> Jernej Porenta
>
> ========================
> Flextronics d.o.o.
> Vodovodna 99
> 1000 Ljubljana, Slovenia
> Tel: +386 1 53 09 500
> Fax: +386 1 53 09 514
> ========================
> _______________________________________________
> eepro100 mailing list
> [email protected]
> http://www.scyld.com/mailman/listinfo/eepro100