Arch Linux

Maybe helpful. If I call 'netcfg2 profile-name' as root the connection is also established.

what a coincidence, i was about to write that. this morning in order to skip scanning a just ran "netcfg proflie" an it did setup my static ip. the issue appears to be with net-auto-wireless rather than netcfg itself (??)

In your rc.conf I see that you didn't comment out the old settings for the network-daemon. This could interfere with netcfg.

IIRC you should comment out the first 5 lines of your rc.conf and disable the network-daemon.

Also, instead of constantly changing 1 profile, you could easily make a second (static) profile...

Of course I meant to say 'first 5 relevant snippets' you had shown and not the first 5 lines of your rc.conf-file...

i dont see how they would interfere since they are set for eth0 and are actually disabled..

gonna comment them anyway ;)

ok, a few things that can be done.

On a normal boot as you have configured now, when it does not work, have a look in /var/log/daemon.log for any entries, relating to that particular boot, from wpa_actiond and dhcpcd. You can tell they're from the current boot by timestamp. Do this before fixing it with dhcpcd.


Then there's 2 tests:

After boot with the current config, where you do not have a functional connection, please provide the output of
wpa_cli status
netcfg status
pgrep dhcp
This should identify whether netcfg is somehow returning success yet not providing an IP.

Second, test only that profile on boot:
Set:
NETWORKS=(my_profile)
And ensure the only networking related daemon in your rc.conf is 'net-profiles'. Don't background it.
On boot, watch the output carefully and post it exactly - especially if it mentions dhcp at all.
If the network is not functional, run the 3 commands above and post the output.
This should identify whether it's a problem within netcfg and not the auto stuff.

checked daemons.log

only line worth mentioning:
-------
Nov 17 23:14:44 lappy wpa_actiond[2577]: Starting wpa_actiond session for interface 'wlan0'
-------

output of wpa_cli status (run with sudo)
------
Selected interface 'wlan0'
wpa_state=SCANNING
------

both netcfg status and pgrep dhcp dont give any output


second test:
bringing the profile up fails: wireless network not present..

ran the test again, but set the profile to SCAN="no" and it did bring the interface up successfuly including the ip.

i must say, that if i run "/etc/rc.d/net-auto-wireless restart" with scan="yes" in the profile, it brings the connection up successfuly, yet the ip is missing. (a dhclient wlan0 fixes it)

With my home network, I have better results with dhclient than with dhcpcd. Setting DHCLIENT="yes" in your profile will make nefcfg choose dhclient over dhcpcd.

