13 Replies Latest reply on May 16, 2016 12:02 PM by Intel_Alvarado

    3 WiFi Issues

    KarlMiller

      I'm a long time programmer, but new to Edison.  I'm having the following problems with it after setting up the WiFi per "Getting Started" directions, any help would be appreciated.

       

      1. If I continuously ping the Edison at 192.168.42.1 (ping/t from Windows 10) it will drop (or delay for 3+ secs) every 10th ping response. The board seems to be in this mode most of the time, but I've found that rebooting Edison will sometimes fix this... WHAT GIVES???
      2. When I connect to the Edison from my Windows 10 laptop, it will not stay up all day -- after some (small) number of hours it drops the connection and I have to reconnect. WHY DOESN'T THE CONNECTION STAY UP FOR MANY HOURS OR DAYS AT A TIME???
      3. I am working on the road and staying at a hotel which requires a webpage login to access the Internet. IS THERE ANYWAY TO GET EDISON PAST THIS WEB PAGE TO SUCCESSFULLY LOGIN TO THE INTERNET???

      Any help would be much appreciated! Thanks!!!

        • 1. Re: 3 WiFi Issues
          Intel_Alvarado

          Hi KarlMiller,

           

          1. Using the ping command once, the 10th response gets a delay or fails to receive a response? I don’t see this behavior on my Edison. Can you post a screenshot of your terminal window showing the ping command and the moment where the ping responses start to fail?
          2. For how long was the Edison connected? The only thing that failed was the Wi-Fi connection or other processes dropped as well? Isn’t this issue related to your router rather than the Edison? Some routers have set specific lease times for certain IP addresses. Make sure the IP address of your Edison is not being terminated because the lease time expired.
          3. If you can connect to the Edison in, for example, your home or your work network, but are failing to connect in a hotel network then the issue is likely with the hotel network. Make sure this network doesn’t have any kind of security enabled or password so you can connect.


          Make sure you’re using the latest image. You can check using configure_edison –version and get 159.devkit as a response.


          Sergio

          • 2. Re: 3 WiFi Issues
            KarlMiller

            I am using the latest image - 280915.

             

            1. Here's a log of this happening - I changed nothing on the Edison or Windows 10 to affect this. I'm in Silicon Valley - If you want me to bring my Edison by to Intel, just let me know!

             

            D:\>ping/t 192.168.42.1

             

            Pinging 192.168.42.1 with 32 bytes of data:

            Reply from 192.168.42.1: bytes=32 time=1485ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=2ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=15ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=21ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=17ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=2ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=16ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=16ms TTL=64

            Request timed out.

            Reply from 192.168.42.1: bytes=32 time=16ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=23ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=13ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=2ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=15ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Request timed out.

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=21ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=15ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=14ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=18ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=17ms TTL=64

            Request timed out.

            Reply from 192.168.42.1: bytes=32 time=14ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=16ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=18ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=15ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=21ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=16ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=20ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=13ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=3777ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=3ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=22ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=23ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=27ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=2ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=14ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=17ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=13ms TTL=64

            Reply from 192.168.42.1: bytes=32 time=19ms TTL=64

            Request timed out.

             

            2. This is a peer to peer connection between my laptop and the Edison. Does the Edison "short lease" my laptop?

             

            3. Nope. What is missing from Intel is an article on how to connect to hotel and other hot spots that have their own web page requiring such information as name, room number, email, usage agreement checkbox, credit card information, etc.  What should have been supplied is the routing commands and how to setup your developer laptop so it uses the ethernet over usb interface as a web proxy.  This would then enable a human to enter all the (nonstandard) information required by a hotel (or wherever) hot spot. I'll write an article on how to do this soon - just so people have it!

            • 3. Re: 3 WiFi Issues
              jcuzella

              Depending on what is actually happening internal to your board... it may be the issue that myself and another user are experiencing in this thread:

               

              https://communities.intel.com/message/376144#376144

               

              Basically the WiFi has been disconnecting & re-connecting and not coming back up with an IP.  Not sure if there's an easy solution yet... but I've gone down the path of troubleshooting the OS services responsible for the above mentioned issue.

              • 4. Re: 3 WiFi Issues
                jcuzella

                So from the looks of the IP address range, the Edison is most likely getting an IP from your laptop's Ad-Hoc AP (I'm not sure if Windows 10 now is able to run a DHCP server for this.. I haven't been using Windows since 7).  If it were using automatic "Zeroconf" addressing, it would be in range 169.254.0.0/16.  So it's probably either using DHCP to the laptop or static addressing (depending on if you configured this or not).

                 

                Interesting idea for being able to connect to hotel and "captive portal" type WiFi hotspots.  I haven't had the misfortune of needing to do so yet, although I do know there are some techniques for either getting around these network games or simply going through the process of using a terminal browser to login to the portal page might work (such as w3m, lynx, etc..)

                 

                A tcpdump might be helpful to see what's going on with your ICMP packets.  If it does turn out to be the issue I mentioned above, connecting to the serial console via USB can at least get you into the Edison to troubleshoot and verify if it is disassociating.

                • 5. Re: 3 WiFi Issues
                  Intel_Alvarado

                  Hi KarlMiller,

                   

                  Were you able to follow jcuzella’s suggestions, do you still need help with this thread? We also wanted to let you know we’ve passed the suggestion to make a document on how to connect to hotspots that have their own web pages.

                   

                  Sergio

                  • 6. Re: 3 WiFi Issues
                    KarlMiller

                    It seems that at this time the only way to access hotel hotspots is using a pc/tablet to answer their unique questions, as no industry standard exists for these. For our product, the only way to do this would be to hook up an additional WiFi module to the Edison using its serial port and then setup the ip routing withing Edison/Linux to route between the two. Another alternative might be to use 2 Edisons and hook them up back-to-back using their serial ports. Regardless, a pc/tablet could hook up to one of the Edison's WiFi interface while the second WiFi interface performs the connection to the hotel hotspot. The pc/tablet could then be used to provide the information needed by the hotel hotspot.  IT IS A SHAME THIS IS THE ONLY SOLUTION AVAILABLE.   Regarding the stability of the Edison WiFi connection, I am frankly VERY DISAPPOINTED with Intel's response. I am simply using a standard Windows 10 and Edison setup.  THIS SHOULD WORK! If I don't get a better response from Intel, I will be forced to evaluate alternative IoT products... Again, I am in Silicon Valley and would be happy to drop by Intel and demonstrate this straightforward problem...

                    • 7. Re: 3 WiFi Issues
                      Intel_Alvarado

                      We are trying to reproduce the behavior you’re observing, but have not been able to. Can you provide more details of your setup such as how are you powering the board, the procedure used to set the P2P connection, any processes/programs running on the board, etc.

                       

                      Sergio

                      • 8. Re: 3 WiFi Issues
                        KarlMiller

                        This is very simple...

                         

                        1. Setup Edison in Access Point Mode per these instructions: IoT - Getting started with Access Point (AP) Mode for the Intel® Edison board | Intel® Developer Zone

                        2. Use a Windows 10 laptop to connect to this Access Point.

                        3. Ping the Edison from the laptop and watch packets drop, per my previous posts.

                        4. Leave the connection up for a few hours and watch it drop, again per my previous posts.

                         

                        There is no additional software running on the Edison or PC. The Edison is being powered via USB.

                         

                        AGAIN, I CAN STOP BY INTEL IN SILICON VALLEY TO DEMONSTRATE THIS PROBLEM.

                         

                        I am convinced that Access Point mode has hardly been tested by Intel, as it not the usual way most customers will run the Edison.

                        However it is supported, and should work!

                         

                        This is entirely unsatisfactory and is forcing us to evaluate competing IoT boards.

                        • 9. Re: 3 WiFi Issues
                          KarlMiller

                          PLEASE ESCALATE THIS TO THE NEXT LEVEL OF SUPPORT - IT IS RIDICULOUS THAT IT IS TAKING A MONTH TO GET TO THE BOTTOM OF THIS VERY SIMPLE ISSUE!!!

                          • 10. Re: 3 WiFi Issues
                            Intel_Alvarado

                            We just sent you a private message. Please check your community’s inbox.

                             

                            Regards

                            Sergio

                            • 11. Re: 3 WiFi Issues
                              H_E_L_P

                              This...

                               

                              I too am seeing this behavior. I have a socket open between my laptop(server) and the Edison(client) using python and I have noticed that on average the total time for a communication is around 10ms as your ping packets show, but also on occasions (every 5 to 30 seconds) the transmission hangs for .1sec up to 3 seconds. Sometimes its really bad and is very frequent. I have tried disabling the power saving of the wifi on the Edison side with no effect (iwconfig wlan0 power off). I have tried changing the settings on windows 10, but windows 10 sucks in this department, especially on my laptop (surface pro 3). However running both server and client scripts on my laptop shows that these delays do not occur, so its narrowed down to the Edison.

                               

                              I have searched the forums/google for solutions and have found that some people get better performance by better powering the Edison or by using an external antenna (not sure if mine can do this btw....).

                               

                              I am using this to control a robot in real time.... so a half second delay is not tolerable. I need control in the 50Hz range. 

                               

                              Have you found a solution with the Edison or have you jumped ship? I'm running out of options here....

                               

                              Anybody have a solution for this? I know others have had this issue or related issues. 

                              • 12. Re: 3 WiFi Issues
                                H_E_L_P

                                Oh, I'm using a shared wifi network, my home wifi, though I have tried an adhoc network I made in windows 10 using an USB network adapter, but I remember it being slow as S!@# so I couldn't even tell if it had the lag issue. Just FYI.

                                • 13. Re: 3 WiFi Issues
                                  Intel_Alvarado

                                  Hi H_E_L_P,

                                   

                                  Please create a new thread. This thread was created several months ago and some information might not be relevant. Be as detailed as possible with the behavior you’re seeing and list the steps you’ve followed so far.

                                   

                                  Sergio