"netcfg menu" on startup

drum · 2008-08-12 01:52:16

I have the netcfg menu setup and it won't connect at startup but will connect later when I type "netcfg2 wireless" in a terminal.
"wireless" is the name of the profile I set up and it must be Ok as it does connect from a terminal.
Maybe my rc.conf is not set up right?
I attached parts of it below if anyone can please look at it.
Thanks for any advice.

#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid NETGEAR key s:xxxxxxxxxx"  #ascii WEP key

INTERFACES=(eth0 wlan0)

#
NETWORKS=(menu)

DAEMONS=(syslog-ng !network net-profiles @netfs @dbus @hal @fam @dhcdbd @networ$
@alsa @cups @sshd @crond
gdm)

Square · 2008-08-12 02:54:26

You seem to have mixed up a few ways to autostart wireless connections.
Here's some help: http://wiki.archlinux.org/index.php/Netcfg

drum · 2008-08-12 04:00:42

Square, thanks.
Yes you're right I'll sort it out again with the help of the netcfg wiki
cheers

ruscook · 2008-08-12 08:04:35

#NETWORKS=(menu)

I'm not an expert in this (in fact I'm still using the old rc.conf only way of starting my network). But I'd guess changing the above to:

#NETWORKS=(wireless)

If that's what you called your profile.

TjPhysicist · 2008-08-12 08:49:10

My networks array look like yours. But you have to let the daemon for netcfg2 start up, this is what looks at the array and does whatever is neccesary. In you daemons ...) array put in net-profiles, where you wish to finally bring up the menu. Remember the daemon array is executed in order. Also my personal experiance is that an @ in front of the daemon may screw things up, some thing NEED to start before other, not having an @ ensures this. But this is my personal experiance, my computer is not of this world so...

Anyways. Put in net-profiles, and make sure it ONLY starts AFTER any ethernet and/or wireless daemon you have (such as something for the driver etc).

drum · 2008-08-14 01:18:56

Thanks for all your advice guys,
I scapped the netcfg way of wireless on my T61 laptop and went back to the old way of 'wireless_tools' , 'gnome-network-manager' and putting the relevant info for my essid and key for wlan0 into the command line.
I now have the nm-applet come up on startup and then it asks me for a password and it connects perfectly every time.
Arch Forever!
Thanks again

Arch Linux

#1 2008-08-12 01:52:16

"netcfg menu" on startup

#2 2008-08-12 02:54:26

Re: "netcfg menu" on startup

#3 2008-08-12 04:00:42

Re: "netcfg menu" on startup

#4 2008-08-12 08:04:35

Re: "netcfg menu" on startup

#5 2008-08-12 08:49:10

Re: "netcfg menu" on startup

#6 2008-08-14 01:18:56

Re: "netcfg menu" on startup

Board footer