[SOLVED]Netcfg works great manually, but when using the daemon it wont

Question

I installed netcfg a really long time ago following the arch wiki. When I first installed it and set everything up, it was all working perfectly.
For the past three or four months Ive been having problems where netcf daemon is failing to connect (home wireless network 256bit wep). It takes about 20 seconds just waiting and eventually says failed. If I log in and run the command manually (sudo netcfg home-wifi) it connect perfectly fine every time.
Ive tried everything I can think of including different QUIRKS and changing permissions on the profiles but nothing works. I also tried using the netcfg menu but it doesnt work like that either. I went over the wiki page again thinking something might have chnaged, but its all the same. I even reinstalled and configured again but still nothing.
heres my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq cpufreq_ondemand vboxdrv loop)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(home-wifi)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng crond hal cpufreq !network net-profiles @netfs @alsa @sensors @mpd)
What gets me is that it actually takes longer to fail then it does when I manually connect. It times out for like 20 seconds, but when I manually connect its almost instantaneous.
Last edited by tjwoosta (2010-03-02 05:31:37)

Answer 1

I had arch installed on my Sony VAIO, had this problem, and then fixed it somehow.  That was several months ago, recently I fried the laptop so I just reinstalled and can't remember.  But now I have a "solution"  haha
this is kind of silly how I got it to work, though.
I created another profile "home-wifi-boot" with a short timeout, this is called from rc.conf.
then I put "/usr/bin/netcfg home-wifi" in my /etc/rc.local  , which is exactly the same but has a 30 sec timeout.
This just does the same thing as I was doing manually, runs netcfg a second time.  It works for me!
Last edited by jamba (2010-02-14 15:30:58)