M+ : cannot connect over USB-ethernet

Reach Module / M+ / M2 Hardware integration
1

Hi,
I’m trying to do something that I think should be possible (and I vaguely remember doing in the past), but doesn’t work anymore.

Reach M+ is connected via USB cable to a PC. It appears as an ethernet interface; PC gets IP 192.168.2.127 via DHCP.
A packet capture shows Reach advertising itself via MDNS I think, but my PC can’t resolve “reach.local”. Could be my OS’ fault, that’s ok.

No matter, I know the IP of the Reach : 192.168.2.15.
But I can’t load a webpage at that address : TCP connections to port 80 (and 5000) are refused.
I can SSH to reach@192.168.2.15 no problem.

Tried to follow along with Ethernet Over USB - #2 by igor.vereninov
but without success (i.e. changing the address of the PC side to 192.168.2.2)

Any suggestions?

****************** excerpt from packet capture:
|No.|Time|Source|Destination|Protocol|Length|Info|
|---|---|---|---|---|---|---|
|67|129.023945389|192.168.2.15|224.0.0.251|MDNS|81|Standard query response 0x0000 A, cache flush 192.168.2.15|
|68|130.022913485|fe80::95:c29a:3ca9:cd68|ff02::fb|MDNS|91|Standard query 0x0000 A reach.local, "QM" question|
|69|130.023032038|192.168.2.127|224.0.0.251|MDNS|71|Standard query 0x0000 A reach.local, "QM" question|
|70|130.025137725|192.168.2.15|224.0.0.251|MDNS|81|Standard query response 0x0000 A, cache flush 192.168.2.15|
|71|132.023565616|fe80::95:c29a:3ca9:cd68|ff02::fb|MDNS|91|Standard query 0x0000 A reach.local, "QM" question|
|72|132.023667531|192.168.2.127|224.0.0.251|MDNS|71|Standard query 0x0000 A reach.local, "QM" question|
|73|132.025719392|192.168.2.15|224.0.0.251|MDNS|81|Standard query response 0x0000 A, cache flush 192.168.2.15|
|74|142.087782238|192.168.2.127|192.168.2.15|TCP|74|45490 -> 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1 TSval=3999406339 TSecr=0 WS=128|
|75|142.088222207|192.168.2.15|192.168.2.127|TCP|54|80 -> 45490 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0|
2

Oops, some additional info: running firmware 26.1, and it’s connected to a restrictive wifi network (so reachview cannot see it).

4

Hi @chrisb,

Sorry, it seems I don’t quite understand the issue you faced. Could you clarify your goal, please? Why do you try to access Reach via TCP?

5

To configure the M+ via the web UI on a proper computer. Way more convenient than the phone UI , that also requires me to disconnect from wifi, walk 5-10 mins to get far enough away that the Reach starts its AP, then connect, tweak wifi settings, walk back…

I’m speculating that in this case, the reach app is maybe not be starting / listening on port 80 due to timesync services not working.

6

Hi @chrisb,

You’re right. It’s not possible to access ReachView if time sync isn’t passed. I got your point regarding UI. However, please note that we recommend using the ReachView 3 app since it contains all the latest features and improvements. It’s available on iOS and Android only.

8

Thank you for confirming this non-obvious fact.

9

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.