Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 86904 - /etc/init.d/net.ath0 fails to connect to AP (baselayout-1.11.10-r4)
Summary: /etc/init.d/net.ath0 fails to connect to AP (baselayout-1.11.10-r4)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
: 87047 (view as bug list)
Depends on:
Blocks: 66472
  Show dependency tree
 
Reported: 2005-03-27 15:52 UTC by Jason Cooper
Modified: 2005-03-29 14:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Cooper 2005-03-27 15:52:22 UTC
During boot up or when restarting ath0 I get:

 * Starting ath0
 *    Configuring wireless network for ath0
 *    Couldn't find any access points on ath0
 *    Failed to configure wireless for ath0                               [ !! ]

However, when I start it manually, it works fine:

# iwconfig ath0 essid "FakeEssidHere" mode managed channel 6 enc \
0011-2233-4455-6677-8899-AABB-CC

# dhcpcd ath0

# ping google.com
<works fine.>

Reproducible: Always
Steps to Reproduce:
1.See above.
2.
3.

Actual Results:  
See above.

Expected Results:  
connected to the AP.

[root@thermopylae] # emerge info
Portage 2.0.51.19 (default-linux/x86/2004.0, gcc-3.4.3-20050110,
glibc-2.3.4.20050125-r1, 2.6.9-wireless i686)
=================================================================
System uname: 2.6.9-wireless i686 AMD Athlon(tm) XP 2200+
Gentoo Base System version 1.6.10
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Feb 18 2005, 06:41:25)]
dev-lang/python:     2.3.5
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.14
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config
/usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X a52 alsa apm avi bash-completion berkdb bitmap-fonts bonobo cdr crypt
cups curl dga divx4linux dts dv dvd dvdread emboss encode esd fam font-server
foomaticdb fortran freetype gdbm gif gpm gtk gtk2 gtkhtml guile imagemagick
imlib ipv6 java jpeg kde ldap libg++ libwww mad maildir mikmod mjpeg mmx motif
mozilla mp3 mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pda pdflib perl
png python qt quicktime readline scanner sdl slang spell sse ssl tcltk tcpd
theora tiff truetype truetype-fonts type1-fonts usb v4l x xml xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Comment 1 Jason Cooper 2005-03-28 16:20:47 UTC
*** Bug 87047 has been marked as a duplicate of this bug. ***
Comment 2 Roy Marples (RETIRED) gentoo-dev 2005-03-29 03:18:24 UTC
Is your AP broadcasting it's SSID?
Comment 3 Jason Cooper 2005-03-29 03:39:31 UTC
No, my AP is not broadcasting it's ssid.  That seems like a likely suspect, however, I would prefer not to broadcast the ssid if at all possible.
Comment 4 Roy Marples (RETIRED) gentoo-dev 2005-03-29 05:00:31 UTC
OK, you can try mapping the MAC address of the AP (if that is broadcast) - here's the relevant part of the wireless.example file in /etc/conf.d/wireless.example

# Map a MAC address to an ESSID
# This is used when the Access Point is not broadcasting it's ESSID
# WARNING: This will override the ESSID being broadcast due to some
# Access Points sending an ESSID even when they have been configured
# not too!
# Change 001122334455 to the MAC address and ESSID to the ESSID
# it should map to
#mac_essid_001122334455="ESSID"


If that fails, you can always try and "force" a connect
Again, here's the relevant section for you
# You can also say whether we only connect to preferred APs or not
# Values are "any", "preferredonly", "forcepreferred", "forcepreferredonly" and "forceany"
# "any" means it will connect to visible APs in the preferred list and then any
# other available AP
# "preferredonly" means it will only connect to visible APs in the preferred list
# "forcepreferred" means it will forceably connect to APs in order if it does not find
# them in a scan
# "forcepreferredonly" means it forceably connects to the APs in order and does not bother
# to scan
# "forceany" does the same as forcepreferred + connects to any other available AP
# Default is "any"
#associate_order="any"
#associate_order_eth0="any"


If that also fails to work, or is too slow for you, another option is using wpa_supplicant - provided that the AP at least uses WEP it works a treat
Comment 5 Jason Cooper 2005-03-29 14:40:11 UTC
Awesome, that fixed it.  Thanks for input, I'll pass it along to the other guy on gentoo-user who had the same problem.