"Use this device" Nothing Happens

Submitted by AboveUnrefined on #1

<p>Hello!
</p>
<p>I'm in the middle of trying to get things working via the usb port on a Linksys e3000 router and a windows 10 client. Everything is running and set up fine, the problem that's happening is that when I go ahead and select "Use this device" from the client software absolutely *nothing* happens. I've tried using a couple different USB devices, both of them showed up as available, but when I click on "Use this device" nothing happens.; no log events, nothing. Am I missing something? I can't find any details as to why nothing would happen... it's a little vexing since I can't find any feedback as to what the problem could be.
</p>
<p>Here's some details about the setup:
</p>
<p>Server: MIPSEL build 3.8.1<br />
Linksys e3000<br />
Tomato<br />
Version 1.28 by shibby<br />
Binary runs with automount script with: `/cifs1/tomato-e3000/vhusbdmipsel -b -r /cifs1/tomato-e3000/log -c /cifs1/tomato-e3000/config`
</p>
<p>Client: Windows 10 4.6.3 - driver installation succeeded successfully, no sign of issue going on with that.
</p>
<p>Server log:
</p>
<p>```<br />
Sun Dec 23 20:24:38 2018 LOG_INFO >>> Starting VirtualHere USB Server v3.8.1 (Built: Dec 14 2018, 14:35:54)<<<<br />
Sun Dec 23 20:24:38 2018 LOG_INFO Using configuration /cifs1/tomato-e3000/config<br />
Sun Dec 23 20:24:39 2018 LOG_INFO Server licensed to=unlicensed max_devices=1<br />
Sun Dec 23 20:24:39 2018 LOG_INFO Using small URB's<br />
Sun Dec 23 20:24:39 2018 LOG_INFO Listening on all network interfaces at TCP port 7575<br />
Sun Dec 23 20:24:39 2018 LOG_INFO Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 21<br />
Sun Dec 23 20:24:49 2018 LOG_INFO 192.168.45.2 connected as connection 1<br />
Sun Dec 23 20:26:18 2018 LOG_INFO Connection 1 remotely disconnected abruptly (rx msg size)<br />
Sun Dec 23 20:26:25 2018 LOG_INFO Connection 1 successfully removed (reason:timeout)<br />
Sun Dec 23 20:36:44 2018 LOG_INFO 192.168.45.2 connected as connection 2<br />
Sun Dec 23 20:37:57 2018 LOG_INFO Connection 2 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 20:37:59 2018 LOG_INFO 192.168.45.2 connected as connection 3<br />
Sun Dec 23 20:38:04 2018 LOG_INFO Connection 2 successfully removed (reason:timeout)<br />
Sun Dec 23 20:38:47 2018 LOG_INFO Connection 3 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 20:38:49 2018 LOG_INFO 192.168.45.2 connected as connection 4<br />
Sun Dec 23 20:38:55 2018 LOG_INFO Connection 3 successfully removed (reason:timeout)<br />
Sun Dec 23 20:39:14 2018 LOG_INFO Connection 4 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 20:39:22 2018 LOG_INFO 192.168.45.2 connected as connection 5<br />
Sun Dec 23 20:39:24 2018 LOG_INFO Connection 4 successfully removed (reason:timeout)<br />
Sun Dec 23 20:55:59 2018 LOG_INFO Connection 5 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 20:56:01 2018 LOG_INFO 192.168.45.2 connected as connection 6<br />
Sun Dec 23 20:56:06 2018 LOG_INFO Connection 5 successfully removed (reason:timeout)<br />
Sun Dec 23 20:56:30 2018 LOG_INFO Connection 6 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 20:56:31 2018 LOG_INFO 192.168.45.2 connected as connection 7<br />
Sun Dec 23 20:56:40 2018 LOG_INFO Connection 6 successfully removed (reason:timeout)<br />
Sun Dec 23 21:01:25 2018 LOG_INFO Connection 7 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 21:02:21 2018 LOG_INFO >>> Starting VirtualHere USB Server v3.8.1 (Built: Dec 14 2018, 14:35:54)<<<<br />
Sun Dec 23 21:02:21 2018 LOG_INFO Using configuration /cifs1/tomato-e3000/config<br />
Sun Dec 23 21:02:21 2018 LOG_INFO Server licensed to=unlicensed max_devices=1<br />
Sun Dec 23 21:02:21 2018 LOG_INFO Using small URB's<br />
Sun Dec 23 21:02:21 2018 LOG_INFO Listening on all network interfaces at TCP port 7575<br />
Sun Dec 23 21:02:21 2018 LOG_INFO Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 21<br />
Sun Dec 23 21:09:18 2018 LOG_INFO 192.168.45.2 connected as connection 1<br />
Sun Dec 23 21:09:46 2018 LOG_INFO Connection 1 remotely disconnected gracefully (rx msg size)<br />
Sun Dec 23 21:09:53 2018 LOG_INFO Connection 1 successfully removed (reason:timeout)<br />
Sun Dec 23 21:10:36 2018 LOG_INFO 192.168.45.2 connected as connection 2<br />
```
</p>
<p>Client log:
</p>
<p>```<br />
16:10:34 INFO :VirtualHere Client 4.6.3 starting (Compiled: Dec 14 2018 15:47:37)<br />
16:10:34 INFO :Using config at C:\Users\Casey\AppData\Roaming\vhui.ini<br />
16:10:34 INFO :IPC available at \\.\pipe\vhclient<br />
16:10:41 INFO :Drivers are up-to-date<br />
16:10:41 INFO :Connected to the VirtualHere Client Driver (Version 2)<br />
```</p>

