Custom query (902 matches)

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

I'm trying to use my IETF network credentials (7904620783, ietf) to log into the ietf.1x and ietf-a.1x SSIDs and it is not authenticating.  Should I be using some other login info?  ietf-hotel and ietf-portal are working fine.

--aaron

There's a link at the bottom of: <​http://noc.meeting.ietf.org/wiki/IETF78network/wireless-instructions?version=1>

to 'HelpDesk??' which goes to: <​http://noc.meeting.ietf.org/wiki/HelpDesk>

which fails :( boo... also, linux instructions would be nice, as it's not at all obvious how to setup wireless 1x auth.

Things like:

o select TTLS o select authentication type "mschapv2" o put in userid into 'username' o put in passwd into 'password' o accept the 'there is no CA cert' error/warning

(note that the above isn't working, for me at least)

Is there a copy of the CA cert somewhere to download and accept/insert/use? Are there some basic descriptions that'd fit here instead? (I get that not everyone's using NetworkManager?, but the windows/mac instructions don't fit well with linux semantics)