Closed andrewleech closed 3 years ago
Good news: AX88179 adapters work
Hunting through my cupboard I found an old USB hub / Ethernet adaptor that just happened to also be a AX88179. Tried it on the car, with my other AX88179 adapter on the laptop, set the laptop to static IP and straight away the ping 172.16.250.248
went through! The telnet to 123 also works :-)
Note: make sure the car ignition is on, but engine not running. I think on some/most previous attempts I just turned the screen on manually, but didn't turn the car on.
I just used a normal Ethernet cable directly between the two USB Ethernet adaptors, they did not need a cross-over cable.
Once it was working, I swapped the two USB Ethernets over again, so the old one on my laptop and the new one I got from Amazon connected to car - this also worked fine now.
So the failure I saw in the top post might have been from the other USB ethernet I previously used on my laptop, or simply from not having the car ignition on.
AX88179 adapters have become common online as they're natively supported on Nintendo switch, so many/most usb3 adapters advertised as supporting the switch should be this chip. Either way, the Amazon link I noted in the top post explicitly listed this chip was in use.
My boy has a Nintendo switch adaptor, 🤔 but I don’t have the password to 913, so doubt I could tell you if it works or not
Tried my boys official switch adaptor, telnet said couldn’t connect
Tried my boys official switch adaptor, telnet said couldn’t connect
It would be worth checking the adapter on computer / device manager to see what USB vid/pid it is.
It says it’s an AX88772A if that’s what you mean, but I couldn’t find a driver for it (only have a windows 7 pc available to me at the mo)
Ah, AX88772A is the older chipset not directly supported by the firmware - however this is the same chip as the DUB-E100 meaning this adapter can often have its vid/pid changed to match the DUB-E100 which will then work. I'm not sure if it'll still work on the Switch with the changed vid/pid though... https://www.digital-eliteboard.com/threads/how-to-changing-usb-to-ethernet-adapter-vid-pid-to-match-d-link-dub-e100.496271/
I've checked (with grep) all the firmware packs I've got access to - it looks like all current MMX2 firmware should support these two ASIX AX88178 and AX88179 ethernet adapters: | Firmware | ASIX |
---|---|---|
Audi (A3) MHI2_ER_AU37x_P5089 MU1326 MMX2 | yes | |
Audi (A3) MHI2_ER_AU37x_P5089 MU1326 MMX2 | yes | |
Audi (A4-A5-Q5-Q7) MHI2_ER_AUG22_K3346 MU1438 MMX2 | yes | |
Audi (A4-A5-Q5-Q7) MHI2_ER_AUG22_K3346 MU1438 MMX2 | yes | |
Audi (A6-A7) MHI2_ER_AU57x_K3663 MU1425 MMX2 | yes | |
Audi (A6-A7) MHI2_ER_AU57x_K3663 MU1425 MMX2 | yes | |
Audi (Q2) MHI2_ER_AU276_P5088 MU1325 MMX2 | yes | |
Audi (Q2) MHI2_ER_AU276_P5088 MU1325 MMX2 | yes | |
Audi (R8) MHI2_ER_AU62x_P5099 MU1340 MMX2 | yes | |
Audi (R8) MHI2_ER_AU62x_P5099 MU1340 MMX2 | yes | |
Audi (TT) MHI2_ER_AU43x_P5098 MU1339 MMX2 | yes | |
Audi (TT) MHI2_ER_AU43x_P5098 MU1339 MMX2 | yes | |
Seat MHI2_ER_SEG11_P4708 MU1409 MMX2 | yes | |
Seat MHI2_ER_SEG11_P4708 MU1409 MMX2 | yes | |
Skoda MHI2_ER_SKG11_K3343 MU1433 MMX2 | yes | |
Skoda MHI2_ER_SKG11_K3343 MU1433 MMX2 | yes | |
Skoda MHI2_ER_SKG13_P4526 MU1440 MMX2 | yes | |
Skoda MHI2_ER_SKG13_P4526 MU1440 MMX2 | yes | |
VW MHI2_ER_VWG11_K3332 MU1187 MMX2 | yes | |
VW MHI2_ER_VWG11_K3332 MU1187 MMX2 | yes | |
VW MHI2_ER_VWG11_K3342 MU1427 MMX2 | yes | |
VW MHI2_ER_VWG11_K3342 MU1427 MMX2 | yes | |
VW MHI2_ER_VWG13_P4521 MU1367 mmx2 | yes | |
VW MHI2_ER_VWG13_P4521 MU1367 mmx2 | yes |
The only firmware packs I have that don't support it are MMX1 - looking manually at these it appears they literally only support the two versions of D-Link DUB-E100 (ven=2001, dev=3c05 or ven=2001, dev=1a02). | Firmware | ASIX |
---|---|---|
Audi (A3) MHIG_EU_AU_K1549 MU0404 MMX1 | no | |
Audi (A3) MHIG_EU_AU_K1549 MU0404 MMX1 | no | |
Skoda MHIG_EU_SK_K1552 MU0411/EU MMX1 | no | |
Skoda MHIG_EU_SK_K1552 MU0411/EU MMX1 | no | |
Skoda MHIG_EU_SK_K1552 MU0411/RW MMX1 | no | |
Skoda MHIG_EU_SK_K1552 MU0411/RW MMX1 | no | |
VW MHIG_EU_VW_K1550 MU0407 MMX1 | no | |
VW MHIG_EU_VW_K1550 MU0407 MMX1 | no |
Should we merge this info into a Wiki page or FAQ?
I was wondering about how much usb-eth documentation we should add. We don't have login details to share with people anyway so there's only so much we can provide...
We could take the list of possible interfaces to show alternatives maybe. Or we just put this into Wiki -> Research.
Yeah for sure, the ASIX details would be worth listing alongside the DUB
Investigation is no in Wiki: Alternative network adapters
The DUB-E100 can be hard to find in the correct revision, particularly in Australia.
As such I went hunting for other alternatives. In the log files copied off the unit in green screen I saw reference to the other ethernet drivers and the
usblauncher
tool in charge of associating drivers to USB devices.I'd recently updated my firmware to 1367 so still had the firmware pack for that. A grep on the entire SD card revealed\x00 and there it is in plain text after a bit of hex muck (presuably file modes etc). Copy-paste out the right bit and there's the file:
usblauncher
was in theefs-system.img
files. I didn't have much luck finding any way to mound this file as a loop filesystem, however eventually figured I could just look at it with a hex editor. It's pretty easy to manually extract files, just search for \x00usblauncher.lua