1 |
On Friday 03 October 2014 7:21:58 AM walt wrote: |
2 |
> On 10/02/2014 09:39 PM, J. Roeleveld wrote: |
3 |
> > |
4 |
> > On Thursday, October 02, 2014 10:24:51 PM Alec Ten Harmsel wrote: |
5 |
> >> On 10/02/2014 10:05 PM, walt wrote: |
6 |
> >>> I did some googling and enabled the "appropriate" kernel drivers, then |
7 |
> >>> rebooted and now the output from ifconfig includes this interface: |
8 |
> >>> |
9 |
> >>> wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 |
10 |
> >>> |
11 |
> >>> ether b8:a3:86:99:a8:d8 txqueuelen 1000 (Ethernet) |
12 |
> >>> RX packets 0 bytes 0 (0.0 B) |
13 |
> >>> RX errors 0 dropped 0 overruns 0 frame 0 |
14 |
> >>> TX packets 0 bytes 0 (0.0 B) |
15 |
> >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
16 |
> >>> |
17 |
> >>> My yes-or-no question: does the appearance of "wlan0" imply that |
18 |
> >>> my new kernel drivers are the right ones for this particular D-Link |
19 |
> >>> WiFi adapter? |
20 |
> >> |
21 |
> >> It's certainly a great sign, but it may or may not be enough. I'm by no |
22 |
> >> means an expert, but I believe I have to install some extra firmware |
23 |
> >> (b43-firmware) to use on my laptop as it's not in the kernel (unless I'm |
24 |
> >> clueless with kernel config). Without b43-firmware, the interface shows |
25 |
> >> up and is recognized, but can't be used iirc. |
26 |
> > |
27 |
> > In my experience, when it shows in "ifconfig", it is loaded. |
28 |
> > You might want to check the "dmesg" output to see if it is missing firmware |
29 |
> > somewhere. |
30 |
> > Did you try "dhcpcd wlan0" to see if it gets an IP-address? |
31 |
> |
32 |
> That doesn't work (yet). An error message said that |
33 |
/etc/wpa_supplicant.conf |
34 |
> was missing, so I copied this example from a man page: |
35 |
> |
36 |
> #cat /etc/wpa_supplicant.conf |
37 |
> ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel |
38 |
> |
39 |
> network={ |
40 |
> ssid="myhomewireless" |
41 |
> scan_ssid=1 |
42 |
> key_mgmt=WPA-PSK |
43 |
> psk="mypsk" |
44 |
> } |
45 |
> |
46 |
> #dhcpcd wlan0 |
47 |
> dhcpcd[1415]: version 6.4.7 starting |
48 |
> dhcpcd[1415]: wlan0: adding address fe80::f45c:642e:a392:f47c |
49 |
> dhcpcd[1415]: if_addaddress6: Permission denied |
50 |
> dhcpcd[1423]: wlan0: starting wpa_supplicant |
51 |
> dhcpcd[1415]: wlan0: waiting for carrier |
52 |
> dhcpcd[1415]: timed out |
53 |
> dhcpcd[1415]: allowing 8 seconds for IPv4LL timeout |
54 |
> dhcpcd[1415]: timed out |
55 |
> dhcpcd[1415]: exited |
56 |
> |
57 |
> NetworkManager gets wlan0 working normally, but the problem is the |
58 |
> network doesn't come up until I log in and use the NetworkManager |
59 |
> panel applet to enter the psk manually. Ugh. |
60 |
> |
61 |
> So, the hardware works but I need to configure the network properly. |
62 |
> Anyone have an idea how I can get the connection working automatically |
63 |
> during boot? |
64 |
> |
65 |
> Thanks. |
66 |
> |
67 |
> BTW, this is ifconfig after NetworkManager brings wlan0 up: |
68 |
> |
69 |
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
70 |
> inet 192.168.1.75 netmask 255.255.255.0 broadcast 192.168.1.255 |
71 |
> inet6 fe80::baa3:86ff:fe99:a8d8 prefixlen 64 scopeid 0x20<link> |
72 |
> inet6 2602:306:c4d4:cf40:baa3:86ff:fe99:a8d8 prefixlen 128 scopeid |
73 |
0x0<global> |
74 |
> ether b8:a3:86:99:a8:d8 txqueuelen 1000 (Ethernet) |
75 |
> RX packets 317 bytes 18320 (17.8 KiB) |
76 |
> RX errors 0 dropped 0 overruns 0 frame 0 |
77 |
> TX packets 82 bytes 38743 (37.8 KiB) |
78 |
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
79 |
> |
80 |
> |
81 |
|
82 |
As for NetworkManager, just log in to your DE as root or run kde-nm- |
83 |
connection-editor as root (assuming you're using KDE) and setup the |
84 |
connection, then check "All users may connect to this network" on the general |
85 |
tab of the connection details. It will then connect at boot whenever the |
86 |
network is available (if you enable the NetworkManager service at boot) and it |
87 |
also has the advantage that although the PSK is still stored as plain-text |
88 |
only root has access to it. That's specially useful if your wifi login is also |
89 |
your active directory (or similar) account. |
90 |
|
91 |
It's also nicer for laptops if you connect to multiple networks. My ISP has |
92 |
hotspots all over the city and NM keeps me connected while driving around with |
93 |
barely any (noticeable) disconnects. You can also connect to VPNs just a |
94 |
easily. |
95 |
|
96 |
|
97 |
---------- |
98 |
Fernando Rodriguez |
99 |
frodriguez.developer@×××××××.com |