Hi, On Wed, Feb 03, 2010 at 12:53:43PM +0100, Geert Jan de Groot wrote:
If we use 192.168.1.0/24 for the RIPE meeting, and your corporate network at home uses 192.168.1.0/24 as well, most VPN clients will NOT be able to build a working connection. Try it. Given the number of attendees, the chances for address collisions with at least one participant's home network can be assumed to be near 100%.
One workaround would be to have two (vastly different) 1918 prefixes and giving people the possibility to switch (so, 2 SSID's, 2 prefixes, say 192.168.224.0/20 and 10.210.32.0/20). Chances that someone will conflict with both, are small.
For better or worse, we will need to learn how to deal with this -
We're dealing with this every day, outside of RIPE meetings. The RIPE meeting network is not a playground or experimental environment, but is there for the primary purpose that people who attend RIPE meetings can be able to contact their home networks in case something urgently need to be done there. With as little extra pain as possible. Having test networks in addition (!) to that is good. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 144438 SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279