Comment # 10
on bug 9119
from Tyson Key
On another note, although it sadly doesn't let me test the limits of the
InListPassiveTarget Response dissection (since separate packets seem to be
generated for each tag response), but the hardware itself seems to support more
than two tags in its field:
tyson@tyson-HP-Compaq-2510p-Notebook-PC:~/wireshark-1.11.0-SVN-51333$ nfc-list
nfc-list uses libnfc libnfc-1.7.0-rc4-9-g3584338
NFC device: ACS ACR122U 00 00 / ACR122U103 opened
3 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 44
UID (NFCID1): 04 c7 43 ba 34 23 80
SAK (SEL_RES): 00
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 44
UID (NFCID1): 04 45 57 ba 34 23 80
SAK (SEL_RES): 00
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 44
UID (NFCID1): 04 f2 80 ba 34 23 80
SAK (SEL_RES): 00
On the other hand, InAutoPoll can provide a response referring to a maximum(?)
of two targets - but the dissector seems to handle them very gracefully,
despite LibNFC's "nfc-poll" utility only providing details for one tag. Very
impressive!
You are receiving this mail because:
- You are watching all bug changes.
