[SOLVED] netcfg upgrade, wlan broken

zoryfl · 2010-02-19 17:10:43

Hey guys,

I'm really sorry for bothering you. But I checked the other threads that already have been opened and just don't get the hint that could help me with my problem. Most probably because mine is a pretty basic one..

My old /etc/network.d/home file looked like this:

CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="my_essid"
KEY="my_key"
IFOPTS="192.168.1.24 netmask 255.255.255.0 broadcast 192.168.0.255"
GATEWAY=192.168.1.1
IP="static"
USEWPA="yes"
WPAOPTS="-B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf"
TIMEOUT=20
DNS1=192.168.1.1

So that's the file I have to update to it's wpa-configsection style, right? I just don't have an idea how it is supposed to work if I trim this file down to the format the configsection example has. Could anyone help me out here, please?
This is how I did it for now:

CONNECTION="wireless"
INTERFACE=wlan0
ESSID="my_essid"
IP="static"

CONFIGSECTION='
ssid="my_essid"
key_mgmt=WPA
eap=TTLS
group=TKIP
pairwise=TKIP CCMP
anonymous_identity="anonymous"
password="my_key" (is it correct that "password" is what "KEY" was in the old config file?)
priority=1
phase2="auth=PAP"'

And what about my wpa_supplicant.conf - anything I have to change there?

Again, thanks a lot in advance!
Cheers

Last edited by zoryfl (2010-04-08 08:47:20)

zenlord · 2010-02-19 17:34:20

I see you forget to specify the SECURITY-parameter in your new profile.

See: http://wiki.archlinux.org/index.php/Netcfg and the examples in your /etc/network.d/
OOTOMH i think you need to set SECURITY="wpa-configsection" inside your profile

Then you can safely comment out or delete your profile in /etc/wpa_supplicant.conf

and don't forget to specify your WIRELESS_INTERFACE="" inside your /etc/rc.conf if you want to automatically connect upon boot

Last edited by zenlord (2010-02-19 17:35:26)

skanky · 2010-02-19 17:36:32

The CONFIGSECTION part of the profile needs to be the same as your wpa_supplicant.conf file's profile part.
The CONFIGSECTION settings are as described in man wpa_supplicant.con(5).

This way the wpa_supplicant.conf is no longer used - netcfg builds it one to use the fly from the CONFIGSECTION.

zoryfl · 2010-02-19 18:10:35

Thanks a lot for your quick replies!

@zenlord: I just forgot to type that part in; I had something wrong there, though, so it was good you pointed at it again!
@skanky: Thanks for the explanation!

I am now down to the following (/etc/network.d/home)

CONNECTION="wireless"
INTERFACE=wlan0
SECURITY="wpa-configsection"
ESSID="my_essid"
IP="static"

CONFIGSECTION='
        ssid="my_essid"
        psk="my_key"'

The thing is, I can now establish the connection via "netcfg home" (-> replies "done" without any errors") but if I plug-out my ethernet cable I seem to have no connection even though iwconfig says I'm connected.
After a reboot i manages to glance at something [FAIL] while booting. I added "WIRELESS_INTERFACE=wlan0" to my rc.conf and "net-auto-wireless" to the daemon's list.

DAEMONS=(syslog-ng hal cpufreq mpd net-auto-wireless @network @net-auto netfs @crond kdm)

Cheers again

Last edited by zoryfl (2010-02-19 18:11:24)

zenlord · 2010-02-20 07:14:35

Hello again, and again I'm posting this from my non-Arch-box, so please check my advice

1. I see you don't have quotes around 'wlan0' - it is a good practice to use them. It might cause problems.
2. If you set your profile to use a static ip-address, I thought yo had to add more parameters (the first one I can remember is the ip-address itself, but also the gateway and netmask IIRC)

This might be the reason that you are connected, but that you cannot use the network because you don't have an ip-address for that network.

zoryfl · 2010-02-20 23:23:17

Good evening zenlord,
reading your reply everything suddenly fell in place in my mind. I managed to get the wireless lan working again, thanks for your help!

It's just that it's not working on bootup, yet. Manually (netcfg <profile>) works fine.
As already posted, I inserted the WIRELESS_INTERFACE="wlan0" and the net-auto-wireless daemon.
Any ideas are much appreciated!

Best wishes

Horris · 2010-02-21 14:36:19

I have a question. Before the last version of netcfg I had in /etc/rc.conf

INTERFACES=(wlan0)

Now in the last version is required add

WIRELESS_INTERFACE="wlan0".

Is still necesary INTERFACES=(wlan0) ?

skanky · 2010-02-21 21:22:00

zoryfl wrote:

Good evening zenlord,
reading your reply everything suddenly fell in place in my mind. I managed to get the wireless lan working again, thanks for your help!
It's just that it's not working on bootup, yet. Manually (netcfg <profile>) works fine.
As already posted, I inserted the WIRELESS_INTERFACE="wlan0" and the net-auto-wireless daemon.
Any ideas are much appreciated!
Best wishes

Been away for a couple of days, so just got back to this. You're at the stage where I was at until about two minutes ago. I had

...@net-auto @net-auto-wireless @net-auto-wired...

in my DAEMONS array. When I stopped net-auto from being backgrounded (removed the @) it worked. I did wonder if it needed to be running for the net-auto-wireless to work. However, this resolution is not ideal as it blocks at this point, and so delays boot. As it's a nebook, it'll be a little irritating to wait for that to fail when booting when I'm away from home, so I'm going to try a few other things out (making it earlier in the list and backgrounded, for example).

skanky · 2010-02-22 20:23:24

skanky wrote:

.... However, this resolution is not ideal as it blocks at this point, and so delays boot. As it's a nebook, it'll be a little irritating to wait for that to fail when booting when I'm away from home, so I'm going to try a few other things out (making it earlier in the list and backgrounded, for example).

I haven't tested yet, but I'm thinking that actually the delay at boo is because it is connecting to the network, and if the network isn't present the failure will be quite quick - the wired connection failure is pretty quick. Still it has added a delay to boot that wasn't there before. I can't background the net-profiles daemon, I did try putting it earlier and backgrounded - that is before a couple non-backgrounded daemons but it still fails.

Anyone got tis working with the daemons backgrounded?

skanky · 2010-02-23 13:33:53

skanky wrote:

Anyone got tis working with the daemons backgrounded?

Okay, for the record:

Backgrounding is redundant anyway as it backgrounds itself before attempting to connect.

From: http://bbs.archlinux.org/viewtopic.php?id=91439 post #11

NeoXP · 2010-02-23 18:16:38

I have it backgrounded with no problems, my DAEMONS array:

DAEMONS=(syslog-ng @crond @alsa @net-auto-wireless @bluetooth @netfs @cpufreq @sensors @hddtemp @openntpd

skanky · 2010-02-23 20:18:56

Is that list truncated?
No "net-auto"?

NeoXP · 2010-02-24 19:59:11

skanky wrote:

Is that list truncated?
No "net-auto"?

List is not truncated, indeed no "net-auto".

When I updated to netcfg 2.5.x I followed the wiki, as far as I can remember there was still an instruction to use net-auto but with a remark that it was deprecated. When you look at the wiki now it says nothing about net-auto anymore.

Hope this will solve your problem.

skanky · 2010-02-24 20:59:59

Sorry I meant no net-profiles. I'd removed the net-auto when I upgraded.
Anyway, I'll try that, thanks.

BTW it was the missing ")" that made me check if the list was truncated.

skanky · 2010-02-24 21:12:18

Fixed it. Many thanks.

NeoXP · 2010-02-24 22:24:42

O yeah, I see it now, no the missing ")" is a typo.

Indeed also no "net-profiles". As I understood from the wiki you either have to choose for net-profiles or for net-auto-wireless.

And no thxs, I'm glad your puzzle is solved.

Edit: could you mark the topic as [solved]?

Last edited by NeoXP (2010-02-24 22:25:28)

skanky · 2010-02-25 10:21:44

NeoXP wrote:

Indeed also no "net-profiles". As I understood from the wiki you either have to choose for net-profiles or for net-auto-wireless.

I didn't get that meaning...re-reading it I see it now, but that's after knowing.

NeoXP wrote:

And no thxs, I'm glad your puzzle is solved.

NeoXP wrote:

Edit: could you mark the topic as [solved]?

I can't, unfortunately, it's not my topic.

Arch Linux

#1 2010-02-19 17:10:43

[SOLVED] netcfg upgrade, wlan broken

#2 2010-02-19 17:34:20

Re: [SOLVED] netcfg upgrade, wlan broken

#3 2010-02-19 17:36:32

Re: [SOLVED] netcfg upgrade, wlan broken

#4 2010-02-19 18:10:35

Re: [SOLVED] netcfg upgrade, wlan broken

#5 2010-02-20 07:14:35

Re: [SOLVED] netcfg upgrade, wlan broken

#6 2010-02-20 23:23:17

Re: [SOLVED] netcfg upgrade, wlan broken

#7 2010-02-21 14:36:19

Re: [SOLVED] netcfg upgrade, wlan broken

#8 2010-02-21 21:22:00

Re: [SOLVED] netcfg upgrade, wlan broken

#9 2010-02-22 20:23:24

Re: [SOLVED] netcfg upgrade, wlan broken

#10 2010-02-23 13:33:53

Re: [SOLVED] netcfg upgrade, wlan broken

#11 2010-02-23 18:16:38

Re: [SOLVED] netcfg upgrade, wlan broken

#12 2010-02-23 20:18:56

Re: [SOLVED] netcfg upgrade, wlan broken

#13 2010-02-24 19:59:11

Re: [SOLVED] netcfg upgrade, wlan broken

#14 2010-02-24 20:59:59

Re: [SOLVED] netcfg upgrade, wlan broken

#15 2010-02-24 21:12:18

Re: [SOLVED] netcfg upgrade, wlan broken

#16 2010-02-24 22:24:42

Re: [SOLVED] netcfg upgrade, wlan broken

#17 2010-02-25 10:21:44

Re: [SOLVED] netcfg upgrade, wlan broken

Board footer