Re: Re(4): [67ATTENDEES] IETF 67 Network goes down at 12:00
Simon Leinen <simon@switch.ch> Wed, 15 November 2006 12:20 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkJkr-000117-Qq; Wed, 15 Nov 2006 07:20:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkHS2-0003Dh-2U for 67attendees@ietf.org; Wed, 15 Nov 2006 04:53:02 -0500
Received: from central.switch.ch ([130.59.11.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkHRz-00045B-Oo for 67attendees@ietf.org; Wed, 15 Nov 2006 04:53:02 -0500
Received: from diotima.switch.ch ([130.59.4.87] helo=diotima) by central.switch.ch with esmtp (Exim 3.20 #1) id 1GkHRk-0006Fe-00; Wed, 15 Nov 2006 10:52:44 +0100
From: Simon Leinen <simon@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17754.58219.549424.80270@switch.ch>
Date: Wed, 15 Nov 2006 10:52:43 +0100
To: Markus Stenberg <mstenber@cisco.com>
Subject: Re: Re(4): [67ATTENDEES] IETF 67 Network goes down at 12:00
In-Reply-To: <874pt11p9c.fsf@cisco.com>
References: <EE8D912486CB3B40978DC42135F2BF8C88A733@ma02exchtmp01.Cantata.com> <BADDD6BD-EB92-4893-8C62-718AF5A49CAC@multicasttech.com> <A0927308-C51A-4C31-A395-BEDBDF3CFB86@mit.edu> <20061113134147.GF5131@login.ecs.soton.ac.uk> <20061113221430.453823151@127.0.0.1> <147DAF3B-F6F1-4044-93DA-3A294A93422D@daedelus.com> <20061113231441.1947189493@127.0.0.1> <20061114121911.GE8091@login.ecs.soton.ac.uk> <874pt11p9c.fsf@cisco.com>
X-Mailer: VM 7.18 under Emacs 21.3.3
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z, @ttmwYVO7l`6OXXYR`
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Wed, 15 Nov 2006 07:20:36 -0500
Cc: 67attendees@ietf.org
X-BeenThere: 67attendees@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF 67 Attendess <67attendees.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/67attendees>, <mailto:67attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/67attendees>
List-Post: <mailto:67attendees@ietf.org>
List-Help: <mailto:67attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/67attendees>, <mailto:67attendees-request@ietf.org?subject=subscribe>
Errors-To: 67attendees-bounces@ietf.org
Markus Stenberg writes: > I'm hoping the 11a goes away, if it leads to more b/g coverage > (unlikely, considering they're probably provided by the same access > points, but I live in hope). The problem is not so much that 11a and b/g are provided by the same access points. The problem is more that the ~2.4GHz spectrum available for 11b/g is very limited compared to the ~5GHz spectrum for 11a. This makes it much harder for to come up with a good channel allocation plan for b/g than for a. > Why is that? I have a Japanese 11a/b/g both in my Thinkpad and > Panasonic laptops. Unfortunately, it seems that some moron's been in > charge when the frequency sets for 11a were chosen (or I'm a moron), > as I can't see the 11a networks in IETFs at all. I _suspect_ it is > our good friend region-coding that is acting up - apparently both of > my laptops subscribe to the ZZJ (Japan) frequency set according to > the Intel driver in Linux, and unfortunately I can't change that > while travelling. Shouldn't that be possible, e.g. by flashing the card with different firmware when you change continents? And as someone else said, regulations in Japan seem to have changed anyway, so maybe you can upgrade firmware to the newer Japanese channel set, or the common subset of that and the other regions. -- Simon. _______________________________________________ 67ATTENDEES mailing list 67ATTENDEES@ietf.org https://www1.ietf.org/mailman/listinfo/67attendees
- [67ATTENDEES] IETF 67 Network goes down at 12:00 Jim Martin
- [67ATTENDEES] Re: IETF 67 Network goes down at 12… Tim Chown
- [67ATTENDEES] Re: IETF 67 Network goes down at 12… Brian E Carpenter
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Bernie Hoeneisen
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Burger, Eric
- Re: [67ATTENDEES] Re: IETF 67 Network goes down a… Joerg Ott
- RE: [67ATTENDEES] Re: IETF 67 Network goes down a… Hallam-Baker, Phillip
- Re: [67ATTENDEES] Re: IETF 67 Network goes down a… Krzysztof Rzecki
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Marshall Eubanks
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Steven M. Bellovin
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Ken Raeburn
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Tim Chown
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Bill Fenner
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Tim Chown
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Richard Barnes
- Re(2): [67ATTENDEES] IETF 67 Network goes down at… Peter Lovell
- Re: Re(2): [67ATTENDEES] IETF 67 Network goes dow… Jim Martin
- Re(4): [67ATTENDEES] IETF 67 Network goes down at… Peter Lovell
- Re: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Tim Chown
- Re: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Fred Baker
- Re: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Markus Stenberg
- RE: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Tom Alexander
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… YOSHIFUJI Hideaki / 吉藤英明
- Re(4): [67ATTENDEES] IETF 67 Network goes down at… Tim Thome
- Re: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Simon Leinen
- Re: Re(4): [67ATTENDEES] IETF 67 Network goes dow… Andrew G. Malis
- Re: Re(2): [67ATTENDEES] IETF 67 Network goes dow… Stephen Casner
- Re: [67ATTENDEES] IETF 67 Network goes down at 12… Tim Chown