wifi password phrase



  • I am having difficulty in getting the onion to connect to a wifi network that is protected by a password phrase instead of a password. Has anyone else had problems with this?



  • @Paul-Koene Can you explain what you mean by password phrase? Like how you might need to log in via a browser at a public Wi-Fi hotspot?



  • Hi Paul,

    might be a stupid question, but what's the exact difference? Both sound for me like a password as "password12345". Maybe it's a language problem for me - sorry.
    In fact you could have a look at /etc/config/wireless for the wireless configuration. There you can also set the type of encryption.

    BR
    Frank



  • By a password phrase I mean the WPA key to be multiple words and special characters including spaces. The omega seems to have problems connecting to this. Connecting to a wifi network without these special characters in the WPA key works just fine...


  • administrators

    What method are you using to setup your wifi connection?

    If you're using wifisetup with arguments, you'll need to wrap any ssid's or passwords that include passwords with quotes.

    For example:

    # wifisetup -ssid "my wifi ssid" -password "my wifi password"
    


  • I've connected without any issues to a few wifi networks.



  • @Lazar-Demin I actually used the web interface through the Omega provided app and wifisetup through the menu system. I have now tried your version through the serial console. This gives me a bit more information. It gets to associated and then says deauthenticating with either reason 3=DEAUTH_LEAVING or 1=UNSPECIFIED. @Robert-Gusek Did you join any networks that spaces and specials characters in their WPA key? It can also be that the problem lies in the - character that's in the SSIDs I'm trying to connect to. The network that did work doesn't have that either. It does have spaces in the SSID though. I guess if it works in the SSID it should also work in the WPA key....



  • Hmm, after using the up arrow to retry the wifi command a couple of times it now suddenly does connect... Problem solved I guess...



  • @Paul-Koene Yes, one had spaces, the other had ! and * in the key. Now having said that I realized that both these networks were using WPA2 only.



  • Hi Paul,

    does it also work after a reboot?
    I had a similar problem with my laptop, there it was a problem with the speed (and I guess used frequency). For me there it helped limiting the speed to 54Mbit/s. (How fast is the wlan on the Omega?)

    BR
    Frank



  • Hi Frank,

    I have rebooted it a couple of times and it seems to come up without problems every time.

    Paul



  • Hi Paul,

    ah, that sounds great. :)

    BR
    Frank



  • Hi,

    I should have taken some cups of "STFU"… now I'm getting the problem:

    [   14.240000] cfg80211: Calling CRDA to update world regulatory domain
    [   14.240000] cfg80211: World regulatory domain updated:
    [   14.250000] cfg80211:  DFS Master region: unset
    [   14.250000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [   14.260000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [   14.270000] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [   14.280000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [   14.280000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [   14.290000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    [   14.300000] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [   14.310000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [   14.320000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    […]
    [   14.590000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
    [   14.590000] cfg80211: Calling CRDA for country: US
    [   14.640000] cfg80211: Regulatory domain changed to country: US
    [   14.640000] cfg80211:  DFS Master region: FCC
    [   14.640000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [   14.650000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
    [   14.660000] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
    [   14.670000] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
    [   14.680000] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
    [   14.690000] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
    [   28.880000] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
    [   29.810000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [   31.270000] wlan0: authenticate with 88:03:55:da:21:b2
    [   31.290000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [   31.290000] wlan0: authenticated
    [   31.320000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [   31.320000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=2)
    [   31.330000] wlan0: associated
    [   31.330000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [   32.660000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
    [   55.560000] random: nonblocking pool is initialized
    [   79.980000] wlan0: deauthenticated from 88:03:55:da:21:b2 (Reason: 3=DEAUTH_LEAVING)
    [   80.750000] wlan0: authenticate with 88:03:55:da:21:b2
    [   80.770000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [   80.770000] wlan0: authenticated
    [   80.790000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [   80.800000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=2)
    [   80.800000] wlan0: associated
    [  124.300000] wlan0: deauthenticated from 88:03:55:da:21:b2 (Reason: 3=DEAUTH_LEAVING)
    [  125.080000] wlan0: authenticate with 88:03:55:da:21:b2
    [  125.100000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [  125.100000] wlan0: authenticated
    [  125.120000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [  125.130000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=2)
    [  125.130000] wlan0: associated
    [  164.570000] wlan0: deauthenticated from 88:03:55:da:21:b2 (Reason: 3=DEAUTH_LEAVING)
    [  165.340000] wlan0: authenticate with 88:03:55:da:21:b2
    [  165.360000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [  165.360000] wlan0: authenticated
    [  165.380000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [  165.380000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=2)
    [  165.390000] wlan0: associated
    

    But I'll take care about that tomorrow… it's quite late here, so I wish a good night to everybody!

    BR
    Frank



  • This is really strange, because the wifi is already shown as properly configured as shown in:

    [ 31.330000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 32.660000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
    

    And then it deauthenticates for some reason. Perhaps the router is booting it off?



  • Hello,

    thanks for your reply. I don't think it's a specific problem with my router, but I'll test that later.
    Does the Omega support the 5GHz frequency band? Somehow I have the feeling that that might be part of the problem - but as I said it's just a feeling…

    BR
    Frank



  • @Frank-Neuhaus No, unfortunately the Omega does not support 5GHz. But if it shows that the device is connected, then it should have connected. Most routers that support 5GHz will also create an access point for 2.4GHz.



  • Hi Boken,

    that's true. Mine does so as well, I just asked because my Thinkpad T520 had the same problem and limiting it to 54MBit/s solved the problem.
    In the other thread about this topic you asked the user whether he is able to ping Google or not. For me I can say that that is not possible; here is the output:

    root@Omega-1D30:/etc/config# ip a s dev wlan0 
    6: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 40:a3:6b:c1:1d:31 brd ff:ff:ff:ff:ff:ff
        inet 192.168.3.146/24 brd 192.168.3.255 scope global wlan0
           valid_lft forever preferred_lft forever
        inet6 fe80::42a3:6bff:fec1:1d31/64 scope link 
           valid_lft forever preferred_lft forever
    root@Omega-1D30:/etc/config# ip r s
    default via 192.168.3.1 dev wlan0  proto static  src 192.168.3.150 
    192.168.3.0/24 dev wlan0  proto kernel  scope link  src 192.168.3.150 
    192.168.3.1 dev wlan0  proto static  scope link  src 192.168.3.150 
    192.168.4.0/24 dev wlan0-1  proto kernel  scope link  src 192.168.4.1 
    root@Omega-1D30:/etc/config# iw dev wlan0 station dump
    Station 88:03:55:da:21:b2 (on wlan0)
            inactive time:  3220 ms
            rx bytes:       114057
            rx packets:     768
            tx bytes:       5891
            tx packets:     34
            tx retries:     2
            tx failed:      0
            signal:         -53 [-53] dBm
            signal avg:     -53 [-53] dBm
            tx bitrate:     28.9 MBit/s MCS 3 short GI
            rx bitrate:     1.0 MBit/s
            expected throughput:    18.575Mbps
            authorized:     yes
            authenticated:  yes
            preamble:       long
            WMM/WME:        yes
            MFP:            no
            TDLS peer:      no
    root@Omega-1D30:/etc/config# ping www.google.de
    [44735.130000] wlan0: deauthenticated from 88:03:55:da:21:b2 (Reason: 3=DEAUTH_LEAVING)
    [44735.910000] wlan0: authenticate with 88:03:55:da:21:b2
    [44735.930000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [44735.930000] wlan0: authenticated
    [44735.950000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [44735.950000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=1)
    [44735.960000] wlan0: associated
    ping: bad address 'www.google.de'
    root@Omega-1D30:/etc/config# [44772.380000] wlan0: deauthenticated from 88:03:55:da:21:b2 (Reason: 3=DEAUTH_LEAVING)
    [44773.160000] wlan0: authenticate with 88:03:55:da:21:b2
    [44773.180000] wlan0: send auth to 88:03:55:da:21:b2 (try 1/3)
    [44773.180000] wlan0: authenticated
    [44773.200000] wlan0: associate with 88:03:55:da:21:b2 (try 1/3)
    [44773.200000] wlan0: RX AssocResp from 88:03:55:da:21:b2 (capab=0x411 status=0 aid=1)
    [44773.210000] wlan0: associated
    

    I'm wondering about that because it claims to be connected, has a proper IP assigned, and still no traffic is going through.

    Any help about this is appreciated!

    BR
    Frank



  • @Frank-Neuhaus Very strange! Can you display the output of ifconfig?



  • Hello Boken,

    sure, here it is:

    root@Omega-1D30:/# ifconfig
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:312 errors:0 dropped:0 overruns:0 frame:0
              TX packets:312 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:21888 (21.3 KiB)  TX bytes:21888 (21.3 KiB)
    
    wlan0     Link encap:Ethernet  HWaddr 40:A3:6B:C1:1D:31  
              inet addr:192.168.3.193  Bcast:192.168.3.255  Mask:255.255.255.0
              inet6 addr: fe80::42a3:6bff:fec1:1d31/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:1129 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1277 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:142643 (139.2 KiB)  TX bytes:231079 (225.6 KiB)
    
    wlan0-1   Link encap:Ethernet  HWaddr 42:A3:6B:C1:1D:31  
              inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
              inet6 addr: fe80::40a3:6bff:fec1:1d31/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:6276 (6.1 KiB)
    

    I've rebooted in between, that's why the IP changed.

    BR
    Frank

    EDIT: Changed format.

    EDIT2: Obviouly the IP is continuously changing, I think every time it tries to re-associate. But that's does not exactly explain the broken rules in the first setup - I'll just play around with that now… [EDIT: Must have been a change during getting the example… routes fit to the IPs.]

    EDIT2^n:

    I've just done the following:

    [21:09:59  5.11.2015] [frank@waffeleisen] [/home/frank]
    % sudo iw dev wlan0 scan | grep SSID
            SSID: Schillerstrasse
            SSID: SchnurlosesNetzwerk
            SSID: Funkkiste SGV Blockhaus
            SSID: Funkkiste SGV
            SSID: WLAN-E7B142
    

    No, I did not change the SSID of my Omega. And the Laptop is standing directly next to the Omega.

    P.S.: Connecting to another AP I opened using my mobile (OnePlus One) worked just fine…

    EDIT 2^n +1: Most likely my last edit for today, which now might help other people as well. Hopefully.
    I've just set my router to only support 802.11b/g (so without n!), and it works. Maybe a problem of the router; I'll test that tomorrow when I'm at a place with another 802.11b/g/n network.



  • Hello everybody,

    I've decided to make a new reply.
    Minutes ago I've tested to connect my Omega and my T520 without limitations to the 802.11b/g/n. What shall I say? It just works fine for both devices, so there seems to be some problem with my router at home.
    Therefor I'd say that this problem is solved.
    Thanks to everybody who helped me!

    BR
    Frank


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.