3 Replies Latest reply on Jan 5, 2016 8:15 AM by Intel_Alvarado

    Wifi connection times out




      I have an Edison with the latest image:


      root@edison:~# configure_edison --version



      Now, I have setup Wifi with configure_edison --wifi and get:


      root@edison:~# wpa_cli status

      Selected interface 'wlan0'













      However, the connection times out on


      Also, the route command times out:


      root@edison:~# route

      Kernel IP routing table

      Destination     Gateway         Genmask         Flags Metric Ref    Use Iface


      Netstat -rn gives:


      root@edison:~# netstat -rn

      Kernel IP routing table

      Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface         UG        0 0          0 usb0   U         0 0          0 usb0   U         0 0          0 wlan0


      But trying to close usb0, delete the usb0 route, etc. to possibly resolve an interface conflict does not work.


      What could I try?



        • 1. Re: Wifi connection times out



          I checked with my Edison and the output of route and netstat –rn is almost the same as yours. As you said, this issue is because of an IP conflict between usb0 and wlan0.

          In my case I have for usb0 and for wlan0. For both interfaces I have the same Gateway and Genmask as yours.

          The easiest way to solve this would be to go to your router and specify the DHCP settings. Set up the router so that it leases IPs from a different IP range.


          Try this and let us know your results.



          • 2. Re: Wifi connection times out

            Indeed, now it works with a different subnet


            wlan0     Link encap:Ethernet  HWaddr fc:c2:de:2f:81:72

                      inet addr:  Bcast:  Mask:

                      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

                      RX packets:157 errors:0 dropped:0 overruns:0 frame:0

                      TX packets:188 errors:0 dropped:0 overruns:0 carrier:0

                      collisions:0 txqueuelen:1000

                      RX bytes:36744 (35.8 KiB)  TX bytes:34554 (33.7 KiB)



            root@edison:~# ping google.com

            PING google.com ( 56 data bytes

            64 bytes from seq=0 ttl=57 time=25.008 ms

            64 bytes from seq=1 ttl=57 time=25.337 ms

            64 bytes from seq=2 ttl=57 time=43.837 ms


            --- google.com ping statistics ---

            3 packets transmitted, 3 packets received, 0% packet loss

            round-trip min/avg/max = 25.008/31.394/43.837 ms

            root@edison:~# route

            Kernel IP routing table

            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

            default         speedport.ip         UG    0      0        0 wlan0

       *        U     0      0        0 usb0

       *        U     0      0        0 wlan0


            But to understand better, would there be another way to create different subnets for usb0 and wlan0 ?

            Also, a bit confusing is that this Edison worked before in my home office router.


            Thanks in any case!

            • 3. Re: Wifi connection times out

              If you are using any interface and you wish it to have a different IP range you can change the interface’s settings with  ifconfig. Depending on the options you use with ifconfig you can either view or edit your interface’s settings. Take a look at 15 Useful "ifconfig" Commands to Configure Network Interface in Linux .


              Now, if you want to have a single interface to be connected to devices that belong to different networks and have it route properly you’d have to create VLANs. A VLAN is a virtual LAN interface. Each VLAN you create will have a different ID and will behave as a different subnetwork. You can see more information on VLANs here https://wiki.archlinux.org/index.php/VLAN .


              Your Edison might have been working properly on your home office router because of the router’s configuration. Your home office router might be configured to lease a different range of IP addresses through DHCP. When you scanned for networks and connected, it received an IP from a different range that didn’t conflict with any other interface.