This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

J5Create JU130 (with AX88179 chipset) compatibility

0

I just bought J5Create's JU130 USB to ethernet adapter, specifically to inspect packets as a "man-in-the-middle" in order to debug a problem we're having with an embedded device we're developing. This device has an AX88179 inside (according to Windows 7's device manager).

Is this compatibile with Wireshark? It is not appearing in the interface list. According to this FAQ on ASIX's website, it seems like it should work.

Any ideas?

asked 14 Nov '14, 12:01

zman97211's gravatar image

zman97211
11112
accept rate: 0%


One Answer:

0

Is this compatibile with Wireshark?

Wireshark isn't directly compatible, or incompatible, with any networking hardware; for example, it has no device drivers. It relies on the hardware's drivers, the OS's native packet capture mechanism on UN*X and the OS's NDIS and the WinPcap driver (which isn't a hardware device driver) on Windows, and the libpcap/WinPcap library.

The code above the driver shouldn't be treating any particular Ethernet adapter differently on Windows; does your adapter show up in the "Network and Sharing Center" pane in Control Panel?

answered 14 Nov '14, 16:08

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%

It does show up in the control panel. The solution I ended up using was passing the USB-Ethernet adapter through to Ubuntu 12.04 running inside VirtualBox. Wireshark was able to use the adapter there without a problem.

(17 Nov '14, 05:46) zman97211

Did you plug the JU130 in after you started Wireshark? If so, what happens if you quit Wireshark and restart it? Does it show up again?

If it doesn't show up in that case, or if you plugged it in before you started Wireshark, what happens if you plug the JU130, reboot the machine, and start Wireshark? Does Wireshark see it then?

This might be a case of WinPcap not handling interfaces plugged in after the program starts, or not handling adapters added after the system booted. Those tests could help determine whether that's the case.

(17 Nov '14, 16:57) Guy Harris ♦♦