unable to configure W-LAN Adapter(Sinus 154 data II + Ubuntu)
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
unable to configure W-LAN Adapter(Sinus 154 data II + Ubuntu)
Hello everyone
I upgraded my ubuntu to the new version, but now my W-LAN doesn't work anymore
If i want to configurate my WLAN-Adapter it asks every 30s for the Encription key. I runned out of ideas what i can do to get this working, so I'm posting here.
I tried to configure it manually, but didn't work.
I reinstalled the driver with ndiswrapper, didn't help.
Another problem is that I cannot change the encription of the Router, atm i'm using WPA.
My W-lan adapter is called T-Com Sinus 154 data II, afaik it is build by Siemens.
I hope i didn't forget anything important, so maybe you can help me
Oh and btw I'm still a Linux Newb, so i cannot promise that i will understand everything what you say
Hey could you give some more info, especially what does your system say about it...
In terminal window: sudo tail -f /var/log/syslog
This would show you system log. Now try to connect (via NetworkManager applet?) and collect the messages regarding your connection. Post them. Keep your fingers crossed someone can figure that out.
ok here is the log, at first i tried using the "normal" config (i hope you know what i mean):
sudo tail -f /var/log/syslog
May 2 11:43:04 baumi NetworkManager: <info> wlan0: driver does not support SSID scans (scan_capa 0x00).
May 2 11:43:04 baumi NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 2 11:43:04 baumi NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 2 11:43:04 baumi NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'.
May 2 11:43:04 baumi NetworkManager: <info> Deactivating device wlan0.
May 2 11:43:04 baumi avahi-daemon[5113]: Withdrawing address record for 192.168.2.110 on wlan0.
May 2 11:43:04 baumi avahi-daemon[5113]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.110.
May 2 11:43:04 baumi avahi-daemon[5113]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 2 11:43:04 baumi NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
May 2 11:43:04 baumi NetworkManager: <info> Device list recreated successfully.
May 2 11:44:23 baumi dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
May 2 11:44:23 baumi NetworkManager: <debug> [1209721463.356131] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'B@vm9Art3!'
May 2 11:44:23 baumi NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / B@vm9Art3!
May 2 11:44:23 baumi NetworkManager: <info> Deactivating device wlan0.
May 2 11:44:23 baumi NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
May 2 11:44:23 baumi NetworkManager: <info> Device wlan0 activation scheduled...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) started...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0/wireless): access point 'B@vm9Art3!' is encrypted, but NO valid key exists. New key needed.
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'B@vm9Art3!'.
May 2 11:44:23 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) New wireless user key for network 'B@vm9Art3!' received.
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 2 11:45:06 baumi NetworkManager: <info> Activation (wlan0/wireless): access point 'B@vm9Art3!' is encrypted, and a key exists. No new key needed.
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was '0'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 4240766d394172743321'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
May 2 11:45:08 baumi NetworkManager: <info> SUP: response was 'OK'
May 2 11:45:08 baumi NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 2 11:45:12 baumi kernel: [ 1045.752548] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 2 11:45:14 baumi avahi-daemon[5113]: Registering new address record for fe80::230:f1ff:fef6:e12b on wlan0.*.
May 2 11:45:22 baumi NetworkManager: <info> Supplicant state changed: 0 May 2 11:45:23 baumi kernel: [ 1057.317855] wlan0: no IPv6 routers present
May 2 11:45:37 baumi NetworkManager: <info> Supplicant state changed: 0
May 2 11:45:42 baumi NetworkManager: <info> Activation (wlan0/wireless): disconnected during association, asking for new key.
May 2 11:45:42 baumi NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'B@vm9Art3!'.
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) New wireless user key request for network 'B@vm9Art3!' was canceled.
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failure scheduled...
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failed for access point (B@vm9Art3!)
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failed.
May 2 11:45:46 baumi NetworkManager: <info> Deactivating device wlan0.
May 2 11:45:46 baumi avahi-daemon[5113]: Withdrawing address record for fe80::230:f1ff:fef6:e12b on wlan0.
May 2 11:45:46 baumi NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Manual Config with static IP (I had some issues with DHCP with Windows, so i thought it is maybe the same)
May 2 11:48:29 baumi NetworkManager: <info> /etc/network/interface changed: rebuilding the device list.
May 2 11:48:29 baumi NetworkManager: <info> Removing wired Ethernet (802.3) device 'eth0'.
May 2 11:48:29 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:29 baumi NetworkManager: <info> Removing wireless (802.11) device 'wlan0'.
May 2 11:48:29 baumi NetworkManager: <info> Deactivating device wlan0.
May 2 11:48:29 baumi NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
May 2 11:48:29 baumi NetworkManager: <info> Recreating the device list.
May 2 11:48:29 baumi kernel: [ 1265.885253] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 2 11:48:29 baumi kernel: [ 1265.894411] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 2 11:48:29 baumi NetworkManager: <info> eth0: Device is fully-supported using driver '(null)'.
May 2 11:48:29 baumi NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 2 11:48:29 baumi NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 2 11:48:29 baumi NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
May 2 11:48:29 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:29 baumi NetworkManager: <info> Device list recreated successfully.
May 2 11:48:29 baumi NetworkManager: <info> /etc/network/interface changed: rebuilding the device list.
May 2 11:48:29 baumi NetworkManager: <info> Removing wired Ethernet (802.3) device 'eth0'.
May 2 11:48:29 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:29 baumi NetworkManager: <info> Recreating the device list.
May 2 11:48:29 baumi kernel: [ 1266.142494] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 2 11:48:29 baumi NetworkManager: <info> eth0: Device is fully-supported using driver '(null)'.
May 2 11:48:29 baumi NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 2 11:48:29 baumi NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 2 11:48:29 baumi NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
May 2 11:48:29 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:29 baumi NetworkManager: <info> Device list recreated successfully.
May 2 11:48:29 baumi avahi-daemon[5113]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.110.
May 2 11:48:29 baumi avahi-daemon[5113]: New relevant interface wlan0.IPv4 for mDNS.
May 2 11:48:29 baumi avahi-daemon[5113]: Registering new address record for 192.168.2.110 on wlan0.IPv4.
May 2 11:48:32 baumi NetworkManager: <info> Going to sleep.
May 2 11:48:32 baumi NetworkManager: <info> Waking up from sleep.
May 2 11:48:32 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:32 baumi kernel: [ 577.678584] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 2 11:48:32 baumi NetworkManager: <info> eth0: Device is fully-supported using driver '(null)'.
May 2 11:48:32 baumi NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
May 2 11:48:32 baumi NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
May 2 11:48:32 baumi NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
May 2 11:48:32 baumi NetworkManager: <info> Deactivating device eth0.
May 2 11:48:38 baumi kernel: [ 641.384111] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 2 11:48:40 baumi avahi-daemon[5113]: Registering new address record for fe80::230:f1ff:fef6:e12b on wlan0.*.
daemon[5113]: Registering new address record for fe80::230:f1ff:fef6:e12b on wlan0.*.
May 2 11:45:22 baumi NetworkManager: <info> Supplicant state changed: 0 May 2 11:45:23 baumi kernel: [ 1057.317855] wlan0: no IPv6 routers present
May 2 11:45:37 baumi NetworkManager: <info> Supplicant state changed: 0
May 2 11:45:42 baumi NetworkManager: <info> Activation (wlan0/wireless): disconnected during association, asking for new key.
May 2 11:45:42 baumi NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'B@vm9Art3!'.
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) New wireless user key request for network 'B@vm9Art3!' was canceled.
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failure scheduled...
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failed for access point (B@vm9Art3!)
May 2 11:45:46 baumi NetworkManager: <info> Activation (wlan0) failed. May 2 11:45:46 baumi NetwMay 2 11:48:49 baumi kernel: [ 1297.281818] wlan0: no IPv6 routers present
May 2 11:49:26 baumi ntpdate[7294]: can't find host ntp.ubuntu.com
May 2 11:49:26 baumi ntpdate[7294]: no servers can be used, exiting
Seems like the problem is a missing IPv6 router, but what is that and what can i do against it?
For me that sounds like a problem of the router, but my Windows has no problem to connect to the W-Lan so I'm a little bit confused
The problem is with missing key. Which crypto mechanism are you using? I mean WEP/ WPA/ WPA-PSK? :-)
There is no problem with the IPv6 as you do not need any.
Hmmm it's weird - i mean it seems like you need second key. That's possible of course but it would be required on windows as well. Are you using TKIP or AES. Perhaps try using TKIP if not using it already. Note that your connection process stop BEFORE an attempt to get IP address so there is no difference in using static or dynamic IP - the problem lies elsewhere.
I had similar problem when my AP was set to use channel '13'. I dunno why ubuntu box failed on the same stage your connection process fails. I changed the wireless channel ID to something like 6 and it helped, but don't ask me why... magic? ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.