im using a static ip, so this will be of no use :(

Current state of my connection is as follows: During a normal boot, with the radio killswitch turned off (= wireless-card turned on), the dhcp-lease fails. Today I had the radio killswitch turned on (= wireless card turned off) during boot, and when I pushed it after logging in to X, the connection was established instantly.

Here are relevant snippets of rc.conf and of my network profile:

rc.conf
WIRELESS_INTERFACE="wlan0"
DAEMONS=(syslog-ng cpufreq net-rename hal @alsa @net-auto-wireless @mysqld @crond @laptop-mode)

network profile:
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="Funkensprueher_ST"
KEY="some_key"
IP="dhcp"
TIMEOUT=60

Here are the the outputs of the requested commands:
output of wpa_cli status:
Selected interface 'wlan0'
bssid=00:21:27:ff:15:2a
ssid=Funkensprueher_ST
id=1
id_str=steinfurt
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED

output of netcfg status:
(no output)

output of pgrep dhcp:
(no output)

output of dhcpd wlan0:
dhcpcd: version 5.1.3 starting
dhcpcd: wlan0: broadcasting for a lease
dhcpcd: wlan0: offered 192.168.1.100 from 192.168.1.250 `�'
dhcpcd: wlan0: acknowledged 192.168.1.100 from 192.168.1.250 `�'
dhcpcd: wlan0: checking for 192.168.1.100
dhcpcd: wlan0: leased 192.168.1.100 for infinity
dhcpcd: wlan0: MTU set to 576
dhcpcd: forking to background

outout of netcfg status is unchanged after obtaining the lease, but the output of pgrep dhcp is changed to:
4464

I hope that this is helpful.

installed kernel 2.6.32-rc8 and it fixed half the issues.

now during boot, net-auto-wireless authenticates with the AP correctly, but it still fails to setup the ip for the wireless device. (no error provided), it just doesnt do it.

running netcfg profile-name works ok.

same config as above.

restarting net-auto-wireless doesnt fix the issue.

this might be quite noobish of me, but ive been following the net-auto-wireless code and havent found a single line that suggests the ip settings are being set up / parsed.... iphitus, could you highlight this portion of the code please?

in netcfg-wpa_actiond-action, it calls /usr/lib/network/connections/ethernet with the profile name matching the network. 'ethernet' then configures it according to the options.

After it's associated and settled down, could you check your logs for lines like the following:
wpa_actiond[1234]: Interface 'ethX' connected to network 'mynetwork'
wpa_actiond[1234]: Interface 'ethX' reestablished/lost connection to network 'mynetwork'

If all is working fine,
- wpa_supplicant should associate
- wpa_actiond detects this event, and calls netcfg-wpa_actiond-action
- netcfg-wpa_actiond-action configures your IP settings

I'm looking at this. I'll get back to you in a day with a suggestion.

ive followed the codepath with echos and im stuck at /usr/sbin/wpa_actiond which runs with all the options,


additionally: here is what i get rom my logs:
Dec 3 12:18:11 lappy wpa_actiond[13229]: Starting wpa_actiond session for interface 'wlan0'

nothing else.

when running netcfg profile, wpa_actiond is not used, is this correct?

im at a wireless spot which works half the time..

when it works, logs appear as stated above.

when it does not

check this log: the delays show something timeoutish about it:

Dec 4 19:50:01 lappy wpa_actiond[3123]: Terminating wpa_actiond session for interface 'wlan0'
Dec 4 19:50:07 lappy wpa_actiond[3825]: Starting wpa_actiond session for interface 'wlan0'
Dec 4 19:50:19 lappy wpa_actiond[3825]: Terminating wpa_actiond session for interface 'wlan0'
Dec 4 19:50:25 lappy wpa_actiond[3921]: Starting wpa_actiond session for interface 'wlan0'
Dec 4 19:51:38 lappy wpa_actiond[3921]: Terminating wpa_actiond session for interface 'wlan0'
Dec 4 20:12:17 lappy wpa_actiond[4788]: Starting wpa_actiond session for interface 'wlan0'
Dec 4 20:12:44 lappy wpa_actiond[4788]: Terminating wpa_actiond session for interface 'wlan0'
Dec 4 20:12:48 lappy wpa_actiond[4970]: Starting wpa_actiond session for interface 'wlan0'
Dec 4 20:12:48 lappy wpa_actiond[4970]: Interface 'wlan0' connected to network 'marianita'
Dec 4 20:15:04 lappy wpa_actiond[4970]: Interface 'wlan0' lost connection to network 'marianita'
Dec 4 20:15:05 lappy wpa_actiond[4970]: Interface 'wlan0' reestablished connection to network 'marianita'
Dec 4 20:22:21 lappy wpa_actiond[4970]: Interface 'wlan0' lost connection to network 'marianita'
Dec 4 20:22:22 lappy wpa_actiond[4970]: Interface 'wlan0' reestablished connection to network 'marianita'

which delays are you talking about?

Yes, when running a profile, wpa_actiond is not used.

Also could you test, running nothing network related at all on boot, and then /etc/rc.d/net-auto-wireless start after logging in?

well yes. not starting net-auto-wireless during boot (or anything network related) and then starting the daemon in a shell works ok.

ive always had this small annoyance of not having a correct environment during boot. never been able to figure this out. do you know where to look?

ive noticed a custom kernel ive built does not work with wpa_actiond

the current 2.6.32-ARCH one does.. so i guess its safe to close this bug report as invalid. do you know what kernel config might trigger this?

If starting net-auto-wireless after logging in, instead of at boot works, that may indicate that the driver isn't ready when it is started at boot.

I've seen this with some ethernet cards in the past too.

If your driver needs a daemon, eg crda, put that at the start of your DAEMONS and don't background it. try putting net-auto-wireless right at the end of your daemons.

yes, ive seen this happen...

but. when this does happen, a SIOCTRL error (or something like that) appears under dmesg, this is not the case.

anyway, ive moved net-auto-wireless to the bottom of the list. might add a sleep 5 to the beggining of the rc script to help with the issue if it arises again ;)

try 2.5.0 in [testing].

brain0 identified a possible race which may be the cause of this. wpa_supplicant starts up and associates before wpa_actiond is able to connect and so it misses the event. A fix has been applied.

Thank you very much. 2.5.1 fixed the issue for me.