You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@HipsterBrown
Brand new T2 fails to connect - t2 wifi reports the connection is good. t2 list only reports USB, no LAN (wifi)
It can connect to my network but cannot ping it and cannot ping your host machine from it.
Ran webserver.js sample:
In the browser: I can see the t2 with tesssel01.local:8080, but not via the ip address.
Rooting in, I see that mDNS service fails to reach my network. The service won't start.
Tessel [tessel01] version: 0.0.11
On install had one warning:
WARN engine [email protected]: wanted: {"node":"^0.10.3 || ^0.12.0"} (current: {"node":"4.4.2","npm":"2.15.0”})
@jonmckay was helpful but suggested we bring this to your attention.
The text was updated successfully, but these errors were encountered:
While connected to your network, when you run t2 wifi in your command
line, what does that return?
Reports back connected:
t2 wifi
INFO Looking for your Tessel...
INFO Connected to tessel01.
INFO Connected to "Dan's Wi-Fi Network"
INFO Signal Strength: (59/70)
INFO Bitrate: 72mbps
$ t2 list
INFO Searching for nearby Tessels...
tessel01 USB (NO LAN)
Do you know your current network's security settings, i.e. WPA2?
@HipsterBrown
Brand new T2 fails to connect - t2 wifi reports the connection is good. t2 list only reports USB, no LAN (wifi)
It can connect to my network but cannot ping it and cannot ping your host machine from it.
Ran webserver.js sample:
In the browser: I can see the t2 with tesssel01.local:8080, but not via the ip address.
Rooting in, I see that mDNS service fails to reach my network. The service won't start.
Tessel [tessel01] version: 0.0.11
On install had one warning:
WARN engine [email protected]: wanted: {"node":"^0.10.3 || ^0.12.0"} (current: {"node":"4.4.2","npm":"2.15.0”})
@jonmckay was helpful but suggested we bring this to your attention.
The text was updated successfully, but these errors were encountered: