Rp-pppoe won't connect at boot; LCP timeout

Question

At my college, we all have our own PPP connection to the main server. To start it at boot, I've put the 'adsl' in the daemons array in rc.conf, and this worked for a long time. Then, some time ago, the service failed to start at boot. However, once I've gotten into X, open xterm and type 'pppoe-connect' or '/etc/rc.d/adsl start', it works fine.
Here's the log of when it fails to start up at boot time:
Oct 18 10:22:44 archie PPP generic driver version 2.4.2
Oct 18 10:22:45 archie pppd[3713]: pppd 2.4.4 started by root, uid 0
Oct 18 10:22:45 archie pppd[3713]: Using interface ppp0
Oct 18 10:22:45 archie pppd[3713]: Connect: ppp0 <--> /dev/pts/0
Oct 18 10:23:16 archie pppd[3713]: LCP: timeout sending Config-Requests
Oct 18 10:23:16 archie pppd[3713]: Connection terminated.
Oct 18 10:23:16 archie pppd[3713]: Modem hangup
Oct 18 10:23:20 archie pppd[3713]: Exit
And then, once I do it manually, it works:
Oct 18 10:24:46 archie pppd[4103]: pppd 2.4.4 started by root, uid 0
Oct 18 10:24:46 archie pppd[4103]: Using interface ppp0
Oct 18 10:24:46 archie pppd[4103]: Connect: ppp0 <--> /dev/pts/1
Oct 18 10:24:46 archie pppoe[4104]: PPP session is 25 (0x19)
Oct 18 10:24:47 archie pppd[4103]: EAP: Identity prompt "Name"
Oct 18 10:24:47 archie pppd[4103]: EAP authentication succeeded
Oct 18 10:24:47 archie PPP BSD Compression module registered
Oct 18 10:24:47 archie pppd[4103]: local  IP address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: remote IP address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: primary   DNS address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: secondary DNS address xxx.xxx.xxx.xxx
Here's my rc.conf:
lo="lo 127.0.0.1"
eth1="eth1 10.0.0.1"
eth0="eth0 000.000.00.0"
INTERFACES=(lo eth0 eth1)
gateway="default gw 10.0.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng network @hal @cups @alsa adsl)
...and my pppoe.conf:
# Ethernet card connected to DSL modem
ETH='eth0'
# PPPoE user name.  You may have to supply "@provider.com"  Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication.  Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use [email protected]
USER='room20'
# Bring link up on demand?  Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300
# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER
# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS.  Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes
DNS1=
DNS2=
# Make the PPPoE connection your default route.  Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes
### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT
# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong.  If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up.  Time is in seconds.
# WARNING WARNING WARNING:
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0.  This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called.  Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30
# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2
# Specific desired AC Name
ACNAME=
# Specific desired service name
SERVICENAME=
# Character to echo at each poll.  Use PING="" if you don't want
# anything echoed
PING=".
# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
#   $PIDFILE       contains PID of pppoe-connect script
#   $PIDFILE.pppoe contains PID of pppoe process
#   $PIDFILE.pppd  contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"
# Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much
# easier on CPU usage, but may not work for you.  It is safer to use
# "no", but you may want to experiment with "yes".  "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no
# Do you want to clamp the MSS?  Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
#   "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
#   The setting of 1412 is safe for either setup, but uses slightly more
#   CPU power.
CLAMPMSS=1412
#CLAMPMSS=no
# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3
# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80
# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE
# Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=
# Any extra arguments to pass to pppoe.  Normally, use a blank string
# like this:
PPPOE_EXTRA=""
# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"
# Any extra arguments to pass to pppd.  Normally, use a blank string
# like this:
PPPD_EXTRA=""
########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"
# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no

Answer 1

That's what I have in mine - it may not be necessary, the wiki is ambiguous on the point. It's certainly necessary if using "net-profiles" but may or may not be for net-auto-wireless. I've always added them just in case (it hasn't stopped it working).
However, you *will* need wpa_actiond installed for net-auto-wireless, if you haven't.
The other thing is, as the wiki says:
Note that wpa-config profiles does not work with net-auto-wireless. Convert them to wpa-configsection instead.
So you will probably need to switch your config profile to a configsection one (again, that's what I use and have no issue automatically connecting to any profile networks).