linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	"Ortiz, Samuel" <samuel.ortiz@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: regression: tethering fails in 3.5 with iwlwifi
Date: Tue, 18 Sep 2012 16:20:32 +0300	[thread overview]
Message-ID: <1347974432.7112.61.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1347968754.4283.6.camel@jlt4.sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

On Tue, 2012-09-18 at 13:45 +0200, Johannes Berg wrote:
> On Tue, 2012-09-18 at 10:44 +0200, Johannes Berg wrote:
> 
> > Thanks. I just got that far as well, but I hadn't set up a DHCP
> > server ... I'll debug further, I just confirmed that association still
> > works.
> 
> Ok I can't reproduce the problem. You're going to have to be more
> specific about what connman sets up, I think.
> 
> Here's what I did:
> 
>  * brctl addbr br0
>  * ip addr add ... br0
>  * ip link set br0 up
>  * start dnsmasq on br0
>  * start wpa_supplicant on wlan0, with -Dnl80211 -bbr0 -iwlan0 -c../cfg
>  * brctl addif br0 wlan0
> 
> Maybe this isn't exactly what connman does, but it works for me with
> kernel 3.5.4, a 6230 Intel device and 1.0 wpa_supplicant.
> 
> Can you capture exactly what connman does?

I can with some amount of efforts - I'd need to read the code. If you
would be kind / enthusiastic enough to try this with Tizen images, that
would be a lot easier for me.

But let me CC Samuel who did tethering support for connman. Samuel, if
you wish to provide some input, here is the link to this discussion:

http://thread.gmane.org/gmane.linux.kernel.wireless.general/97389

> Also, are you sure that reverting just the carrier state patch isn't
> sufficient? It seems to me that the carrier state patch might confuse
> the bridge code, but I really see no reason Eric's change should have
> any impact at all.

Yes, 100% sure. I spent a lot of time bisecting this, and found out that
in my setup tethering starts working only if I revert both.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-09-18 13:15 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347361823.26457.3.camel@sauron.fi.intel.com>
     [not found] ` <1DC40B07CD6EC041A66726C271A73AE6195AE9C8@IRSMSX102.ger.corp.intel.com>
2012-09-14 14:02   ` regression: tethering fails in 3.5 with iwlwifi Artem Bityutskiy
2012-09-14 16:39     ` Artem Bityutskiy
2012-09-17 14:41       ` Artem Bityutskiy
2012-09-17 15:15         ` Eric Dumazet
2012-09-17 15:17           ` Johannes Berg
2012-09-18  7:09         ` Johannes Berg
2012-09-18  8:40           ` Artem Bityutskiy
2012-09-18  8:44             ` Johannes Berg
2012-09-18 11:45               ` Johannes Berg
2012-09-18 13:20                 ` Artem Bityutskiy [this message]
2012-09-20 12:06         ` Artem Bityutskiy
2012-09-20 12:35           ` Johannes Berg
2012-09-20 12:40             ` Eric Dumazet
2012-09-20 12:45               ` Eric Dumazet
2012-09-20 12:46                 ` Eric Dumazet
2012-09-20 12:50                   ` Johannes Berg
2012-09-20 12:47                 ` Johannes Berg
2012-09-20 12:48                   ` Eric Dumazet
2012-09-20 12:50                     ` Johannes Berg
2012-09-20 12:51                       ` Eric Dumazet
2012-09-20 12:54                         ` Johannes Berg
2012-09-20 12:51                   ` Johannes Berg
2012-09-20 12:58                 ` Artem Bityutskiy
2012-09-20 13:04                   ` Eric Dumazet
2012-09-20 13:15                     ` Eric Dumazet
2012-09-20 13:22                     ` Artem Bityutskiy
2012-09-20 13:22                       ` Eric Dumazet
2012-09-20 13:39                         ` Artem Bityutskiy
2012-09-20 13:41                           ` Eric Dumazet
2012-09-20 14:25                       ` Eric Dumazet
2012-09-20 14:37                         ` Artem Bityutskiy
2012-09-20 14:56                           ` Eric Dumazet
2012-09-20 15:05                             ` Johannes Berg
2012-09-20 15:18                               ` Eric Dumazet
2012-09-20 15:22                                 ` Johannes Berg
2012-09-20 15:27                                   ` Eric Dumazet
2012-09-20 15:31                                     ` Eric Dumazet
2012-09-20 15:32                                       ` Eric Dumazet
2012-09-20 15:19                               ` Eric Dumazet
2012-09-20 15:26                                 ` Johannes Berg
2012-09-20 15:09                             ` Artem Bityutskiy
2012-09-21 17:24                         ` David Miller
2012-09-20 12:47               ` Johannes Berg
2013-03-21 19:34         ` Johannes Berg
2013-03-21 21:24           ` David Miller
2013-03-22  7:01           ` Artem Bityutskiy
2013-03-23 15:45           ` Luis Henriques

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=1347974432.7112.61.camel@sauron.fi.intel.com \
    --to=artem.bityutskiy@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=samuel.ortiz@intel.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;
as well as URLs for NNTP newsgroup(s).