1 |
On 18/08/10 09:04, CJoeB wrote: |
2 |
> On 08/17/10 10:55, Jake Moe wrote: |
3 |
>> On 08/17/10 11:55, Adam Carter wrote: |
4 |
>>>> Hi, |
5 |
>>>> |
6 |
>>>> I'm biting the bullet here and asking for help. Yes! I've posted |
7 |
>>>> before. And before anyone asks, I have read the responses to my |
8 |
>>>> previous posts which helped little. I have read the documentation and |
9 |
>>>> the wikis - ad nauseum. I'm still having problems with wireless. |
10 |
>>>> |
11 |
>>> I use wpa_supplicant to provide the wifi crypto. |
12 |
>>>> So, I'm left with trying to use the iwl3945 driver in the kernel. I |
13 |
>>>> followed the wiki for setting this up and thought I had succeeded. I |
14 |
>>>> got to the point where I was told to type the following: |
15 |
>>>> ifconfig wlan0 up (this does activate the wireless led on my computer) |
16 |
>>>> iwlist wlan0 scan |
17 |
>>>> iwconfig wlan0 essid "network name" (where the network name is the |
18 |
>>>> essid that has been set) |
19 |
>>>> |
20 |
>>>> When I got this to work, I thought I was home free despite the "kludgy" |
21 |
>>>> way of getting wireless working. However, I rebooted and now, when I |
22 |
>>>> type iwlist wlan0 scan I get told that scanning is not supported. Yes, |
23 |
>>>> I have iwl3945-ucode installed and yes, it was recompiled after the |
24 |
>>>> kernel was rebuilt. |
25 |
>>>> |
26 |
>>>> I have no idea what I'm doing wrong. |
27 |
>>> Forgetting to post up your configs :) eg /etc/conf.d/net etc |
28 |
>> I've used the iwl3945 on a few HP laptops without much problem. The few |
29 |
>> problems I had were related to switching the wireless on and off; I'd |
30 |
>> have to rmmod and modprobe kernel modules to get it working again. |
31 |
>> |
32 |
>> Does "ifconfig" list the interface? If not, what does "ifconfig wlan0 |
33 |
>> up" do? What about the output of "iwconfig"? And going for the obvious |
34 |
>> here, any chance that the wireless is turned off? |
35 |
>> |
36 |
>> Jake Moe |
37 |
>> |
38 |
>> |
39 |
> iwconfig lists the interface as wlan0 |
40 |
> |
41 |
> I discovered last night after sending my original message that my |
42 |
> symlink was wrong - I used to have net.eth0 and net.eth1 pointing to |
43 |
> net.lo. However, last night I removed the net.eth1 symlink and created |
44 |
> the net.wlan0 symlink to net.lo. Now when I boot the computer, my |
45 |
> wireless comes up and the LED comes on, but then it times out because (I |
46 |
> assume) it can't establish a connection. |
47 |
> |
48 |
> This is my /etc/conf.d/net file. Note that the "any" used to work when |
49 |
> I used the ipw3945 driver. I would scan for available networks. I |
50 |
> tried last night to change the "any" to the essid printed on my Bell |
51 |
> router, but that didn't work. |
52 |
> |
53 |
> |
54 |
> # This blank configuration will automatically use DHCP for any net.* |
55 |
> # scripts in /etc/init.d. To create a more complete configuration, |
56 |
> # please review /etc/conf.d/net.example and save your configuration |
57 |
> # in /etc/conf.d/net (this file :]!). |
58 |
> |
59 |
> #preup() { |
60 |
> # if [[ ${IFACE} = "wlan0" ]]; then |
61 |
> # sleep 3 |
62 |
> # fi |
63 |
> # return 0 |
64 |
> #} |
65 |
> |
66 |
> modules=( "iwconfig" ) |
67 |
> iwconfig_wlan0="mode managed" |
68 |
> config_eth0=("dhcp") |
69 |
> config_wlan0=("dhcp") |
70 |
> wpa_timeout_wlan0=15 |
71 |
> essid_wlan0="any" |
72 |
> |
73 |
> Regards, |
74 |
> |
75 |
> Colleen |
76 |
This is the wireless part of mine: |
77 |
|
78 |
modules=( "iwconfig" ) |
79 |
config_wlan0=( "noop" "dhcp" ) |
80 |
dhcpcd_wlan0=( "-d -t 15" ) |
81 |
associate_order=( "forcepreferredonly" ) |
82 |
associate_timeout=( "5" ) |
83 |
preferred_aps=( "firstessid" "secondessid" ) |
84 |
key_firstessid=( "THIS-ISMY-KEY1-1234-5678-90AB-CD" ) |
85 |
key_secondessid=( "THIS-ISMY-KEY2-ABCD-EFGH-IJKL-MN" ) |
86 |
|
87 |
|
88 |
I've removed anything not having to do with the wireless for clarity. |
89 |
From memory, the only lines needed are "modules", "config_wlan0", and |
90 |
"preferred_aps" (I have two because I also use wireless at my g/f's |
91 |
mum's house). Oh, and I use "forcepreferredonly" so it'll try to |
92 |
connect even though it can't find my essid by scanning (because I've |
93 |
told my router to stop broadcasting the essid of my wireless network), |
94 |
and it'll only try to connect to networks I specifically tell it to, no |
95 |
others. If your essid is hidden as well, you'll probably need to add |
96 |
either "forcepreferredonly" or "forceany" if you want it to auto-connect |
97 |
to any it finds if it can't connect to yours. |
98 |
|
99 |
Reading through the wireless.example file, I came across this: |
100 |
|
101 |
############################################################################## |
102 |
# SETTINGS |
103 |
############################################################################## |
104 |
# Hard code an ESSID to an interface - leave this unset if you wish |
105 |
the driver |
106 |
# to scan for available Access Points |
107 |
# Set to "any" to connect to any ESSID - the driver picks an Access |
108 |
Point |
109 |
# This needs to be done when the driver doesn't support scanning |
110 |
# This may work for drivers that don't support scanning but you need |
111 |
automatic |
112 |
# AP association |
113 |
# I would only set this as a last resort really - use the preferred_aps |
114 |
# setting at the bottom of this file |
115 |
|
116 |
Which is why I used perferred_aps instead of essid_wlan0. Give that a |
117 |
try, perhaps? |
118 |
|
119 |
Jake Moe |