Custom query (937 matches)

Sitting in the Plenary. SSID ietf works fine--I select it and I have an address and connectivity in 5 seconds. Joining the ietf-NAT64 SSID fails. After 120 seconds, still no address; the WiFi? signal bar looks like it's still searching.

Using OSX 10.11.6.

Hello,

I'm having a trouble connecting to any ietf network from my laptop.  The
ietf-hotel works only in my hotel room, not around the meeting rooms.
Also everything works fine with the same configuration on my phone.

I have Intel Corporation Centrino Advanced-N 6200 (rev 35) wifi module
in my laptop. I remember some poeple with this module (including me) had
the same problem on the Hawaii meeting:

http://www.ietf.org/mail-archive/web/91attendees/current/msg00211.html

Unfortunately, connecting to the 2.4 only network doesn't fix it for me
this time. I will authenticate, usually get both IPv4 and IPv6
configuration, but pinging the default gateway times out.

Regards,

Jan

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.

Cheers,

Geert Jan