Just to echo Randall here - it seemed especially brutal last night,
when we were all in Salon D. I didn't start Network Stumbler during
the Plenary, but I did earlier in the week, and was seeing as many as
15-20 machines announcing ad-hoc ietf58.
If I hadn't been typing as fast as I could, I
If you'd like to drum for a bit before we get started, I'm planning to
arrive about half an hour early and drum quietly - see you near Salon
D at 7:00 PM...
Spencer
(drumming is a healing thing, in many cultures)
On Thu, 13 Nov 2003, Spencer Dawkins wrote:
(drumming is a healing thing, in many cultures)
Isn't it after the plenary when we'll need the healing?
;-)
--
Pekka Savola You each name yourselves king, yet the
Netcore Oykingdom bleeds.
Systems. Networks.
I'll be happy if we don't have to do it again in mid-plenary!
- Original Message -
From: Pekka Savola [EMAIL PROTECTED]
To: Spencer Dawkins [EMAIL PROTECTED]
Cc: IETF General Discussion Mailing List [EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 8:15 AM
Subject: Re: Hand drumming
I have seen the exact same phenomena this afternoon and evening.
I am starting to get paranoid. Is there a vengeful person out there who
wants us to stop reading mail and listen to the WG meetings? Is there a
bit pattern that someone is broadcasting on purpose that causes this
problem?
It is not
this is partially a product of your driver and it's user-interface...
if you can really truely statically configure your adhesion to managed
network it will work better.
joelja
On Wed, 12 Nov 2003, Cyrus Shaoul wrote:
I have seen the exact same phenomena this afternoon and evening.
I am
Randall Gellens wrote:
I have been consistently unable to maintain a connection
for more than a very few minutes, usually not even lon
enough to establish a VPN tunnel and fetch one message.
The 802.11 coverage comes and goes; the APs seem to
vanish and I see nothing for a while, eventually
Yes, this looks to affect some models of cards and drivers more than other.
Unfortunately, I fell this time in the unlucky category. The same model of card,
driver, and OS that worked perfectly for many in many other similar events, including
the last three or four IETF meetings made my work
Michel Py [EMAIL PROTECTED] writes:
I have had the same issue. Not suggesting the way I solved it is the
right one, it turned out that when I replaced my Linksys 802.11b with
a brand new Motorola 802.11g the problem went away; there is a Radio
Shark on the third floor of City Center that
Joel Jaeggli wrote:
this is partially a product of your driver and it's user-interface...
if you can really truely statically configure your adhesion to managed
network it will work better.
I don't know. I can configure my linux card to be in managed
mode on ssid ietf58, but that seems to mainly
Note that getting 802.11a works even better.
until everybody does, and 'everbody' is twice
as many people as now
Randy Bush writes:
Note that getting 802.11a works even better.
until everybody does, and 'everbody' is twice
as many people as now
I think 802.11a should be able to support more than twice as many
users than 802.11b. At least in the US, the band reserved for 802.11a
has more channels
it turned out that when I replaced my Linksys 802.11b with
a brand new Motorola 802.11g the problem went away; there is a Radio
Shark on the third floor of City Center that sells them for $70.
Similarly, when I put a $70 Linksys WPC54G (directly supported by Mac
OS X 10.2.8) into my Powerbook to
Simon Leinen wrote:
If someone knows which 802.11a PCMCIA card can be made to work reliably
under Linux (with 2.6 kernel!), I'd really like to hear about it...
Atheros released open-source linux drivers for their chips and the
corresponding reference design.
I don't know which cards use the
On Thursday 13 November 2003 14:46, Romascanu, Dan (Dan) wrote:
Yes, this looks to affect some models of cards and drivers more than other.
Unfortunately, I fell this time in the unlucky category. The same model of
card, driver, and OS that worked perfectly for many in many other similar
Brett,
It would be great if you could publish all the issues that came up, how
you fixed them, and a brief overview of what you deployed (at the start
and end) for the event.
Tim
On Thu, Nov 13, 2003 at 06:50:11PM -0500, Brett Thorson wrote:
On Thursday 13 November 2003 14:46, Romascanu, Dan
You can probably find that info at http://personaltelco.net although I'm
not sure you will be able to take advantage of the Prism2 chipset AP fuctions
avialable using 80211b.
Scott
On Thu, 13 Nov 2003, Simon Leinen wrote:
Randy Bush writes:
Note that getting 802.11a works even better.
--On 13. november 2003 21:46 +0200 Romascanu, Dan (Dan)
[EMAIL PROTECTED] wrote:
Yes, this looks to affect some models of cards and drivers more than
other. Unfortunately, I fell this time in the unlucky category. The same
model of card, driver, and OS that worked perfectly for many in many
basic lessons previously learned were not put to use here, e.g., lowering
the radios so wetware limits range and reduces xmtrs bandwidth fight.
randy
Sitting in the Thursday plenary, I note none of the network-to-ad-hoc
flappage that have been plaguing us the past few days.
Did the attackers get bored and go home?
Did the accidental ad-hocers finally get their settings right?
Did someone deploy a good blocking mechanism?
--Paul Hoffman,
In message [EMAIL PROTECTED], Randy Bush writes:
basic lessons previously learned were not put to use here, e.g., lowering
the radios so wetware limits range and reduces xmtrs bandwidth fight.
We also had the new overly helpful operating systems and a variety of
infected machines eating
On Thu, Nov 13, 2003 at 07:57:33PM -0600, Harald Tveit Alvestrand wrote:
so rather than worrying, let's see what we can do to help
if someone - for instance - has EFFECTIVE tools for triangulating and
locating ad-hoc stations, perhaps they can bring them to the next IETF
meeting?
On 13-nov-03, at 16:44, Carsten Bormann wrote:
it turned out that when I replaced my Linksys 802.11b with
a brand new Motorola 802.11g the problem went away; there is a Radio
Shark on the third floor of City Center that sells them for $70.
Similarly, when I put a $70 Linksys WPC54G (directly
-BEGIN PGP SIGNED MESSAGE-
IMC == IMC Paul writes:
IMC Sitting in the Thursday plenary, I note none of the network-to-ad-hoc
IMC flappage that have been plaguing us the past few days.
IMC Did the attackers get bored and go home?
No, you are just sitting in the wrong
I would have agreed with you until I just bounced onto the aodv network
- oh well
Bill
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul
Hoffman / IMC
Sent: Thursday, November 13, 2003 6:23 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE:
On Thu, Nov 13, 2003 at 09:33:30PM -0500, Andrew Partan wrote:
Another suggestion - it would have been real useful if the software
on my laptop could have been told to ignore some APs (or some other
laptops pretending to be APs), or to only listen to this other set
of APs. White/black
We also had the new overly helpful operating systems and a variety of
infected machines eating bandwidth.
How depressing. Does anybody have any good estimate on what % of machines were
infected with one or more of the usual standard-equipment pieces of
bandwidth-sucking malware?
It's sad
These are my preliminary notes from the Plenaries - neither official
nor complete. Please send me corrections and misattributions!
Thanks,
Spencer
Wednesday Night Plenary
* Welcome - Harald and Leslie
Doing different split than usual - report Wednesday, listen Thursday
Attendance - smallest
basic lessons previously learned were not put to use here, e.g., lowering
the radios so wetware limits range and reduces xmtrs bandwidth fight.
Right. Like this really works. This just ensures that the folks in the
middle of the room will get really bad performance. Been there.
the opposite.
If you'd like to drum for a bit before we get started, I'm planning to
arrive about half an hour early and drum quietly - see you near Salon
D at 7:00 PM...
I find myself wondering if drumming could become as much of a tradition
at IETF as Nuclear War...
30 matches
Mail list logo
