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 (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 > > events, including the last three or four IETF meetings made my work > > impossible this whole week with the wireless setting at this IETF network. > > On this respect this was - for me - by far the worst IETF since I am using > > wireless connectivity. Sorry guys. > > The only thing thing you have to be sorry for is not coming to us sooner. If > you had come to us sooner, we could have been able to solve some of your > problems or fix it all together. > > We hope that by working together to solve these problems we can help you out. > I have heard many comments from many people that this has been a great > wireless IETF. We identified several client problems, and we saw a larger > number of infected machines. If the wireless did suffer (which I don't think > it did because of our volunteer team who worked VERY hard and configuring it) > it was due to problems simply beyond our control. > > And as always, we are happy to take in more volunteers. If there is something > you don't like, hop on board and solve the problems! > > Cheers, and I hope to hear more from you, in realtime next time these issues > pop up. > > --Brett > > > > Dan > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Behalf Of Roland Bless > > > Sent: 13 November, 2003 7:08 PM > > > To: Randall Gellens > > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > > Subject: Re: IETF58 - Network Status > > > > > > > > > Hi Randall, > > > > > > > I have been consistently unable to maintain a connection for more > > > > than a very few minutes, usually not even long 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 the network comes back but only briefly. This has been > > > > > > I can partly confirm your observations, since > > > I often see my driver reporting a signal strength of 0 for seconds. > > > The connection is somehow unstable as my log also reports > > > (NSIS meeting this morning, actually not crowded) > > > Nov 13 10:41:01 kernel: eth1: New link status: AP In Range (0005) > > > Nov 13 10:41:03 kernel: eth1: New link status: AP Changed (0003) > > > Nov 13 10:41:25 kernel: eth1: New link status: AP Out of Range (0004) > > > Nov 13 10:41:26 kernel: eth1: New link status: AP In Range (0005) > > > Nov 13 10:42:58 kernel: eth1: New link status: AP Changed (0003) > > > Nov 13 10:45:18 kernel: eth1: New link status: AP Out of Range (0004) > > > Nov 13 10:45:18 kernel: eth1: New link status: AP In Range (0005) > > > Nov 13 10:45:18 kernel: eth1: New link status: AP Changed (0003) > > > Nov 13 10:45:23 kernel: eth1: New link status: AP Out of Range (0004) > > > Nov 13 10:45:24 kernel: eth1: New link status: AP In Range (0005) > > > Nov 13 10:45:54 kernel: eth1: New link status: AP Changed (0003) > > > Nov 13 10:46:28 kernel: eth1: New link status: AP Out of Range (0004) > > > Nov 13 10:46:28 kernel: eth1: New link status: AP In Range (0005) > > > ... and so on... > > > however, it seems also to depend on the cards firmware and driver, > > > so other people may have no problems at all... > > > Inspite all the problems, it works well enough to get things > > > actually done. > > > > > > > the case in every session I've attended, as well as tonight's > > > > plenary. It doesn't seem to matter if the room is crowded > > > > > > or empty, > > > > > > > or where I sit. > > > > > > > > I have attempted to only select the 'ietf58' network, but often the > > > > network vanishes and there are no networks visible; other times the > > > > only visible "network" is an ad-hoc calling itself 'ietf58'. > > > > > > I wasn't often successful to reattach to APs after my card was > > > "hi-jacked" to ad-hoc cards announcing ietf58. Setting the > > > essid again to the same value seems to do trick, however, > > > often I see signals of strength 0 (maybe the card is confused then..). > > > Furthermore, it happens often that I don't get an IPv6 address > > > directly after activating the card (maybe the RA doesn't get through). > > > > > > Cheers, > > > Roland > > > > _______________________________________________ > > 56crew mailing list > > [EMAIL PROTECTED] > > https://www1.ietf.org/mailman/listinfo/56crew >
