mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: clemens fischer <ino-news@spotteswoode.dnsalias.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	wlanfae@realtek.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: r8712u: Fix driver to support ad-hoc mode
Date: Sat, 30 Apr 2011 14:21:15 +0200	[thread overview]
Message-ID: <20110430122115.GA3694@spotteswoode.de.eu.org> (raw)
In-Reply-To: <20110430014157.GB3719@spotteswoode.de.eu.org>

> clemens fischer:

> > Jeff Chua:
>
> > On Sat, Apr 30, 2011 at 6:25 AM, clemens fischer
> > <ino-news@spotteswoode.dnsalias.org> wrote:
> > > whereas "r8712u" has only DHCP offers in the logs but no ACKs.
> >
> > Are you saying you're seeing dhcpd being offered in the log? Please
> > post the log from the time your mobile starts up the r8712u.
>
> Presently I cannot reproduce this peculiar situation.  The win-CE
> device provides next to nothing regarding helpful logs, but I know
> that it said "connected" at various occasions without any link being
> active.  Also, it seems DHCP leases are not verified, instead the
> remaining lease time being taken for granted.

Whatever I did late in the past night: sleeping ten hours helped a lot!

I can now confirm that "r8712u" works in Ad-hoc mode using
"wpa_supplicant(8)", it gets its IP from DHCP, connects everywhere and
lets me get spam and all that.

I have a couple of fancy scripts overseeing things, much less intrusive
than network-managers, but I disabled parts of them and did everything
manually.

In the end it may well have been the windows-mobile device hanging on to
its (dead) DHCP lease, but without that mobiles logs I won't know.

I still wish "r8712u" would let me use wireless-tools/iwconfig, but
I can live with "wpa_supplicant(8)".

Thanks for your effort, guys!


regards, clemens

  reply	other threads:[~2011-04-30 12:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 16:25 Larry Finger
2011-04-28 15:08 ` clemens fischer
2011-04-28 15:31   ` Larry Finger
2011-04-28 18:05     ` Jeff Chua
2011-04-28 20:15       ` clemens fischer
2011-04-29  0:36         ` Jeff Chua
2011-04-29 21:15           ` clemens fischer
2011-04-29 21:52             ` Jeff Chua
2011-04-29 22:25               ` clemens fischer
2011-04-29 22:36                 ` Jeff Chua
2011-04-30  1:41                   ` clemens fischer
2011-04-30 12:21                     ` clemens fischer [this message]
2011-04-30 23:08                       ` Jeff Chua
2011-05-01 16:40                         ` clemens fischer
2011-05-01 17:21                           ` Jeff Chua
2011-05-01 19:55                             ` clemens fischer
2011-05-02  5:08                               ` Jeff Chua
2011-04-28 20:54     ` clemens fischer
2011-04-30  0:36     ` clemens fischer
2011-04-30  5:04       ` Larry Finger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110430122115.GA3694@spotteswoode.de.eu.org \
    --to=ino-news@spotteswoode.dnsalias.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@suse.de \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wlanfae@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®