Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Cardreader

Need help with peripherals or devices?
Post Reply
Message
Author
elwis
Posts: 1
Joined: 2017-09-19 13:27
Location: Sweden

Cardreader

#1 Post by elwis »

Hi all,
I had an idea of building a small pythonapp for reading Mifare cards that will probably end up in a raspberry or such in the end. However, when I plug in my reader dmesg tells me this:

Code: Select all

[ 4974.743601] usb 2-1.1: new full-speed USB device number 6 using ehci-pci
[ 4974.857697] usb 2-1.1: New USB device found, idVendor=076b, idProduct=5427
[ 4974.857706] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4974.857708] usb 2-1.1: Product: 5427 CK
[ 4974.857710] usb 2-1.1: Manufacturer: HID OMNIKEY
[ 4974.857712] usb 2-1.1: SerialNumber: 01010053344D303033061F2840143630
[ 4974.859950] cdc_eem 2-1.1:1.1 usb0: register 'cdc_eem' at usb-0000:00:1d.0-1.1, CDC EEM Device, 02:31:b9:d8:c7:0a
[ 4974.890024] cdc_eem 2-1.1:1.1 enp0s29u1u1i1: renamed from usb0
I expected it to end up like "/dev/usb0" but seem to be somekind of network device? I did install the pcsc tools and I can read the card from there

Code: Select all

Scanning present readers...
0: HID OMNIKEY 5427 CK (01010053344D303033061F2840143630) 00 00
I thought I could just use gnetplus.py or something and read from /dev/usb0 just like I did back in the days, and now I don't even know where the mysterious "epnp0s29u1i1" might reside. Happy for all kinds of enlightenments!

Regards

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Cardreader

#2 Post by p.H »

I do not know about this specific device, but EEM stands for "Ethernet Emulation Model" so yes, the kernel considers it as an ethernet device and creates a network interface "usb0" for it. Systemd/udev renames the interface according to the "predictable names specification".

AFAIK, network interfaces never were block device nor character devices and never had device files in /dev.
Network interfaces can be seen with "ip" commands.

Post Reply