Custom query (984 matches)


Show under each result:

Results (148 - 150 of 984)

Ticket Resolution Summary Owner Reporter
#194 worksforme issue on ietf-a.1x? chelliot@… Robert Kisteleki <robert@…>

Upon arrival (around 11h today), I was unable to connect to the neeting 
network ietf-a.1x. I tired twice, making sure there are no typos. I got back 
a "password incorrect" error. Then I tried the ietf-a-portal network, and it 
accepted me with the same name/password.

Username is random 8 character string, password is "ietf".

I'm using Mac OSX 10.6, works just fine, I have not had this issue on other 
networks yet.

I don't have a problem now as I was able to connect eventually (through the 
portal) but you might want to know this anyway.

#195 pending unable to complete VPN sessions geertj@… Randall Gellens <rg+ietf@…>

Oddly, I have not been able to complete VPN negotiations in the hotel network since early morning today (I was able to do so prior).

I'm not sure we can resolve this. Some background info: The hotel wifi system consists of a bunch of AP's and a "controller" box. The old controller is limited to 80 sessions max, and was literally falling over when IETF-ers started using the network.

What we did was three-fold:

  • Bring more bandwith in (the old hotel network was an ADSL line that we maxed out). The new bandwith is the orange cable
  • Get a bigger controller box that can handle more sessions
  • Clean out the new controller as much as possible, so it can handle the large number of sessions we need. Think "factory default" with minimal changes" and "minimal work for the controller".

What I suspect is happening, is that your VPN client has particular requirements on NAT-ting that are not met with the NAT the controller is now providing. I'm sure I don't need to explain about the difficulties of NAT, IPsec, and sharing IP's: it's not a pretty sight.

The wifi-controller is quite obscure and we spent many, many hours tuesday night to make it do what we need it to do: make the AP's talk, nothing else. There is not a knob to "un-break IPsec" or anything obvious.

So, this isn't a case of flipping a switch, but a case of fiddling with a box that will likely break the whole hotel network, and I'd rather not do that unless we really need to, and only when we have a better understanding of why the netscreenbox is failing, including logs on both ends, etc.

The long and short is that I'm not sure we can fix it before the IETF network dies (21 hours from now). Perhaps you can use the ietf-nh AP if your room faces the MECC, or access the network in the MECC itself?

Otherwise, pls do swing by in room 0.11 and we'll see what can be done, but realistically speaking I'm not hopeful.

I do apologise for breaking something to you but I hope you understand the improvement we made to the NH-IETF community as a whole.


Geert Jan

#196 not broken Fwd: Re: WG Chairs' Beer Evening in Maastreicht llynch@… Henrik Levkowetz <henrik@…>

I'd like to forward to you the WG Chair's beer evening information which
was sent out on the wgchairs list earlier today:



-------- Original Message --------
Subject: Re: WG Chairs' Beer Evening in Maastreicht
Date: Wed, 28 Jul 2010 02:06:58 -0700
From: Stig Venaas <>
To: Jari Arkko <>
CC: WG Chairs <>, Henrik Levkowetz <>

Jari Arkko wrote:
> Wojciech,
>> Sorry for missing a previous mail, but what day/evening has been chosen?
> Traditionally, we do this Wednesday night. IIRC Wednesday was mentioned 
> earlier in the thread, so I'm hoping this is true for this IETF as well. 
> I can make it on Wednesday, at least :-)

I would suggest we do it at the usual time, which I guess is right after
the plenary tonight.

Several of us have now been to

Cafe 't Pothuiske, Het Bat 1,

and it looks like a good place to go. Only issue is that tonight they
seem to only have cold food like sandwiches.

The place is by the west river bank, just a little bit south of where
the social was.

They have been warned that a large crowd is likely to show up tonight.


Note: See TracQuery for help on using queries.