eth0 & eth1 have same MAC address

anctop · 12-13-2016, 09:40 PM

Quote:

Originally Posted by Ztcoracat

After a short online search the only distribution that I found that supports any of the killer network interface cards is Ubuntu. And that's only some of those cards.

I don't think Slackware works with that card.

No, it does work.

The model of the NIC is "Killer Networking E2400".
According to the manufacturer's FAQ (http://www.killernetworking.com/driv...iew=topic&id=2), it requires "alx" kernel driver support.
The Linux 4.4 kernel (which is in Slackware 14.2) already supports it under

Ethernet driver support
- Atheros devices
  - Qualcomm Atheros AR816x/AR817x support

After so many attempts, I feel that the MAC address abnormality should be OS-independent, otherwise two distinct MACs should have been displayed in the BIOS but it does not.
One possibility (the worst one) is that I get a defective mainboard.
Another possiblity is that it is the manufacturer's design (which then calls for confirmation).

Ztcoracat · 12-13-2016, 10:50 PM

Quote:

Originally Posted by anctop

No, it does work.

The model of the NIC is "Killer Networking E2400".
According to the manufacturer's FAQ (http://www.killernetworking.com/driv...iew=topic&id=2), it requires "alx" kernel driver support.
The Linux 4.4 kernel (which is in Slackware 14.2) already supports it under

Ethernet driver support
- Atheros devices
  - Qualcomm Atheros AR816x/AR817x support

After so many attempts, I feel that the MAC address abnormality should be OS-independent, otherwise two distinct MACs should have been displayed in the BIOS but it does not.
One possibility (the worst one) is that I get a defective mainboard.
Another possiblity is that it is the manufacturer's design (which then calls for confirmation).

That's great that it works for you. Thanks for the link.

I certainly hope in your case that you don't have a defective board.
If you did I'd think you'd start noticing things that aren't right.

Ztcoracat · 12-13-2016, 11:05 PM

Any clue anctop when the alx driver was introduced into the kernel?

The best I found was sometime in 2014.

I could go through the change logs but that can take days or hours.

Fat_Elvis · 12-13-2016, 11:18 PM

Quote:

Originally Posted by Ztcoracat

Yes I helped with one of them on an Alienware laptop last year.
If my memory serves me correctly the ath10k driver is needed and should be in the newer kernel.

http://askubuntu.com/questions/76982...n-ubuntu-16-04

I agree; Ubuntu and Mint are much more user friendly with the UEFI interface.

Grub on top of anything is fine with UEFI. I can probably boot WinXP from Grub on UEFI, lol.

Ubuntu, AFAIK, has a super-duper Microsoft(TM) signed grub image though, that curiously acts up when booting custom kernels. That one helps with laptops that don't allow disabling secure boot.

anctop · 12-13-2016, 11:48 PM

Quote:

Originally Posted by Ztcoracat

Any clue anctop when the alx driver was introduced into the kernel?

The best I found was sometime in 2014.

I could go through the change logs but that can take days or hours.

No idea about the exact version number when the "alx" driver was first introduced into the kernel.

From the old tarballs I have in hand, it is known that versions <= 3.8.8 do NOT have it, but versions >= 4.0.7 have it.

My Slackware installation on this new mainboard has been running for about two weeks without any observable fault. It can be accessed via SSH at both NICs as usual.
I'll monitor it for a longer time before actual deployment.

tramsch · 12-14-2016, 06:58 AM

If you are curious enough and have the time and resources, you could connect one LAN cable to either port, assign two different IP addresses and ping them from another machine.
Then take a look with tcpdump or tshark what actually appears on the interfaces.

Ztcoracat · 12-14-2016, 01:01 PM

Quote:

Originally Posted by anctop

No idea about the exact version number when the "alx" driver was first introduced into the kernel.

From the old tarballs I have in hand, it is known that versions <= 3.8.8 do NOT have it, but versions >= 4.0.7 have it.

My Slackware installation on this new mainboard has been running for about two weeks without any observable fault. It can be accessed via SSH at both NICs as usual.
I'll monitor it for a longer time before actual deployment.

Got it; thanks.

c0wb0y · 12-14-2016, 01:04 PM

Practically, that should not be an issue because one wouldn't assign them both to the same subnet, would it? That's why it can't be bonded as well which kinda sucks.

anctop · 12-18-2016, 08:34 PM

Just an update.

I've lodged a support request at Gigabyte about the issue. They tell me to check with "ipconfig /all" under Windows.
Here is the output :

Code:

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller
   Physical Address. . . . . . . . . : 1C-1B-0D-09-34-D0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
   Physical Address. . . . . . . . . : 1C-1B-0D-09-34-D2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

The two NICs have distinct MAC addresses.

The problem is then reduced to Linux and/or BIOS support.

jefro · 12-19-2016, 02:46 PM

Thanks for the update.

Running that card in windows has a number of changes so we really can't fully use it other than to say it seems to work in Windows. Almost no boards are ever tested in linux so we can't say if it would ever work correctly in Linux.

Mac address still seems to be from Killer products.

It may be possible in linux to force a mac address.