lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200904201457.37704.marcin@juszkiewicz.com.pl>
Date:	Mon, 20 Apr 2009 14:57:36 +0200
From:	Marcin Juszkiewicz <marcin@...zkiewicz.com.pl>
To:	Peter Korsgaard <jacmet@...site.dk>
Cc:	netdev@...r.kernel.org
Subject: dm9601 as ethX or usbX?

Hi

I have two dm9601 based adapters. First one is recognized as 'ethX':

[269425.698235] usb 1-5.4.1: new full speed USB device using ehci_hcd and address 16
[269425.788125] usb 1-5.4.1: configuration #1 chosen from 1 choice
[269425.793478] eth1: register 'dm9601' at usb-0000:00:1a.7-5.4.1, Davicom DM9601 USB Ethernet, 00:60:6e:7f:0c:20

But second is 'usbX':

[269530.937166] usb 1-5.3: new full speed USB device using ehci_hcd and address 19
[269531.048917] usb 1-5.3: configuration #1 chosen from 1 choice
[269531.050188] dm9601: No valid MAC address in EEPROM, using 52:9f:f0:e8:44:36
[269531.054054] usb0: register 'dm9601' at usb-0000:00:1a.7-5.3, Davicom DM9601 USB Ethernet, 52:9f:f0:e8:44:36

Both has same vendor/product id:

Bus 001 Device 019: ID 0a46:9601 Davicom Semiconductor, Inc. DM9601 To Fast Ethernet Adapter
Bus 001 Device 018: ID 0a46:9601 Davicom Semiconductor, Inc. DM9601 To Fast Ethernet Adapter

but they differ in details - eth1 one has iManufacturer, iProduct, iSerial 
fields filled, usb0 one has them empty:

  iManufacturer           1 DM9601 USB NNC                                                  
  iProduct                2 Davicom CO., LTD                                                
  iSerial                 3 9601      

Is this normal behaviour of those adapters that ones with empty eeprom
ends as usbX?

I would prefer to have both as ethX as I use them in devices where usbX
as usually usb-gadget (g_ether) and as such usb0 is configured in total 
different scheme. 

I know that one of options would be using udev and renaming of interface 
but then I would have to remember to always copy that rule to each device.

Regards, 
-- 
JID:      hrw@...ber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