Open dzeitman opened 8 years ago
HipsterBrown
commented
8 years ago @dzeitman Thanks for making this issue.
A few questions:
t2 wifi in your command line, what does that return?That's a good comment about mdns-js. I'll start researching how that could affect our discovery system.
dzeitman
commented
8 years ago 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)
WPA2 Personal (pks2)
Dan Zeitman
On Mon, Apr 11, 2016 at 2:09 PM, Nick Hehr notifications@github.com wrote:
@dzeitman https://github.com/dzeitman Thanks for making this issue.
A few questions:
- While connected to your network, when you run t2 wifi in your command line, what does that return?
- Do you know your current network's security settings, i.e. WPA2?
That's a good comment about mdns-js. I'll start researching how that could affect our discovery system.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/tessel/openwrt-tessel/issues/54#issuecomment-208561710
@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 mdns-js@0.4.0: 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.