From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-73049-garchives=archives.gentoo.org@gentoo.org>)
id 1J69i5-0001Ol-Qg
for garchives@archives.gentoo.org; Sat, 22 Dec 2007 19:08:34 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lBMJ7D54026873;
Sat, 22 Dec 2007 19:07:13 GMT
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.184])
by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lBMJ2XmW021290
for <gentoo-user@lists.gentoo.org>; Sat, 22 Dec 2007 19:02:33 GMT
Received: by fk-out-0910.google.com with SMTP id 18so1843347fkq.2
for <gentoo-user@lists.gentoo.org>; Sat, 22 Dec 2007 11:02:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id;
bh=hnQbdV89TAvamz8rFatyZFqGvxM69AaOdNgUmpSKRkI=;
b=d+dyYjEoSnn6rSDpF65OMkZ0MoN86d/WiZbLCB3eQFER8ih3N1TBlIRwCmsXpbNnLO0Z+Fn1sMKsKS8ck52xENYqtJVCMvilcMJTDEdeEPZ1Wf2g7iiGkpWOA/SbYh8jGsHtOPDNfwqzPtPSXFl1s+7/X2Hx0eGwsTL+M9ZwIUM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id;
b=C1u0ZmHvopzuCbs+GbnUIANFUIyGUGALJESkMcU4ETQ/kVIG0+H532HPsKUPiCgv7Th+VwgU3GvLt3LLV/qnVkG+Z6MzuRIABt7yw4E2MWNLd5fJDcSWf+eqecAcEG6s0pQSGRzCMaS1s2aMGs8Xf1co42ZsCdxGXe0mVdtA2Tk=
Received: by 10.78.190.10 with SMTP id n10mr3648665huf.37.1198350152669;
Sat, 22 Dec 2007 11:02:32 -0800 (PST)
Received: from lappy.study ( [213.162.120.196])
by mx.google.com with ESMTPS id g12sm113972nfb.27.2007.12.22.11.02.30
(version=TLSv1/SSLv3 cipher=OTHER);
Sat, 22 Dec 2007 11:02:31 -0800 (PST)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] realtek 8197 wireless card setup
Date: Sat, 22 Dec 2007 19:01:34 +0000
User-Agent: KMail/1.9.7
References: <28254489.1197934001504.JavaMail.root@elwamui-royal.atl.sa.earthlink.net> <20071222163045.8ff3d6b0.hilse@web.de> <200712221220.20261.jcranmer01@earthlink.net>
In-Reply-To: <200712221220.20261.jcranmer01@earthlink.net>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart1752984.RRAY7mGpLk";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200712221901.36397.michaelkintzios@gmail.com>
X-Archives-Salt: de73d679-2560-4535-a417-ba48e2e5702a
X-Archives-Hash: 1a4ef4a767d621de615f7fbbd4c93a72
--nextPart1752984.RRAY7mGpLk
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Saturday 22 December 2007, Jeff Cranmer wrote:
> On Saturday 22 December 2007 10:30:45 am Hans-Werner Hilse wrote:
> > > I think I'm getting closer now.
> > > I removed the driver from the kernel, and installed ndiswrapper.
> > > I got the inf driver from a guy from realtek, and used
> > > ndiswrapper -i drivername.inf to install it.
> > >
> > > Now, when I run
> > > iwlist wlan0 scanning, I can actually see my access point listed, plus
> > > lots of other local wireless networks.
> >
> > That's good. It actually receives.
Yep, you're half way there. The radio communication part of the equation=20
seems to be working.
> > > connecting to it is a different matter, however, as the connection
> > > always appears to time out. I'm using iwconfig to manually set the
> > > ESSID, wep key etc. at the moment, and have tried the trick of setting
> > > the speed manually to 5.5M to avoid timeouts.
> > >
> > > When I try to run dhcpcd wlan0 the first time, I get Error, wlan0:
> > > timed out The second time I try to run it, I get an error because
> > > dhcpcd is already running.
Try to kill it first (dhcpcd -k) and then re-run it. I would run with=20
defaults (re. channel, speed, etc.) and perhaps only add a small delay in=20
your /etc/conf.d/net to allow the device to come up:
sleep_scan_wlan0=3D"1"
> > Try the minimal approach first and configure it manually using
> > ifconfig/route and ping some host on your network (or the AP if it does
> > IP). If that does not work, there's something wrong with the driver, if
> > it does, the culprit is dhcpcd (vram USE flag?).
>
> Just to clarify, how would I ping a host on my network? I only have one
> other PC connected to the router.
You use the LAN IP address of the router/host. I don't know what options=20
Belkin gives you, can you turn on responses to pings (ICMP packet requests)=
=20
both on the router and on the other PC?
> If that is not possible, due to wireless router firewall stealthing (I ha=
ve
> a rather crash-prone Belkin wireless router at the moment), the next
> attempt would presumably be to ping the AP.
> If I have an AP MAC address, 00:15:E9:19:73:F2 (for example), how would I
> ping this?
You could use arping (net-analyzer/arping) - but that assumes that the rout=
er=20
accepts broadcast messages.
> I have checked the dhcpcd install, and the vram USE flag is presently
> unset. Does this flag need to be set?
Well, it may need to be set depending on your router. Certain dhcpcd serve=
r=20
implementations won't play nicely with the latest stable version of the=20
dhcpcd client and you end up getting time outs and no IP address. =20
Re-emerging with vram USE flag set solves this problem. Manually setting u=
p=20
an available/suitable static LAN IP address may also work (e.g. ifconfig=20
wlan0 192.168.0.2).
> > Start with WEP, if that works switch to WPA.
>
> I've given up on WPA for now. If I can get WEP to work, I'll be happy at
> this point, though WPA operation would be the ultimate goal.
> Is ndiswrapper meant to work with the 2.6.23 kernel? I don't want to have
> to step down to an earlier kernel, as that causes problems with changing
> Xorg configurations, but I could go through the pain of this if it were
> strictly necessary.
ndiswrapper works fine with this kernel. I would start with the dhcpcd vra=
m=20
flag to take this time out problem out of the equation and then I would edi=
t=20
the /etc/conf.d/net to set up all necessary parameters instead of having to=
=20
enter everything via iwconfig at the command line. This will also minimise=
=20
the chance of typos at the CLI. Following a process of elimination I would=
=20
start with no encryption whatsoever at the router and if it works I would=20
then gradually add WEP and finally WAP.
PS. Assuming you get ndiswrapper going you can retry the in-kernel driver i=
n=20
future versions as it is likely that more and more devices will be added.
HTH.
=2D-=20
Regards,
Mick
--nextPart1752984.RRAY7mGpLk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQBHbV8Q5Fp0QerLYPcRAgZHAKChDqq9t6H/20lGSqP9rRDnfcYUFQCgldsN
mM+NUjgN6lZiHeQjHjEee9w=
=Mgrf
-----END PGP SIGNATURE-----
--nextPart1752984.RRAY7mGpLk--
--
gentoo-user@gentoo.org mailing list