Submitted by AboveUnrefined on Mon, 2018/12/24 - 07:43

#2

<p>I was able to fish out some more information, seems like after I do click on "Use this device" on the client, I get the following deeper in the messages getting output in the Tomato firmware:
</p>
<p>```<br />
Dec 23 16:39:22 unknown user.info kernel: usb 2-1: reset full speed USB device using ohci_hcd and address 2<br />
Dec 23 16:39:23 unknown user.alert kernel: CPU 0 Unable to handle kernel paging request at virtual address 00000108, epc == c00cedf8, ra == c00cedcc<br />
Dec 23 16:39:23 unknown user.warn kernel: Oops[#1]:<br />
Dec 23 16:39:23 unknown user.warn kernel: Cpu 0<br />
Dec 23 16:39:23 unknown user.warn kernel: $ 0 : 00000000 00000001 00000000 00000000<br />
Dec 23 16:39:23 unknown user.warn kernel: $ 4 : 8131f000 00000001 00000000 fffffffe<br />
Dec 23 16:39:23 unknown user.warn kernel: $ 8 : 00000001 4004550f 8008dcbc fffffff8<br />
Dec 23 16:39:23 unknown user.warn kernel: $12 : 81097808 81097810 83f96cc0 0bdaa7bb<br />
Dec 23 16:39:23 unknown user.warn kernel: $16 : 00000000 83c5a380 00000001 00000001<br />
Dec 23 16:39:23 unknown user.warn kernel: $20 : 83c5a3bc 83f96538 83a5e740 802b2700<br />
Dec 23 16:39:23 unknown user.warn kernel: $24 : 00000002 c00d0fdc<br />
Dec 23 16:39:23 unknown user.warn kernel: $28 : 83188000 83189d48 00000403 c00cedcc<br />
Dec 23 16:39:23 unknown user.warn kernel: Hi : 00000000<br />
Dec 23 16:39:23 unknown user.warn kernel: Lo : 00989680<br />
Dec 23 16:39:23 unknown user.warn kernel: epc : c00cedf8 Tainted: P<br />
Dec 23 16:39:23 unknown user.warn kernel: ra : c00cedcc Status: 1100fc03 KERNEL EXL IE<br />
Dec 23 16:39:23 unknown user.warn kernel: Cause : 00000008<br />
Dec 23 16:39:23 unknown user.warn kernel: BadVA : 00000108<br />
Dec 23 16:39:23 unknown user.warn kernel: PrId : 00019740<br />
Dec 23 16:39:23 unknown user.warn kernel: Modules linked in: cifs ebtable_filter ebtables ip6table_mangle ip6table_filter xt_recent xt_IMQ imq ohci_hcd ehci_hcd leds_usb led_class ledtrig_usbdev usbcore nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_conntrack_proto_gre nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 wl(P) et(P) igs(P) emf(P)<br />
Dec 23 16:39:23 unknown user.warn kernel: Process vhusbdmipsel (pid: 792, threadinfo=83188000, task=810b0400)<br />
Dec 23 16:39:23 unknown user.warn kernel: Stack : 20005514 83f96400 ffffffff 83c5a380 4004550f 83f96400 fffffff2 83c5a380<br />
Dec 23 16:39:23 unknown user.warn kernel: 2abe2cb8 c00d15e8 802a3e90 802e0000 802a3e94 8005c09c 000a00d2 00000000<br />
Dec 23 16:39:23 unknown user.warn kernel: 00000001 00000044 00000000 810b0400 000a00d2 00000000 00000000 81006040<br />
Dec 23 16:39:23 unknown user.warn kernel: 0030268b 8334475c 8001bbe4 83718278 80000000 81006040 8334475c 8333f004<br />
Dec 23 16:39:23 unknown user.warn kernel: 83718278 005d7003 00000302 81006040 800657e4 80065b50 00000001 00000000<br />
Dec 23 16:39:23 unknown user.warn kernel: ...<br />
Dec 23 16:39:23 unknown user.warn kernel: Call Trace:[<c00d15e8>][<80003204>]<br />
Dec 23 16:39:23 unknown user.warn kernel: Code: 02203021 10400018 00403821 <8e050108> 3c03c00d 24637a8c 8ca20000 90440000 90610000<br />
```
</p>
<p>I'm not so sure what I can do with that, but I'll keep digging. Hopefully someone can help point something out that can help alleviate the issue.
</p>
<p>Thanks</p>

Submitted by Michael on Mon, 2018/12/24 - 10:17

#3

OK your kernel is crashing. From memory the tomato kernel is 2.6.x something which is ancient. I think you need to use something in this decade :) e.g openwrt would be better.

Submitted by AboveUnrefined on Mon, 2018/12/24 - 12:44

#4

<p>Hahaha, yeah... I already decided to go down OpenWRT wormhole and it turns out that that's what works! Thank you!
</p>
<p>Merry Christmas!</p>