Electromagnetic Field - User contributions [en]

Network

2014-08-10T22:34:04Z

AK47: /* WPA2 802.1X, encryption */

== Network ==

[[Team:NOC]] has tried to build and support the fastest network for you, a network comparable to a medium sized ISP built up in just a couple of days. It might not be perfect all the time. If you experience any outage please report them to the [[Team:InfoHelpDesk|helpdesk]].

We will be providing a high speed onsite network with blanket wireless coverage and wired network access to both venues and camping tents.

== Uplink ==

Uplink from the campsite is currently being arranged. Details will be announced when firm.

== Wireless ==

The whole field has been covered with many wireless access points to ensure the best possible coverage and to allow you to roam seamlessly without interruption. Naturally, there is additional coverage in popular areas such as the talk tents.

The following SSIDs will be available:

* emfcamp
** This is 5GHz and should you should use this one in preference, if you can see it. The username and password are "emf". This is the most secure, WPA2-Enterprise.
* emfcamp-legacy
** This is 2.4GHz and less resistant to interference, use it only if you have to. The username and password are "emf". This is also WPA2-Enterprise.
* emfcamp-insecure '''Warning: less secure'''
** This is both 5GHz and 2.4GHz, and is for older devices that don't support WPA2-Enterprise. It's basic WPA2-PSK and the password is "emfcamp2014".
* spacenet
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your hackerspace is offering spacenet. More information can be found at [https://spacefed.net/ spacefed.net].
* eduroam
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your university/college/school is offering eduroam. More information can be found at [https://www.eduroam.org/ eduroam.org].

Use of the 5GHz SSIDs is recommended if your device supports them. 802.11b is disabled as it slows everyone else down.

Even if you are using an encrypted network, you should still [[#Encryption|encrypt any sensitive traffic]] sent over the air end-to-end to prevent snooping. Although some SSIDs offer encryption, it is only over-the-air.

We have airtime fairness configured on our wireless controllers, so if you wish to download large files please use a wired connection (there will be plenty about).

For proper wireless support under linux, you should have a kernel newer than 2.6.39.2. There is also a kernel panic with brcmsmac on linux 3.10.3 that can be fixed by downgrading to kernel 3.10.2.

=== WPA2 802.1X, encryption ===
Due to popular demand (and with security in mind) we provide WPA2 802.1X. This will encrypt your traffic, preventing attackers from sniffing your data. Keep in mind that this won't protect you from other network attacks and you should still be aware that you are at a hacker conference! Your link layer should be secure if you do certificate checking (see below).

You might think: "WTF!? Do I need to register a user and password blah, blah". Fortunately not. You can '''use any username/password combination using EAP-TTLS with PAP to login''' (example: "user: fbhfbhiaf pass: bgufwbnkqo" is valid), because we don't care who logs in and who you are. We just want to encrypt your data.

Users which use MSCHAPv2 (like Windows users with default 802.1X supplicant) should use a fixed username and password. You can use "emf/emf" or "guest/guest" as "username/password".

==== Client Settings ====
SSID: emfcamp or emfcamp-legacy
Phase 1: EAP-TTLS or PEAP
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP

CN = radius.emf.camp
CA = GeoTrust Global CA
Fingerprint = 5E:A7:65:99:25:14:46:A4:0A:CD:2D:22:27:C1:1B:70:AA:A0:CC:1F

Make sure '''you check the certificate''' in order to know you are connecting to the correct network (you should check on both the CN and the CA).

== Camping area and workshops ==

All camping areas will be within 60m of a Datenklo (Data Toilet), please bring around 60-70m of CAT5 cable. Unless a sponsor comes forward for it, we will be unable to supply cable on site. We will be budgeting only for the infrastructure requirements and necessary spares to deal with issues.

Lay your own cable neatly from your tent back to the nearest Datenklo, and leave 6m of slack coiled on the floor in front of it. And please lay it so that it can be clearly seen that it needs to be plugged in - or you risk having your cable overlooked. At regular intervals a member of the NOC team will connect it up and enable the port.

If you wish to be removed from a Datenklo again, contact the [[Team:InfoDesk|helpdesk]] directly.

All of our edge ports are at least 10/100, some support PoE (802.3af), plus Auto-MDX.

== Static IPs ==

If you need a static IP on either the wired or wireless network, drop by the [[Team:InfoDesk]]. If you are given a static IP on the wireless, connect to the regular SSID, but instead of using the login emf/emf, use static/static.

== Rules ==

* Be nice and friendly! Do not do to others what you do not wish done to yourself.
* Protect your computer! We cannot be taken responsible or held accountable for any damage your devices might sustain due to security problems, power spikes and other such perils.
* Please do not operate your own WiFi access point, our wireless solution includes 'CleanAir' technology and has rogue access point detection.
* If you are operating anything else in the 2.4GHz spectrum, please clear the frequencies in advance with us.
* Do not attempt to run a DHCP or RA server. You will be found and named and shamed!
* Cabling from your tent to the data toilets must not cross any roads.
* If you are connecting a Nanode / Arduino Ethernet / other microcontroller to the network please make sure it is using a unique MAC address. Many of the code examples for such devices use an identical MAC address and this will cause problems - if you aren't sure contact the [[Team:InfoDesk|helpdesk]].
* If you are connecting a switch, you need to contact the NOC to enable this on your port. You are only allowed one uplink from your switch to our network - do not attempt to connect multiple cables or to multiple DKs!

If you break these rules, we will track you down or triangulate you, but we'd rather spend the time maintaining the smooth operation of the network, so please don't waste our time. And if you think [[Team:NOC]] cannot locate you just because you're wireless - think again. ;-)

== IPv6 ==

Naturally, IPv6 is available throughout the network and should "just work" for you. Team:NOC does not recommend disabling IPv6 if you have problems, instead try to understand the problem you are experiencing and get educated in the new world order. Contact the [[Team:InfoDesk|NOC helpdesk]] if you need help.

== Multicast ==

In 2012 we ran multicast with a feed from the BBC. This worked quite well; you could simply open your media player and browse multicast streams (e.g. in VLC "Local Network -> Network Streams (SAP)"). We'll try to do the same again this year, details will appear here.

== Security ==

=== Recent vulnerabilities ====

: '''WARNING: Bring a recent DHCP Client'''. If your OS uses ISC DHCP dhclient make sure you don't run a vulnerable version. https://www.kb.cert.org/vuls/id/410676

=== Encryption ===

Please treat the network as wide open and full of attackers. Although [[Team:NOC]] themselves will not monitor the network, always assume that Alice flirting with Bob will be spied upon by The Third Party.

Any sensitive information including passwords must therefore be encrypted. Please make sure you don't use any software or web applications that send sensitive data or passwords in the clear.

The following mechanisms should be safe:
* Anything that goes through a VPN
* Any website that uses HTTPS
* Any application that uses SSL
** In the case of email, you need to have SSL enabled for both receiving mail (POP, IMAP) and sending it (SMTP)
* ssh and scp
* Where possible, use One-time passwords. Real tokens work best, many of those should be compatible with open source radius servers. [http://perlmonks.org/?node=967433 Here] is a simple Perl radius server implementation for [http://tools.ietf.org/html/rfc6238 RFC6238] tokens that works with ssh and other stuff on linux.

The following are almost always unsafe:

* FTP with login/password (are almost always sent in the clear)
* Telnet with login/password
* Email if you don't use SSL
* Webmail that doesn't use HTTPS
** Someone could trigger a password reminder and then intercept your email
* Websites that use HTTP (not HTTPS) where you need to fill in a password in the page itself

Possibly unsafe, make sure that you understand what you're doing:

* Websites where you need to fill in a password and your ''browser'' (not the website!) tells you it's going to be sent securely
* Websites that require an account but remember you're logged in
** The password ''may'' be protected but not the content or cookies that automatically log you in
* Any time your browser or other application brings up ''anything'' to do with a certificate
* Anything not protected with SSL: someone could be faking DNS answers to impersonate certain sites

Remember: if you're being stupid someone may feel the need to teach you a security lesson in a not so subtle way! (No, that doesn't mean it's ok to hack people just to see if their security is in order.)

=== Firewall ===

There is no network firewall. We operate an unfiltered network that is wide open to the Internet. There is no NAT, and everybody has a public IP address. This is our definition of "network neutrality" - a network that doesn't do anything whatsoever to your IP connection.

If you are used to feeling secure just because you've been sitting behind a NAT router, think again. You are now wide open to the whole Internet. Ensure your personal firewall is enabled and that you have applied all security updates to your OS and applications.

== FAQ ==

=== Can I bring a server? ===

<strike>Yes, though we would rather these were stored centrally in our NOC. This allows us to provision power easily and you also get the added benefit of connecting directly to our core and having UPS backup. If you intend to bring a server please email noc@emfcamp.org so we can fully understand your requirements prior to the event.</strike>

We have not yet determined whether we will be able to provide colocation space for servers, but we would like to in order to save bandwidth on the extensive site network. If this will be helpful for you, please e-mail noc@emfcamp.org so we can gauge demand.

=== Can I use the 2.4GHz band for non-wifi projects? ===

The following channels are available for adhoc/mesh/other wireless stuff:

* 2.4Ghz: Channel 1
* 5Ghz: Channel 136, 140

We cannot force you to use these channels, but we are trying to build a functional wireless network for the other attendees too. So please, don't do any experiments on other channels.

=== Can I bring an access point? ===

No, this is strictly prohibited! We need all available channels to provide good quality coverage for the rest of the attendees. Please do not be selfish here as you will degrade performance for everyone else, and we WILL track you down.

If you are operating a village (using an EMF-supplied tent) that has poor coverage, we may be able to arrange to put an access point in it during the event to improve coverage. Stop by the NOC and ask.

=== Can I bring a switch? ===

Yes, but for stability purposes all edge ports are limited to 3 MAC addresses at a time. If you want to connect a switch, you need to stop by the NOC and ask us to lift the port-security on your port. If you do this, you need to convince us that you know what you're doing and promise not to do anything that may harm the network - in particular, you must not connect the switch to our network by more than 1 cable (not even to a different DK).

=== My port goes up and down every couple of minutes ===

You have probably tripped port security. Most likely scenario is that you have connected a switch without consulting us (see answer to previous question).

== Team Internet ==

[[User:Jasperw]]
[[User:Will-h]]
[[User:Davidc]]

Network

2014-08-10T22:32:54Z

AK47: /* Wireless */

== Network ==

[[Team:NOC]] has tried to build and support the fastest network for you, a network comparable to a medium sized ISP built up in just a couple of days. It might not be perfect all the time. If you experience any outage please report them to the [[Team:InfoHelpDesk|helpdesk]].

We will be providing a high speed onsite network with blanket wireless coverage and wired network access to both venues and camping tents.

== Uplink ==

Uplink from the campsite is currently being arranged. Details will be announced when firm.

== Wireless ==

The whole field has been covered with many wireless access points to ensure the best possible coverage and to allow you to roam seamlessly without interruption. Naturally, there is additional coverage in popular areas such as the talk tents.

The following SSIDs will be available:

* emfcamp
** This is 5GHz and should you should use this one in preference, if you can see it. The username and password are "emf". This is the most secure, WPA2-Enterprise.
* emfcamp-legacy
** This is 2.4GHz and less resistant to interference, use it only if you have to. The username and password are "emf". This is also WPA2-Enterprise.
* emfcamp-insecure '''Warning: less secure'''
** This is both 5GHz and 2.4GHz, and is for older devices that don't support WPA2-Enterprise. It's basic WPA2-PSK and the password is "emfcamp2014".
* spacenet
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your hackerspace is offering spacenet. More information can be found at [https://spacefed.net/ spacefed.net].
* eduroam
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your university/college/school is offering eduroam. More information can be found at [https://www.eduroam.org/ eduroam.org].

Use of the 5GHz SSIDs is recommended if your device supports them. 802.11b is disabled as it slows everyone else down.

Even if you are using an encrypted network, you should still [[#Encryption|encrypt any sensitive traffic]] sent over the air end-to-end to prevent snooping. Although some SSIDs offer encryption, it is only over-the-air.

We have airtime fairness configured on our wireless controllers, so if you wish to download large files please use a wired connection (there will be plenty about).

For proper wireless support under linux, you should have a kernel newer than 2.6.39.2. There is also a kernel panic with brcmsmac on linux 3.10.3 that can be fixed by downgrading to kernel 3.10.2.

=== WPA2 802.1X, encryption ===
Due to popular demand (and with security in mind) we provide WPA2 802.1X. This will encrypt your traffic, preventing attackers from sniffing your data. Keep in mind that this won't protect you from other network attacks and you should still be aware that you are at a hacker conference! Your link layer should be secure if you do certificate checking (see below).

You might think: "WTF!? Do I need to register a user and password blah, blah". Fortunately not. You can '''use any username/password combination using EAP-TTLS with PAP to login''' (example: "user: fbhfbhiaf pass: bgufwbnkqo" is valid), because we don't care who logs in and who you are. We just want to encrypt your data.

Users which use MSCHAPv2 (like Windows users with default 802.1X supplicant) should use a fixed username and password. You can use "emf/emf" or "guest/guest" as "username/password".

==== Client Settings ====
SSID: emfcamp or emfcamp-legacy
Phase 1: EAP-TTLS or PEAP
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP

CN = radius.emf.camp
CA = GeoTrust Global CA
Fingerprint = 5E:A7:65:99:25:14:46:A4:0A:CD:2D:22:27:C1:1B:70:AA:A0:CC:1F

Make sure '''you check the certificate''' in order to know you are connecting to the correct network (you should check on both the CN and the CA). The certificate that is installed on the RADIUS server is same as for the local spacenet-service, it is signed by StartCom (aka StartSSL) of which the root-certificate should be pre-installed on most devices. Check [https://spacefed.net/wiki/index.php/30c3#Certificate here] to see more information about the certificate that is installed.

== Camping area and workshops ==

All camping areas will be within 60m of a Datenklo (Data Toilet), please bring around 60-70m of CAT5 cable. Unless a sponsor comes forward for it, we will be unable to supply cable on site. We will be budgeting only for the infrastructure requirements and necessary spares to deal with issues.

Lay your own cable neatly from your tent back to the nearest Datenklo, and leave 6m of slack coiled on the floor in front of it. And please lay it so that it can be clearly seen that it needs to be plugged in - or you risk having your cable overlooked. At regular intervals a member of the NOC team will connect it up and enable the port.

If you wish to be removed from a Datenklo again, contact the [[Team:InfoDesk|helpdesk]] directly.

All of our edge ports are at least 10/100, some support PoE (802.3af), plus Auto-MDX.

== Static IPs ==

If you need a static IP on either the wired or wireless network, drop by the [[Team:InfoDesk]]. If you are given a static IP on the wireless, connect to the regular SSID, but instead of using the login emf/emf, use static/static.

== Rules ==

* Be nice and friendly! Do not do to others what you do not wish done to yourself.
* Protect your computer! We cannot be taken responsible or held accountable for any damage your devices might sustain due to security problems, power spikes and other such perils.
* Please do not operate your own WiFi access point, our wireless solution includes 'CleanAir' technology and has rogue access point detection.
* If you are operating anything else in the 2.4GHz spectrum, please clear the frequencies in advance with us.
* Do not attempt to run a DHCP or RA server. You will be found and named and shamed!
* Cabling from your tent to the data toilets must not cross any roads.
* If you are connecting a Nanode / Arduino Ethernet / other microcontroller to the network please make sure it is using a unique MAC address. Many of the code examples for such devices use an identical MAC address and this will cause problems - if you aren't sure contact the [[Team:InfoDesk|helpdesk]].
* If you are connecting a switch, you need to contact the NOC to enable this on your port. You are only allowed one uplink from your switch to our network - do not attempt to connect multiple cables or to multiple DKs!

If you break these rules, we will track you down or triangulate you, but we'd rather spend the time maintaining the smooth operation of the network, so please don't waste our time. And if you think [[Team:NOC]] cannot locate you just because you're wireless - think again. ;-)

== IPv6 ==

Naturally, IPv6 is available throughout the network and should "just work" for you. Team:NOC does not recommend disabling IPv6 if you have problems, instead try to understand the problem you are experiencing and get educated in the new world order. Contact the [[Team:InfoDesk|NOC helpdesk]] if you need help.

== Multicast ==

In 2012 we ran multicast with a feed from the BBC. This worked quite well; you could simply open your media player and browse multicast streams (e.g. in VLC "Local Network -> Network Streams (SAP)"). We'll try to do the same again this year, details will appear here.

== Security ==

=== Recent vulnerabilities ====

: '''WARNING: Bring a recent DHCP Client'''. If your OS uses ISC DHCP dhclient make sure you don't run a vulnerable version. https://www.kb.cert.org/vuls/id/410676

=== Encryption ===

Please treat the network as wide open and full of attackers. Although [[Team:NOC]] themselves will not monitor the network, always assume that Alice flirting with Bob will be spied upon by The Third Party.

Any sensitive information including passwords must therefore be encrypted. Please make sure you don't use any software or web applications that send sensitive data or passwords in the clear.

The following mechanisms should be safe:
* Anything that goes through a VPN
* Any website that uses HTTPS
* Any application that uses SSL
** In the case of email, you need to have SSL enabled for both receiving mail (POP, IMAP) and sending it (SMTP)
* ssh and scp
* Where possible, use One-time passwords. Real tokens work best, many of those should be compatible with open source radius servers. [http://perlmonks.org/?node=967433 Here] is a simple Perl radius server implementation for [http://tools.ietf.org/html/rfc6238 RFC6238] tokens that works with ssh and other stuff on linux.

The following are almost always unsafe:

* FTP with login/password (are almost always sent in the clear)
* Telnet with login/password
* Email if you don't use SSL
* Webmail that doesn't use HTTPS
** Someone could trigger a password reminder and then intercept your email
* Websites that use HTTP (not HTTPS) where you need to fill in a password in the page itself

Possibly unsafe, make sure that you understand what you're doing:

* Websites where you need to fill in a password and your ''browser'' (not the website!) tells you it's going to be sent securely
* Websites that require an account but remember you're logged in
** The password ''may'' be protected but not the content or cookies that automatically log you in
* Any time your browser or other application brings up ''anything'' to do with a certificate
* Anything not protected with SSL: someone could be faking DNS answers to impersonate certain sites

Remember: if you're being stupid someone may feel the need to teach you a security lesson in a not so subtle way! (No, that doesn't mean it's ok to hack people just to see if their security is in order.)

=== Firewall ===

There is no network firewall. We operate an unfiltered network that is wide open to the Internet. There is no NAT, and everybody has a public IP address. This is our definition of "network neutrality" - a network that doesn't do anything whatsoever to your IP connection.

If you are used to feeling secure just because you've been sitting behind a NAT router, think again. You are now wide open to the whole Internet. Ensure your personal firewall is enabled and that you have applied all security updates to your OS and applications.

== FAQ ==

=== Can I bring a server? ===

<strike>Yes, though we would rather these were stored centrally in our NOC. This allows us to provision power easily and you also get the added benefit of connecting directly to our core and having UPS backup. If you intend to bring a server please email noc@emfcamp.org so we can fully understand your requirements prior to the event.</strike>

We have not yet determined whether we will be able to provide colocation space for servers, but we would like to in order to save bandwidth on the extensive site network. If this will be helpful for you, please e-mail noc@emfcamp.org so we can gauge demand.

=== Can I use the 2.4GHz band for non-wifi projects? ===

The following channels are available for adhoc/mesh/other wireless stuff:

* 2.4Ghz: Channel 1
* 5Ghz: Channel 136, 140

We cannot force you to use these channels, but we are trying to build a functional wireless network for the other attendees too. So please, don't do any experiments on other channels.

=== Can I bring an access point? ===

No, this is strictly prohibited! We need all available channels to provide good quality coverage for the rest of the attendees. Please do not be selfish here as you will degrade performance for everyone else, and we WILL track you down.

If you are operating a village (using an EMF-supplied tent) that has poor coverage, we may be able to arrange to put an access point in it during the event to improve coverage. Stop by the NOC and ask.

=== Can I bring a switch? ===

Yes, but for stability purposes all edge ports are limited to 3 MAC addresses at a time. If you want to connect a switch, you need to stop by the NOC and ask us to lift the port-security on your port. If you do this, you need to convince us that you know what you're doing and promise not to do anything that may harm the network - in particular, you must not connect the switch to our network by more than 1 cable (not even to a different DK).

=== My port goes up and down every couple of minutes ===

You have probably tripped port security. Most likely scenario is that you have connected a switch without consulting us (see answer to previous question).

== Team Internet ==

[[User:Jasperw]]
[[User:Will-h]]
[[User:Davidc]]

Network

2014-08-10T19:18:21Z

AK47: /* Wireless */

== Network ==

[[Team:NOC]] has tried to build and support the fastest network for you, a network comparable to a medium sized ISP built up in just a couple of days. It might not be perfect all the time. If you experience any outage please report them to the [[Team:InfoHelpDesk|helpdesk]].

We will be providing a high speed onsite network with blanket wireless coverage and wired network access to both venues and camping tents.

== Uplink ==

Uplink from the campsite is currently being arranged. Details will be announced when firm.

== Wireless ==

The whole field has been covered with many wireless access points to ensure the best possible coverage and to allow you to roam seamlessly without interruption. Naturally, there is additional coverage in popular areas such as the talk tents.

The following SSIDs will be available:

* emfcamp
** This is 5GHz and should you should use this one in preference, if you can see it. The username and password are "emf". This is the most secure, WPA2-Enterprise.
* emfcamp-legacy
** This is 2.4GHz and less resistant to interference, use it only if you have to. The username and password are "emf". This is also WPA2-Enterprise.
* emfcamp-insecure '''Warning: less secure'''
** This is both 5GHz and 2.4GHz, and is for older devices that don't support WPA2-Enterprise. It's basic WPA2-PSK and the password is "emfcamp2014".
* spacenet
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your hackerspace is offering spacenet. More information can be found at [https://spacefed.net/ spacefed.net].
* eduroam
** This is 2.4GHz + 5GHz and WPA2-Enterprise, you can connect with a valid account if your university/college/school is offering eduroam. More information can be found at [https://www.eduroam.org/ eduroam.org].

Use of the 5GHz SSIDs is recommended if your device supports them. 802.11b is disabled as it slows everyone else down.

Even if you are using an encrypted network, you should still [[#Encryption|encrypt any sensitive traffic]] sent over the air end-to-end to prevent snooping. Although some SSIDs offer encryption, it is only over-the-air.

We have airtime fairness configured on our wireless controllers, so if you wish to download large files please use a wired connection (there will be plenty about).

For proper wireless support under linux, you should have a kernel newer than 2.6.39.2. There is also a kernel panic with brcmsmac on linux 3.10.3 that can be fixed by downgrading to kernel 3.10.2.

== Camping area and workshops ==

All camping areas will be within 60m of a Datenklo (Data Toilet), please bring around 60-70m of CAT5 cable. Unless a sponsor comes forward for it, we will be unable to supply cable on site. We will be budgeting only for the infrastructure requirements and necessary spares to deal with issues.

Lay your own cable neatly from your tent back to the nearest Datenklo, and leave 6m of slack coiled on the floor in front of it. And please lay it so that it can be clearly seen that it needs to be plugged in - or you risk having your cable overlooked. At regular intervals a member of the NOC team will connect it up and enable the port.

If you wish to be removed from a Datenklo again, contact the [[Team:InfoDesk|helpdesk]] directly.

All of our edge ports are at least 10/100, some support PoE (802.3af), plus Auto-MDX.

== Static IPs ==

If you need a static IP on either the wired or wireless network, drop by the [[Team:InfoDesk]]. If you are given a static IP on the wireless, connect to the regular SSID, but instead of using the login emf/emf, use static/static.

== Rules ==

* Be nice and friendly! Do not do to others what you do not wish done to yourself.
* Protect your computer! We cannot be taken responsible or held accountable for any damage your devices might sustain due to security problems, power spikes and other such perils.
* Please do not operate your own WiFi access point, our wireless solution includes 'CleanAir' technology and has rogue access point detection.
* If you are operating anything else in the 2.4GHz spectrum, please clear the frequencies in advance with us.
* Do not attempt to run a DHCP or RA server. You will be found and named and shamed!
* Cabling from your tent to the data toilets must not cross any roads.
* If you are connecting a Nanode / Arduino Ethernet / other microcontroller to the network please make sure it is using a unique MAC address. Many of the code examples for such devices use an identical MAC address and this will cause problems - if you aren't sure contact the [[Team:InfoDesk|helpdesk]].
* If you are connecting a switch, you need to contact the NOC to enable this on your port. You are only allowed one uplink from your switch to our network - do not attempt to connect multiple cables or to multiple DKs!

If you break these rules, we will track you down or triangulate you, but we'd rather spend the time maintaining the smooth operation of the network, so please don't waste our time. And if you think [[Team:NOC]] cannot locate you just because you're wireless - think again. ;-)

== IPv6 ==

Naturally, IPv6 is available throughout the network and should "just work" for you. Team:NOC does not recommend disabling IPv6 if you have problems, instead try to understand the problem you are experiencing and get educated in the new world order. Contact the [[Team:InfoDesk|NOC helpdesk]] if you need help.

== Multicast ==

In 2012 we ran multicast with a feed from the BBC. This worked quite well; you could simply open your media player and browse multicast streams (e.g. in VLC "Local Network -> Network Streams (SAP)"). We'll try to do the same again this year, details will appear here.

== Security ==

=== Recent vulnerabilities ====

: '''WARNING: Bring a recent DHCP Client'''. If your OS uses ISC DHCP dhclient make sure you don't run a vulnerable version. https://www.kb.cert.org/vuls/id/410676

=== Encryption ===

Please treat the network as wide open and full of attackers. Although [[Team:NOC]] themselves will not monitor the network, always assume that Alice flirting with Bob will be spied upon by The Third Party.

Any sensitive information including passwords must therefore be encrypted. Please make sure you don't use any software or web applications that send sensitive data or passwords in the clear.

The following mechanisms should be safe:
* Anything that goes through a VPN
* Any website that uses HTTPS
* Any application that uses SSL
** In the case of email, you need to have SSL enabled for both receiving mail (POP, IMAP) and sending it (SMTP)
* ssh and scp
* Where possible, use One-time passwords. Real tokens work best, many of those should be compatible with open source radius servers. [http://perlmonks.org/?node=967433 Here] is a simple Perl radius server implementation for [http://tools.ietf.org/html/rfc6238 RFC6238] tokens that works with ssh and other stuff on linux.

The following are almost always unsafe:

* FTP with login/password (are almost always sent in the clear)
* Telnet with login/password
* Email if you don't use SSL
* Webmail that doesn't use HTTPS
** Someone could trigger a password reminder and then intercept your email
* Websites that use HTTP (not HTTPS) where you need to fill in a password in the page itself

Possibly unsafe, make sure that you understand what you're doing:

* Websites where you need to fill in a password and your ''browser'' (not the website!) tells you it's going to be sent securely
* Websites that require an account but remember you're logged in
** The password ''may'' be protected but not the content or cookies that automatically log you in
* Any time your browser or other application brings up ''anything'' to do with a certificate
* Anything not protected with SSL: someone could be faking DNS answers to impersonate certain sites

Remember: if you're being stupid someone may feel the need to teach you a security lesson in a not so subtle way! (No, that doesn't mean it's ok to hack people just to see if their security is in order.)

=== Firewall ===

There is no network firewall. We operate an unfiltered network that is wide open to the Internet. There is no NAT, and everybody has a public IP address. This is our definition of "network neutrality" - a network that doesn't do anything whatsoever to your IP connection.

If you are used to feeling secure just because you've been sitting behind a NAT router, think again. You are now wide open to the whole Internet. Ensure your personal firewall is enabled and that you have applied all security updates to your OS and applications.

== FAQ ==

=== Can I bring a server? ===

<strike>Yes, though we would rather these were stored centrally in our NOC. This allows us to provision power easily and you also get the added benefit of connecting directly to our core and having UPS backup. If you intend to bring a server please email noc@emfcamp.org so we can fully understand your requirements prior to the event.</strike>

We have not yet determined whether we will be able to provide colocation space for servers, but we would like to in order to save bandwidth on the extensive site network. If this will be helpful for you, please e-mail noc@emfcamp.org so we can gauge demand.

=== Can I use the 2.4GHz band for non-wifi projects? ===

The following channels are available for adhoc/mesh/other wireless stuff:

* 2.4Ghz: Channel 1
* 5Ghz: Channel 136, 140

We cannot force you to use these channels, but we are trying to build a functional wireless network for the other attendees too. So please, don't do any experiments on other channels.

=== Can I bring an access point? ===

No, this is strictly prohibited! We need all available channels to provide good quality coverage for the rest of the attendees. Please do not be selfish here as you will degrade performance for everyone else, and we WILL track you down.

If you are operating a village (using an EMF-supplied tent) that has poor coverage, we may be able to arrange to put an access point in it during the event to improve coverage. Stop by the NOC and ask.

=== Can I bring a switch? ===

Yes, but for stability purposes all edge ports are limited to 3 MAC addresses at a time. If you want to connect a switch, you need to stop by the NOC and ask us to lift the port-security on your port. If you do this, you need to convince us that you know what you're doing and promise not to do anything that may harm the network - in particular, you must not connect the switch to our network by more than 1 cable (not even to a different DK).

=== My port goes up and down every couple of minutes ===

You have probably tripped port security. Most likely scenario is that you have connected a switch without consulting us (see answer to previous question).

== Team Internet ==

[[User:Jasperw]]
[[User:Will-h]]
[[User:Davidc]]

Team:NOC

2014-08-04T17:30:12Z

AK47: /* Arrival time coordination */

{{ Infobox Team
| name = NOC
| desc = Network Operations Centre
| lead =
| email =
| needvolunteers = yes
}}

== About ==
Team:NOC is responsible for the entire network infrastructure at the event. This includes all hardware, cabling, wifi, ethernet, IP and so on.

== Current State ==
Working on the uplink, checking line of sight, developing the camp network, begging equipment.

== Volunteering ==

We don't need a lot of help during the event - by Friday morning, all the work will be done, the network will be up and operating perfectly!

If you'd like to help, we really need help in the set-up and tear-down. Particularly, we need people who are willing to run cables and crimp RJ45 ends on Wednesday and Thursday prior, and remove all the cabling on the Monday after. Other than that, we are good, and we don't need any volunteers during the event.

== Team members ==

{{TeamUserList}}

== Arrival time coordination ==

{| border=1
! Who
! Arriving
! Leaving
! Notes
|-
| [[User:davidc]]
| Mon 25th Evening
| Tues 2nd Morning
| Have a hotel for Monday night for an early start
|-
| [[User:YetiFiasco]]
| Wed 27th Evening
| Mon 1st Evening
| Bringing a campervan, can collect gear/people if its between portsmouth<->emf
|-
| [[User:JasperWallace]]
| Tue 26th Morning
| Tue 2nd at some point
|
|-
| [[User:AK47|AK47]]
| Wed 27th Morning
| Tues 2nd Afternoon
| Can be there earlier if needed.
|-
| [[User:markp]]
| Thu 28th Evening
| Mon 1st PM
| Camping Thu-Mon, will gladly crimp, unspool and respool cables.
(Used to do network cabling in a previous life, will bring tools)
|-
| [[User:Danrl|danrl]]
| Tue 25th
| Mon 1st
| Let's get those fibers into the dirt and run IPv6 on them!
|-
| [[User:Mat]]
| Tue 26th Morning
| Tue 2nd Morning
| Am local. May well visit Bank Holiday Monday :)
|}

User:AK47

2014-08-04T17:29:34Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Village:Slackers On Holiday
|email=arjan@koopen.net
|Arrival=2014/08/27 9:00
|Departure=2014/09/02 15:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:27:45Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Village:Slackers On Holiday
|email=arjan@koopen.net
|Arrival=2014/08/27 18:00
|Departure=2014/09/02 12:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:27:01Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Slackers On Holiday
|email=arjan@koopen.net
|Arrival=2014/08/27 18:00
|Departure=2014/09/02 12:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:26:44Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Hackers On Holiday
|email=arjan@koopen.net
|Arrival=2014/08/27 18:00
|Departure=2014/09/02 12:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:26:35Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Hackers on Holiday
|email=arjan@koopen.net
|Arrival=2014/08/27 18:00
|Departure=2014/09/02 12:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:26:25Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=Hackers on Holiday :-)
|email=arjan@koopen.net
|Arrival=2014/08/27 18:00
|Departure=2014/09/02 12:00
|IRC=AK47
|teams=NOC
}}

User:AK47

2014-08-02T14:24:27Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

{{Attendee
|name=AK47
|village=haha
|email=arjan@koopen.net
|Arrival=2014/08/26 07:00
|Departure=2014/09/03 09:00
|IRC=AK47
|teams=NOC
}}

Team:NOC

2014-06-19T17:20:34Z

AK47:

User:AK47

2014-05-04T14:55:52Z

AK47:

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox
* AK47 @ IRC

User:AK47

2014-05-04T14:55:31Z

AK47: Created page with "* Arjan * Living in Amersfoort, NL * Member of [https://bitlair.nl/ Bitlair] * NOC member for hacker events like CCC, OHM/HAR, HackInTheBox"

* Arjan
* Living in Amersfoort, NL
* Member of [https://bitlair.nl/ Bitlair]
* NOC member for hacker events like CCC, OHM/HAR, HackInTheBox

Volunteers

2014-05-04T14:53:48Z

AK47:

== Don't put your name here unless you really mean it and don't edit other people's words without their permission. ==

{| class="wikitable"

|-
|'''Wiki user'''||'''[[Volunteers/DrivingLicenceCategories|Driving licence categories]]<br/>(if willing to drive)'''||'''I'd like to'''||'''I'm willing to'''


|-
|
[[User:NAB|NAB]]
|
B, BE, C1, C1E, D1, D1E (clean)
|

* Take ownership of caravan/motorhome/trailer-tent section of site (selection of initial location, mark-up, marshalling, liaison re power/potable water/greywater/blackwater etc.)
* Create "I'm shy/alone, please talk to me" type badges
* Offer telephone conference room(s) with SIP, geo and freephone access
* Offer on-site telecoms
|
* Drive minibuses
* Run shop (basic staples)
* Keep loos stocked with toilet roll
* Pretty much anything else



|-
|
[[User:lohapuk|lohapuk]]
|
A,B, B1 (clean)
|
* Help Deploy wireless / wired network (Certs CCNP,RHCE)
* Help Build tents / camp
|
* Anything to help out



|-
|
[[User:Sling|Sling]]
|
B (but Dutch)
|
* Help with info/noc helpdesk
* Buildup and teardown
* Sysadmin
* Wiki maintaining & structuring
|
* Parking/Security
* Barshifts
* Help with cooking
* Probably more stuff I'm forgetting.



|-
|
[[User:Dpslwk|'RepRap' Matt]]
|
Nope
|
* Badge Team, already working on it [[TiLDA 2]]
* Workshop Team, if I can convince JamesH form NottingHack to still do it with me, Organising of the workshop tents, before during and after. Includes worshop tents for people to hold workshops, and general hacking/making tents
* Buildup and teardown
|
* Anything in between Badge hacking and running the Workshop area



|-
|
[[User:User_4574|Nathan Lasseter]]
|
B,B1,f,k,p (clean)
|
* Help with the NOC team (LAIT1 Accredited)
* Lay/fly cabling/fibre
* Buildup and teardown
|
* Do most things once



|-
|
[[User:danrl|danrl]]
|
B, C1, C
|
* deploy wireless / wired network
* build-up and tear-down
* IPv6 / NAT64
* Colocation
* Making teh NOC tent a fancy place to chill^M^Mwork hard
|
* rescue golf carts from ditches



|-
|
[[User:markp|markp]]
|
B, B1, f, k. p (clean)
|
* network / power cabling & termination
* build-up and tear-down
* transport (have estate car and trailer)
* lighting
* have access to mifare card/badge printing facilities
* assist with camping facilities
|
* help out wherever I'm needed
(can only be on-site Friday to Monday, but happy to help weekend before)



|-
|
[[User:bigcw|bigcw]]
|
B, B+E
|
* Get involved. Will help with anything. Very good at 'getting things done'.
|
* Connectivity (15 years experience in ISP industry)
* Power (former event lighting engineer)
* Transport (have Range Rover and trailer license)
* Anything else (lots of local knowledge, contacts, etc)



|-
|
[[User:simonvc|Simon Vans-Colina]]
|
A,B,BE,B2,f,k,p
|
* Anything really
|
* Dont have a car, but can drive one if needed.



|-
|
[[User:Si1entDave|Dave Wilson]]
|
B, B1
|
* Most things involving cables - I am also known as SparkyDave, head of site electrics for Profound Decisions LRP events
* My attendance will be contingent on my employer, Warwicknet, providing the connectivity - in which case they will give me the time off to attend :-)
* I also have a Defender which I am rather good at using to position trailers/generators/etc on fields
|
* I'll muck in with most things, but definitely specialise in electrics and networking.



|-
|
[[User:gmc|gmc]]
|
B, AM
|
* drive a manitou
* man the HQ
* do radio
* organize stuff
* A/V related stuff
* all of the above preferably in a supervisory / gophery kinda way
* build-up / tear-down
|
* pick up trash
* herald a lecture venue
* driving
* bar-shifts
* ...



|-
|
[[User:sleepycal|sleepycal]]
|
B,B1 (clean)
|
* Anything network related (NOC support, cabling, maintenance etc)
* Any aspect of site build-up/tear-down
* Prep work / planning
* Anything workshop related
* On-site help/emergency team (someone you can flag down any time/place if you need help)
|
* Anything to help out



|-
|
[[User:Big Kate|Big Kate]]
|
B, BE, C1, C1E, D1, D1E, Blue Badge
|
* Heralding/Speaker desk - On the day introduction to events etc
* Green Room Team:Content - Building a green room
* Making sure presenters have met there Heralds, hand off process etc
* Team:Rehash - Assuming its the same crew from OHM
* Queering the community i.e. LGBT etc community aspects
* Disability Access issues
|
* Build up and tear down
* (as best I can - given my disabilities)
* Drive Vehicles - upto 7.5 Tonnes
* (I have a disabled/ blue badge)
* (easier parking/ pickup/ drop off)
* Logistics and Operations
* Usual gophering type stuff



|-
|
[[User:drrk|Kimball]]
|
None
|
* <s>Buildup</s>Due to change of job I can't be there before the Friday now :(
* Badge Firmware
* Sysadmin
* AV/Radio
|
* Anything else


|-
|
[[User:Critical|Critical]]
|
B, BE, C1, C1E, D1, D1E
|
* Build up and tear down
* Anything Network / IT / AV related
* Meet / greet / help
|
* Whatever is needed


|-
|
[[User:chris_martin|chris_martin]]
|
0
|
* Build up and tear down
* FULLY SIA LICENSED >>> marshaling
* bar-shifts
|
* Whatever is needed


|-
|
[[User:lozarythmic|lozarythmic]]
|
AM, A, B, B1 (clean)
|
* Networking
* Fire Marshall
* Bar Work
|
* Whatever is needed


|-
|
[[User:JimM|Jim MacArthur]]
|
|
* Build up/tear down
* Bar Work
|
* Whatever is needed


|-
|
[[User:RattyMaHatty|Ratty]]
|
B, BE, C1, C1E, D1, D1E, fklnp (a few points)
|
* M$ Windows fixing
* PC/Server hardware engineer
* Networking
* Bar Work
* Driving
|
* Whatever is needed


|-
|
[[User:ens|ens]]
|
None - but willing ;)
|
* Media/Editing stuff (Can provide lend of broadcast-standard video gear if needed, aswell as editing gear)
* You need an electro-hacker-trippy-ambient DJ? hook me up.
* Build-up or Tear-down.
* Heralding.
* Helping those who are giving talks to get sorted.
|
* Help sourcing physical resources for the site.


|-
|
[[User:pioneer|pioneer]]
|
B,B+E,kfp (clean)
|
* Help Deploy wireless / wired network - Anything network related.. I have my own RJ45 Cripmer :p
* Help with VoIP system if deployed
* Sysadmin, NOC Help, Server admin
* Power, Lighting, AV - Part time sound engineer with access to PA systems, AV gear, projectors etc
* Build-up and tear-down
|
* I can loan a PA System
* can also loan networking/wifi + server equipment if needed, just ask and I might have it.
* I'll Help with most things, but I specialise in electrics, networking / server admin.


|-
|
[[User:AK47|AK47]]
|
B
|
* NOC
* WiFi
* VoIP
* General networking stuff
|
* Anything else