<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Aquarion</id>
	<title>PD Crew Wiki - User contributions [en-gb]</title>
	<link rel="self" type="application/atom+xml" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Aquarion"/>
	<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/crew-wiki/Special:Contributions/Aquarion"/>
	<updated>2026-04-04T09:49:52Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.6</generator>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=5070</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=5070"/>
		<updated>2023-05-19T17:26:44Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:IT]]&lt;br /&gt;
= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Apple devices on site ==&lt;br /&gt;
&lt;br /&gt;
For some reason best known only to Apple, their devices don&#039;t want to connect to a network that doesn&#039;t have a default gateway they can reach. Back in Preston, the gateway is their router (10.0.0.2), but that&#039;s not reachable from the field.&lt;br /&gt;
&lt;br /&gt;
If you shut down DHCP on beaker and instead run it on merple, devices will get told the default gateway is 10.0.0.19 (merple), which they can reach, and therefore will connect happily to the network.&lt;br /&gt;
1. On beaker, open &amp;lt;code&amp;gt;Services&amp;lt;/code&amp;gt; and find &amp;lt;code&amp;gt;DHCP Server&amp;lt;/code&amp;gt;. Stop it, but don&#039;t change its startup settings (we want it running when it goes back to Preston).&lt;br /&gt;
1. On merple, run &amp;lt;code&amp;gt;systemctl start dhcpd.service&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will need to be done after the servers are rebooted.&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
Ideally, they go to the password reset page - https://www.profounddecisions.co.uk/empireplotwiki/Special:PasswordReset for the plot wiki - and that works. &lt;br /&gt;
&lt;br /&gt;
If not, ssh in:&lt;br /&gt;
&lt;br /&gt;
* SSH into the server&lt;br /&gt;
* Go to the directory for the wiki:&lt;br /&gt;
** Plot Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
** Public Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-public&amp;lt;/code&amp;gt;&lt;br /&gt;
** Crew Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-pd&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script: &amp;lt;code&amp;gt;php maintenance/changePassword.php --user={USERS_USER_NAME} --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Suggest they go to change it at &amp;lt;code&amp;gt;https://www.profounddecisions.co.uk/empireplotwiki/Special:ChangeCredentials/&amp;lt;/code&amp;gt; (replace for correct wiki location)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;br /&gt;
&lt;br /&gt;
== Clearing a wiki cache ==&lt;br /&gt;
&lt;br /&gt;
ssh in, go to the directory for the wiki (same as above)&lt;br /&gt;
&lt;br /&gt;
Then run: &amp;lt;code&amp;gt;php maintenance/purgeList.php --all -v&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4914</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4914"/>
		<updated>2022-07-22T20:21:19Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
Ideally, they go to the password reset page - https://www.profounddecisions.co.uk/empireplotwiki/Special:PasswordReset for the plot wiki - and that works. &lt;br /&gt;
&lt;br /&gt;
If not, ssh in:&lt;br /&gt;
&lt;br /&gt;
* SSH into the server&lt;br /&gt;
* Go to the directory for the wiki:&lt;br /&gt;
** Plot Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
** Public Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-public&amp;lt;/code&amp;gt;&lt;br /&gt;
** Crew Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-pd&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script: &amp;lt;code&amp;gt;php maintenance/changePassword.php --user=aquarion --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Suggest they go to change it at &amp;lt;code&amp;gt;https://www.profounddecisions.co.uk/empireplotwiki/Special:ChangeCredentials/&amp;lt;/code&amp;gt; (replace for correct wiki location)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4913</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4913"/>
		<updated>2022-07-22T20:19:59Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
Ideally, they go to the password reset page - https://www.profounddecisions.co.uk/empireplotwiki/Special:PasswordReset for the plot wiki - and that works. &lt;br /&gt;
&lt;br /&gt;
If not, ssh in:&lt;br /&gt;
&lt;br /&gt;
* Go to the directory for the wiki.:&lt;br /&gt;
* SSH into the server&lt;br /&gt;
  * Plot Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
  * Public Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-public&amp;lt;/code&amp;gt;&lt;br /&gt;
  * Crew Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-pd&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script: &amp;lt;code&amp;gt;php maintenance/changePassword.php --user=aquarion --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Suggest they go to change it at &amp;lt;code&amp;gt;https://www.profounddecisions.co.uk/empireplotwiki/Special:ChangeCredentials/&amp;lt;/code&amp;gt; (replace for correct wiki location)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4842</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4842"/>
		<updated>2022-04-18T17:40:53Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
Ideally, they go to the password reset page - https://www.profounddecisions.co.uk/empireplotwiki/Special:PasswordReset for the plot wiki - and that works. &lt;br /&gt;
&lt;br /&gt;
If not, ssh in:&lt;br /&gt;
&lt;br /&gt;
* Go to the directory for the wiki.:&lt;br /&gt;
* SSH into the server&lt;br /&gt;
* * Plot Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
* * Public Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-public&amp;lt;/code&amp;gt;&lt;br /&gt;
* * Crew Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-pd&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script e.g &amp;lt;code&amp;gt;php maintenance/changePassword.php --user=aquarion --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Suggest they go to change it at &amp;lt;code&amp;gt;https://www.profounddecisions.co.uk/empireplotwiki/Special:ChangeCredentials/&amp;lt;/code&amp;gt; (replace for correct wiki location)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4841</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=4841"/>
		<updated>2022-04-18T17:17:59Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Changing a Wiki User password */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
* Go to the directory for the wiki.:&lt;br /&gt;
* SSH into the server&lt;br /&gt;
* * Plot Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
* * Public Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-public&amp;lt;/code&amp;gt;&lt;br /&gt;
* * Crew Wiki &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-pd&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script e.g &amp;lt;code&amp;gt;php maintenance/changePassword.php --user=aquarion --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Suggest they go to change it at &amp;lt;code&amp;gt;https://www.profounddecisions.co.uk/empireplotwiki/Special:ChangeCredentials/&amp;lt;/code&amp;gt; (replace for correct wiki location)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=2566</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=2566"/>
		<updated>2018-09-24T21:58:12Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;br /&gt;
&lt;br /&gt;
== Changing a Wiki User password ==&lt;br /&gt;
&lt;br /&gt;
* Go to the directory for the wiki. eg &amp;lt;code&amp;gt;cd /srv/www/htdocs/mediawiki-crew-empire&amp;lt;/code&amp;gt;&lt;br /&gt;
* Run the script e.g &amp;lt;code&amp;gt;php maintenance/changePassword.php --user=aquarion --password=VerySecurePassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That&#039;s it.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2491</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2491"/>
		<updated>2018-04-27T18:29:54Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || 0026.cb6a.8db0 || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| Outside GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || 0023.5e0b.6b40 || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients || Navarr toilets || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || root access point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2490</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2490"/>
		<updated>2018-04-27T17:35:50Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || 0026.cb6a.8db0 || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| Outside GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || 0023.5e0b.6b40 || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients || Navarr toilets || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2488</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2488"/>
		<updated>2018-04-27T13:41:00Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || 0026.cb6a.8db0 || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| Outside&lt;br /&gt;
 GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || 0023.5e0b.6b40 || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2487</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2487"/>
		<updated>2018-04-27T12:40:15Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || 0026.cb6a.8db0 || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || 0023.5e0b.6b40 || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2486</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2486"/>
		<updated>2018-04-27T12:35:49Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2485</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2485"/>
		<updated>2018-04-27T11:48:20Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Current configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || repeater || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2484</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2484"/>
		<updated>2018-04-27T11:14:31Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Current configuration ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-e || 10.1.0.40 || 001f.9ed3.3fe0 || 10.1.0.41 || 10.2.0.40 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-f || 10.1.0.42 || 0013.19a4.9fe0 || 10.1.0.43 || 10.2.0.42 ||  || non-root bridge wireless-clients || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root ||Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater |||| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| India || 10.1.0.44 || 000d.29e1.60d9 || 10.1.0.45 || 10.2.0.44 || Not Set || repeater || Military Council || OK || Dot11Radio1 fitted, not configured&lt;br /&gt;
|-&lt;br /&gt;
| Juliet || 10.1.0.46 || 000d.2917.ebee || 10.1.0.47 || 10.2.0.46 || Not Set || root || || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
| Kilo || 10.1.0.48 || 000d.bc7e.716a || 10.1.0.49 || 10.2.0.48 || Not Set || repeater || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Lima || 10.1.0.52 ||  || 10.1.0.53 || 10.2.0.52 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Mike || 10.1.0.54 ||  || 10.1.0.55 || 10.2.0.54 || Not Set || repeater/root || || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| November|| 10.1.0.50 || 000d.2917.eba6 || 10.1.0.51 || 10.2.0.50 || Not Set || root|| GOD || OK || Dot11Radio 0 not fitted&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Capabilities ==&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz or 5 Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have many units:&lt;br /&gt;
  12(?) x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200 series)&lt;br /&gt;
&lt;br /&gt;
Some of the 1200 series have two radios installed: The 2.4-GHz radio is radio 0, and the 5-GHz radio is radio 1.&lt;br /&gt;
&lt;br /&gt;
  6x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (Aironet 1300 series)&lt;br /&gt;
&lt;br /&gt;
== Controlling the units ==&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided or the cyan USB-serial cables.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet and have a web interface which is occasionally useful. By default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address, but we have over-ridden this for obvious reasons (it&#039;s hard to telnet to a device when you don&#039;t know what its address is ...).&lt;br /&gt;
&lt;br /&gt;
=== Connecting ===&lt;br /&gt;
==== Windows XP ====&lt;br /&gt;
Use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
==== OSX/Linux ====&lt;br /&gt;
There should be a USB/Serial cable in the box. Clive will also have one in his bag of stuff. But if you lose his, it will be painful ...&lt;br /&gt;
&lt;br /&gt;
Find the port number in terminal:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ ls -ltr /dev/*usb*&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   2  7 Apr 16:33 /dev/tty.usbserial-AH0668GD&lt;br /&gt;
crw-rw-rw-  1 root  wheel   21,   3  7 Apr 16:33 /dev/cu.usbserial-AH0668GD&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use screen to connect:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;$ screen /dev/tty.usbserial-AH0668GD 9600&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Log in ====&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
== Configuring units ==&lt;br /&gt;
&lt;br /&gt;
==== Common ====&lt;br /&gt;
&lt;br /&gt;
* Enter admin mode&lt;br /&gt;
** Gain privileged access: enable&lt;br /&gt;
** The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
* Enter config mode.&lt;br /&gt;
** Enter (configuration) context: &lt;br /&gt;
    configure terminal&lt;br /&gt;
&lt;br /&gt;
* Set the local hostname:&lt;br /&gt;
** Set hostname: &lt;br /&gt;
    hostname NEWHOSTNAME&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
* Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
** Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
    sntp broadcast client&lt;br /&gt;
  &lt;br /&gt;
* Configure AP to maintain a network map:&lt;br /&gt;
** Enable network-map generation &lt;br /&gt;
    dot11 network-map 1&lt;br /&gt;
&lt;br /&gt;
* Configure AP with the PDCREW wireless network details:&lt;br /&gt;
** Mint the new SSID: &amp;lt;pre&amp;gt;dot11 ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the shared secret to connect to this AP:&lt;br /&gt;
    authentication open&lt;br /&gt;
    authentication key-management wpa&lt;br /&gt;
    wpa-psk ascii PASSWORD&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer. You know what the password is ...&lt;br /&gt;
&lt;br /&gt;
* Allow to be used as an infrastructure ssid&lt;br /&gt;
    infrastructure-ssid optional&lt;br /&gt;
* Set the SSID to be announced:&lt;br /&gt;
    guest-mode&lt;br /&gt;
* Exit from SSID sub-mode: &lt;br /&gt;
    exit&lt;br /&gt;
&lt;br /&gt;
* Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
** Select a radio interface to add the SSID to: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Tell the wireless system to use correct regional settings:&amp;lt;pre&amp;gt;world-mode dot11d country-code GB outdoor&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the radio to optimise for range (as opposed to speed)&amp;lt;pre&amp;gt;speed range&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the power settings to locally-permitted maximums.&amp;lt;pre&amp;gt;power local cck maximum&amp;lt;/pre&amp;gt;&amp;lt;pre&amp;gt;power local ofdm maximum&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set to channel 1:&amp;lt;pre&amp;gt;channel 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Turn the radio on:&amp;lt;pre&amp;gt;no shutdown&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Configure encryption mode ciphers:&amp;lt;pre&amp;gt;encryption mode ciphers tkip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** enable extensions:&amp;lt;pre&amp;gt;dot11 extension aironet&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Add the SSID to this radio:&amp;lt;pre&amp;gt;ssid PDCREW&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit SSID configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the ethernet port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface FastEthernet 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.1.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit ethernet configuration mode: &amp;lt;pre&amp;gt;exit&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure the BVI port&lt;br /&gt;
** select interface&amp;lt;pre&amp;gt;interface BVI 1&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set the ip address&amp;lt;pre&amp;gt;ip address 10.2.0.x 255.0.0.0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Exit BVI configuration mode: exit&lt;br /&gt;
&lt;br /&gt;
* Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
   bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
* Save your work&lt;br /&gt;
   copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
==== Root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a root bridge role:&lt;br /&gt;
** Enable configuration mode: &amp;lt;pre&amp;gt;configuration terminal&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Select 2.4Ghz radio:&amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role:&amp;lt;pre&amp;gt;station-role root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Non-root bridge ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a non-root bridge role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Field/Tent AP ====&lt;br /&gt;
&lt;br /&gt;
* Make sure the radio is in root mode:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role non-root bridge wireless-clients&amp;lt;/pre&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
==== Repeater ====&lt;br /&gt;
&lt;br /&gt;
* Configure radio to operation in a repeater role:&lt;br /&gt;
** Select 2.4Ghz radio: &amp;lt;pre&amp;gt;interface dot11radio 0&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Set role: &amp;lt;pre&amp;gt;station-role repeater&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Finish ====&lt;br /&gt;
&lt;br /&gt;
* Review the current SSID list:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config ssid PDCREW&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show the network-map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show dot11 network-map&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show live configuration:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show running-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
* Commit live configuration as the new default:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;copy running-config startup-config&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show neighbouring Cisco equipment:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;show cdp neighbors [detail]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Show interface status:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;sh ip interface brief&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Get an idea of your network map:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh dot11 associations&lt;br /&gt;
&lt;br /&gt;
802.11 Client Stations on Dot11Radio0:&lt;br /&gt;
&lt;br /&gt;
SSID [PDCREW] :&lt;br /&gt;
&lt;br /&gt;
MAC Address    IP address      Device        Name            Parent         State&lt;br /&gt;
000d.29e1.60d9 10.2.0.44       Repeater      india           000d.bc7e.716a Assoc&lt;br /&gt;
000d.bc7e.716a 10.2.0.48       ap1200-Rptr   kilo            self           Assoc&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Removing an ssid ===&lt;br /&gt;
Some images set up the _tsunami_ ssid on factory reset, to remove it:&lt;br /&gt;
(from configure mode)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
ap(config)#interface dot11Radio 0&lt;br /&gt;
ap(config-if)#no ssid tsunami&lt;br /&gt;
ap(config-if)#exit&lt;br /&gt;
// if fitted repeat for dot11Radio 1&lt;br /&gt;
ap(config)#no dot11 ssid tsunami&lt;br /&gt;
ap(config)#exit&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Factory reset ==&lt;br /&gt;
=== 1200 series ===&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
=== 1300 series ===&lt;br /&gt;
If you can login (enable):&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;erase nvram&amp;lt;/code&amp;gt; to erase all NVRAM files including the startup configuration.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;reload&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Erase of nvram: complete&amp;lt;/code&amp;gt;. This command reloads the operating system.&lt;br /&gt;
*Enter &amp;lt;code&amp;gt;Y&amp;lt;/code&amp;gt; when the following CLI message appears: &amp;lt;code&amp;gt;Proceed with reload? [confirm]&amp;lt;/code&amp;gt;.&lt;br /&gt;
If you can&#039;t login, try &#039;&#039;&#039;really hard&#039;&#039;&#039; to log in. Otherwise:&lt;br /&gt;
*Open the CLI with a Telnet session or a connection to the bridge console port.&lt;br /&gt;
*Reboot the bridge by removing and reapplying power.&lt;br /&gt;
*Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.&lt;br /&gt;
*Press ESC when you see lines that are similar to these on the CLI:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314&amp;quot;&lt;br /&gt;
...#############################################################################&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.&lt;br /&gt;
Messages that are similar to these appear:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Error loading &amp;quot;flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_&lt;br /&gt;
ja.20040314&amp;quot;&lt;br /&gt;
Interrupt within 5 seconds to abort boot process.&lt;br /&gt;
Boot process terminated.&lt;br /&gt;
The system is unable to boot automatically. The BOOT environment variable needs to &lt;br /&gt;
be set to a bootable image.&lt;br /&gt;
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*At the bridge: prompt, issue the &#039;&#039;&#039;dir flash:&#039;&#039;&#039; command in order to view a directory of the Flash file system. The directory is similar to this directory:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: dir flash:&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
2	-rwx		0		&amp;lt;date&amp;gt;	env_vars&lt;br /&gt;
5	drwx		384		&amp;lt;date&amp;gt;	C1310-k9w7-mx.v133_15_JA.20040314&lt;br /&gt;
3	-rwx		1128		&amp;lt;date&amp;gt;	config.txt&lt;br /&gt;
4	-rwx		5		&amp;lt;date&amp;gt;	private-config&lt;br /&gt;
&lt;br /&gt;
3693568 bytes available (4047872 bytes used)&lt;br /&gt;
bridge:&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Delete or rename the files config.txt and env_vars, and reboot the bridge. &#039;&#039;&#039;Note&#039;&#039;&#039;: Do not forget the / character before the filenames.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge: delete flash:/config.txt&lt;br /&gt;
Are you sure you want to delete flash:/config.txt (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/config.txt&amp;quot; deleted&lt;br /&gt;
&lt;br /&gt;
bridge: delete flash:/env_vars&lt;br /&gt;
Are you sure you want to delete &amp;quot;flash:/env_vars&amp;quot; (y/n)?y&lt;br /&gt;
File &amp;quot;flash:/env_vars&amp;quot; deleted&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
*Issue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.&lt;br /&gt;
&lt;br /&gt;
== Updating the operating system --- Here be dragons ==&lt;br /&gt;
Some problems Clive has been having with some of the devices have been resolved by updating to a more recent version of IOS. (Yes, Cisco also call their OS IOS. In fairness, they were there first: [https://blogs.cisco.com/news/cisco_and_apple_agreement_on_ios_trademark “Cisco has agreed to license the iOS trademark to Apple for use as the name of Apple’s operating system for iPhone, iPod touch and iPad.  The license is for use of the trademark only and not for any technology.”])&lt;br /&gt;
&lt;br /&gt;
There should be a running tftp server on favog. It should even have one or more IOS images on it. It&#039;ll look like this (once Clive has copied it from his local server to favog, anyway):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt; ls -ls /srv/tftpboot/&lt;br /&gt;
total 5284&lt;br /&gt;
5284 -rw-r--r-- 1 tftp tftp 5408256 Apr 23 19:41 c1310-k9w7-mx.124-10b.JA1.tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Steps ===&lt;br /&gt;
Simple in principle:&lt;br /&gt;
# Find an equivalent piece of hardware that is working and has the feature &lt;br /&gt;
# Get both devices on the network, use an ethernet cable for preference&lt;br /&gt;
# Upload its current image, if it&#039;s not already there&lt;br /&gt;
# Download it on the &#039;broken&#039; one&lt;br /&gt;
==== Upload an image ====&lt;br /&gt;
First, find out what image you have. It&#039;ll be the directory with long name starting with your hardware&#039;s part number, eg:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#sh flash&lt;br /&gt;
&lt;br /&gt;
Directory of flash:/&lt;br /&gt;
&lt;br /&gt;
    2  -rwx        2072   Mar 1 2002 00:11:18 +00:00  private-multiple-fs&lt;br /&gt;
    3  -rwx        1261   Mar 1 2002 00:11:18 +00:00  config.txt&lt;br /&gt;
    4  drwx         256   Jan 1 1970 00:06:24 +00:00  c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
  153  -rwx          70   Mar 1 2002 00:02:33 +00:00  env_vars&lt;br /&gt;
  155  -rwx           5   Mar 1 2002 00:11:18 +00:00  private-config&lt;br /&gt;
&lt;br /&gt;
7741440 bytes total (2395648 bytes free)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, &#039;&#039;&#039;c1310-k9w7-mx.124-10b.JA1&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Copying it is actually fairly easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-e#archive upload-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Download an image ====&lt;br /&gt;
Again, relatively easy:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;bridge-f#archive download-sw tftp://10.0.0.18/[the directory name from above].tar&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
You&#039;ll see something along the lines of:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;examining image...&lt;br /&gt;
Loading c1310-k9w7-mx.124-10b.JA1.tar from 192.168.0.20 (via BVI1): !&lt;br /&gt;
extracting info (275 bytes)!!!!!!!!!!!!!!!!! &lt;br /&gt;
[OK - 5408256 bytes]&lt;br /&gt;
&lt;br /&gt;
Image info:&lt;br /&gt;
    Version Suffix: k9w7-.124-10b.JA1&lt;br /&gt;
    Image Name: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Version Directory: c1310-k9w7-mx.124-10b.JA1&lt;br /&gt;
    Ios Image Size: 4669952&lt;br /&gt;
    Total Image Size: 5407232&lt;br /&gt;
    Image Feature: UNKNOWN&lt;br /&gt;
    Image Family: C1310&lt;br /&gt;
    Wireless Switch Management Version: 1.0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
followed by a lot of progress information which may well include wiping the original image out.&lt;br /&gt;
&lt;br /&gt;
Once this is done, restart it. And hope that you&#039;ve not bricked it ...&lt;br /&gt;
&lt;br /&gt;
== Old bits from early experiments, probably not really worth keeping, but just might be ==&lt;br /&gt;
&lt;br /&gt;
Aquarion&#039;s notes, essentially&lt;br /&gt;
============&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:Pdlogo-white.png&amp;diff=2466</id>
		<title>File:Pdlogo-white.png</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:Pdlogo-white.png&amp;diff=2466"/>
		<updated>2018-04-23T20:54:27Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Aquarion uploaded a new version of File:Pdlogo-white.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:Pdlogo-white.png&amp;diff=2465</id>
		<title>File:Pdlogo-white.png</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:Pdlogo-white.png&amp;diff=2465"/>
		<updated>2018-04-23T20:50:13Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Backups&amp;diff=2416</id>
		<title>Server Backups</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Backups&amp;diff=2416"/>
		<updated>2018-03-05T16:26:40Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Created page with &amp;quot;Every day, Cron runs a bash script to backup the MySQL DB &amp;amp; Mediawiki image files to Beaker, from where we rely on Beaker&amp;#039;s cloud backup for longer term storage.  == The Scrip...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Every day, Cron runs a bash script to backup the MySQL DB &amp;amp; Mediawiki image files to Beaker, from where we rely on Beaker&#039;s cloud backup for longer term storage.&lt;br /&gt;
&lt;br /&gt;
== The Script ==&lt;br /&gt;
&lt;br /&gt;
The canonical location of the script is &amp;lt;code&amp;gt;/root/backup.sh&amp;lt;/code&amp;gt;, there is a symlink from &amp;lt;code&amp;gt;/etc/cron.daily/backup.sh&amp;lt;/code&amp;gt; (which is how it runs daily)&lt;br /&gt;
&lt;br /&gt;
== Databases ==&lt;br /&gt;
&lt;br /&gt;
The script loops through the databases (except the system DBs &#039;information_schema&#039;, &#039;performance_schema&#039;  &amp;amp; &#039;archive&#039;), dumps them in SQL format to a tmpfile, and then compresses that file to &amp;lt;code&amp;gt;/mnt/beaker/IT/MySQL_Backups/[DAY OF THE WEEK]/[DATABASE].sql.bz&amp;lt;/code&amp;gt;, providing us with an automated one week backlog &lt;br /&gt;
&lt;br /&gt;
== Wiki Uploads ==&lt;br /&gt;
&lt;br /&gt;
The three live wikis (Crew, Plot &amp;amp; Public) also have their image directories backed up to &amp;lt;code&amp;gt;/mnt/beaker/IT/mediawiki-image-backups/&amp;lt;/code&amp;gt; by rsync as part of the same script. &lt;br /&gt;
&lt;br /&gt;
== Flaws == &lt;br /&gt;
&lt;br /&gt;
* Errors go to cron-mail, which I&#039;m fairly sure is a black hole&lt;br /&gt;
* Working out which is the most recent backup isn&#039;t trivial&lt;br /&gt;
* Daily cron tasks happen at 17:45, which isn&#039;t a great time to slow the DB down.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=2415</id>
		<title>Server Playbooks</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Server_Playbooks&amp;diff=2415"/>
		<updated>2018-03-05T16:10:42Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Created page with &amp;quot;= Stuff on how the servers work =  * Wiki Transfer * Beaker DNS * Favog Wiki Backups&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Stuff on how the servers work =&lt;br /&gt;
&lt;br /&gt;
* [[Wiki Transfer]]&lt;br /&gt;
* [[Beaker DNS]]&lt;br /&gt;
* [[Favog Wiki Backups]]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:TitleBar&amp;diff=2414</id>
		<title>Imperial:TitleBar</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:TitleBar&amp;diff=2414"/>
		<updated>2018-03-05T16:09:17Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* All Crew&lt;br /&gt;
** [[General introduction|Overview]]&lt;br /&gt;
** --&lt;br /&gt;
** [[Crewing]]&lt;br /&gt;
** [[Crew organization|Organization]]&lt;br /&gt;
** [[What to wear|What to Wear]]&lt;br /&gt;
** [[Crew protocol|Crew Protocol]]&lt;br /&gt;
** [[Supporting players|Supporting Players]]&lt;br /&gt;
** [[New crew|New Crew]]&lt;br /&gt;
** --&lt;br /&gt;
** [[Time off|Time Off]]&lt;br /&gt;
** [[Food and drink|Food and Drink]]&lt;br /&gt;
** [[Crew facebook groups|Crew Facebook Groups]]&lt;br /&gt;
* Plot&lt;br /&gt;
** [[Plot organization|Organization]]&lt;br /&gt;
** --&lt;br /&gt;
** =Writing=&lt;br /&gt;
** [[Plot team|Plot Team]]&lt;br /&gt;
** [[Style guide|Style Guide]]&lt;br /&gt;
** [[Plot creation process|Process]]&lt;br /&gt;
** [[Plot tools|Tools]]&lt;br /&gt;
** =Skirmish=&lt;br /&gt;
** [[Battle team|Organization]]&lt;br /&gt;
** [[Skirmish style guide|Approach]]&lt;br /&gt;
* NPCs&lt;br /&gt;
** [[NPC guidelines|Guidelines]]&lt;br /&gt;
** --&lt;br /&gt;
** = Civil Service =&lt;br /&gt;
** [[Civil servants|Civil Servants]]&lt;br /&gt;
** [[Hub records|Hub Records]]&lt;br /&gt;
** = Skirmish Team =&lt;br /&gt;
** [[The Hundred]]&lt;br /&gt;
** = Player Support =&lt;br /&gt;
** [[Three Refrains]]&lt;br /&gt;
* Refs&lt;br /&gt;
** [[Intervention|How and When to Intervene]]&lt;br /&gt;
** [[Ref jackets|Ref Jackets]]&lt;br /&gt;
** [[Ref documents]]&lt;br /&gt;
** [[Introduction to reffing]]&lt;br /&gt;
* Site&lt;br /&gt;
** [[Early Arrivals]]&lt;br /&gt;
** [[Hook loader units]]&lt;br /&gt;
** [[Local amenities]]&lt;br /&gt;
** [[Vehicle safety|Vehicle Safety]]&lt;br /&gt;
* Admin&lt;br /&gt;
** [[Radio protocol|Radio Protocol]]&lt;br /&gt;
** [[Ordering check list]]&lt;br /&gt;
* IT&lt;br /&gt;
** [[Broken rituals]]&lt;br /&gt;
** [[Photography]]&lt;br /&gt;
** [[Wireless]]&lt;br /&gt;
** [[IT work required]]&lt;br /&gt;
** [[Server Playbooks]]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:TitleBar&amp;diff=2413</id>
		<title>Imperial:TitleBar</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:TitleBar&amp;diff=2413"/>
		<updated>2018-03-05T16:09:00Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* All Crew&lt;br /&gt;
** [[General introduction|Overview]]&lt;br /&gt;
** --&lt;br /&gt;
** [[Crewing]]&lt;br /&gt;
** [[Crew organization|Organization]]&lt;br /&gt;
** [[What to wear|What to Wear]]&lt;br /&gt;
** [[Crew protocol|Crew Protocol]]&lt;br /&gt;
** [[Supporting players|Supporting Players]]&lt;br /&gt;
** [[New crew|New Crew]]&lt;br /&gt;
** --&lt;br /&gt;
** [[Time off|Time Off]]&lt;br /&gt;
** [[Food and drink|Food and Drink]]&lt;br /&gt;
** [[Crew facebook groups|Crew Facebook Groups]]&lt;br /&gt;
* Plot&lt;br /&gt;
** [[Plot organization|Organization]]&lt;br /&gt;
** --&lt;br /&gt;
** =Writing=&lt;br /&gt;
** [[Plot team|Plot Team]]&lt;br /&gt;
** [[Style guide|Style Guide]]&lt;br /&gt;
** [[Plot creation process|Process]]&lt;br /&gt;
** [[Plot tools|Tools]]&lt;br /&gt;
** =Skirmish=&lt;br /&gt;
** [[Battle team|Organization]]&lt;br /&gt;
** [[Skirmish style guide|Approach]]&lt;br /&gt;
* NPCs&lt;br /&gt;
** [[NPC guidelines|Guidelines]]&lt;br /&gt;
** --&lt;br /&gt;
** = Civil Service =&lt;br /&gt;
** [[Civil servants|Civil Servants]]&lt;br /&gt;
** [[Hub records|Hub Records]]&lt;br /&gt;
** = Skirmish Team =&lt;br /&gt;
** [[The Hundred]]&lt;br /&gt;
** = Player Support =&lt;br /&gt;
** [[Three Refrains]]&lt;br /&gt;
* Refs&lt;br /&gt;
** [[Intervention|How and When to Intervene]]&lt;br /&gt;
** [[Ref jackets|Ref Jackets]]&lt;br /&gt;
** [[Ref documents]]&lt;br /&gt;
** [[Introduction to reffing]]&lt;br /&gt;
* Site&lt;br /&gt;
** [[Early Arrivals]]&lt;br /&gt;
** [[Hook loader units]]&lt;br /&gt;
** [[Local amenities]]&lt;br /&gt;
** [[Vehicle safety|Vehicle Safety]]&lt;br /&gt;
* Admin&lt;br /&gt;
** [[Radio protocol|Radio Protocol]]&lt;br /&gt;
** [[Ordering check list]]&lt;br /&gt;
* IT&lt;br /&gt;
** [[Broken rituals]]&lt;br /&gt;
** [[Photography]]&lt;br /&gt;
** [[Wireless]]&lt;br /&gt;
** [[IT Work Required]]&lt;br /&gt;
** [[Server Playbooks]]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2396</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2396"/>
		<updated>2017-09-15T13:20:09Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| - || Failed to connect - 2017-09-15 || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || Monster || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || God || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Navaar || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| -|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2395</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2395"/>
		<updated>2017-09-15T12:41:39Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| Navaar || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || Monster || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || God || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Golf || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || -|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| -|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2394</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2394"/>
		<updated>2017-09-15T12:39:38Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| Navaar || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || Monster || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || God || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Hotel || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2393</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2393"/>
		<updated>2017-09-15T12:13:17Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Foxtrot || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| Navaar || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Echo || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || Monster || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || God || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-6 || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2392</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2392"/>
		<updated>2017-09-15T12:00:56Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| field-ap || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-1 || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Delta || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root access-point || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || GOD || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || - || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-6 || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2391</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2391"/>
		<updated>2017-09-15T11:56:54Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| field-ap || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-1 || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-2 || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || GOD || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || root || - || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-6 || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2390</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2390"/>
		<updated>2017-09-15T11:55:42Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| field-ap || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-1 || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-2 || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || AP || GOD || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || AP || - || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-6 || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2389</id>
		<title>Wireless</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Wireless&amp;diff=2389"/>
		<updated>2017-09-15T11:55:24Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Hostname !! Wireless IP !! Wireless MAC !!FastEthernet IP !! BVI IP !! Channel !! Mode !! Location !! Config Status !! Notes&lt;br /&gt;
|-&lt;br /&gt;
| bridge-a|| 10.1.0.2 || || 10.1.0.1 || 10.2.0.1 || 2412|| root bridge wireless-clients|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-b || 10.1.0.4 || || 10.1.0.3 || 10.2.0.2|| 2437 || root bridge wireless-clients || GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-c || 10.1.0.16 || || 10.1.0.15 || 10.2.0.3 ||  || root bridge wireless-clients || Monster || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| bridge-d || 10.1.0.18 || || 10.1.0.17 || 10.2.0.4 ||  || non-root bridge wireless-clients ||  || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| field-ap || 10.1.0.6 || || 10.1.0.5 || 10.2.0.5  ||   || repeater|| GOD || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-1 || 10.1.0.8 || || 10.1.0.7 || 10.2.0.7 || Not Set || repeater || Hub|| OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-2 || 10.1.0.10 || ||10.1.0.9 || 10.2.0.6 || 2472 || root || Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| Charlie || 10.1.0.11 || ||10.1.0.12 || 10.2.0.11 || 2447 || root || GOD || ? || -&lt;br /&gt;
|-&lt;br /&gt;
| Bravo || 10.1.0.14 || ||10.1.0.13 ||10.2.0.8 ||  || AP || - || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-5 || 10.1.0.31 || || 10.1.0.30 || 10.2.0.30 || 2447 || repeater || Academy || OK || -&lt;br /&gt;
|-&lt;br /&gt;
| repeater-6 || 10.1.0.20 || || 10.1.0.19 || 10.2.0.19 || Not Set || root|| Stored || OK || -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The Below needs Editing for Sanity/Procedure etc....&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Notes on Cisco Wireless kit&lt;br /&gt;
===========================&lt;br /&gt;
&lt;br /&gt;
Capabilities&lt;br /&gt;
------------&lt;br /&gt;
&lt;br /&gt;
These radios operate in the 2.4Ghz microwave band, and support 802.11b/g wifi connections.&lt;br /&gt;
We have 6 units:&lt;br /&gt;
  4x omnidirectional, indoor units, two with standard antennas, two with (high-gain?) antennas.&lt;br /&gt;
     (Aironet 1200-series)&lt;br /&gt;
&lt;br /&gt;
  2x weather-proofed point-to-point units with highly-directional integrated antennas,&lt;br /&gt;
     with separate (indoor) breakout boxes.&lt;br /&gt;
     (AIR-BR1310G-E-K9)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Controlling the units&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
These wireless base-stations are sophisticated computers in their own right.  They run the&lt;br /&gt;
Cisco IOS operating system: specifically, version 12.3.&lt;br /&gt;
By default, they can be controlled via a serial console, using the special&lt;br /&gt;
cyan RJ45-DB9 serial cable provided.&lt;br /&gt;
&lt;br /&gt;
They can also be controlled via telnet; they are, by default, configured to use DHCP to &lt;br /&gt;
acquire their own IP address.&lt;br /&gt;
&lt;br /&gt;
From Windows XP, you can use Hyperterminal to connect to a unit:&lt;br /&gt;
  -&amp;gt; Use 9600 baud, no parity, 1 stop bit, and disable hardware flow control.&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve got things right, then if you have the cable plugged in when you turn a wireless&lt;br /&gt;
base-unit on, you should see boot-time messages start to scroll past for about a minute after&lt;br /&gt;
power-on.&lt;br /&gt;
&lt;br /&gt;
Press &amp;lt;ENTER&amp;gt; when prompted to bring up control menu.&lt;br /&gt;
&lt;br /&gt;
Prompt is displayed as: ap&amp;gt; -- or, if the device has been given a different hostname, either manually&lt;br /&gt;
or via DHCP, then it will appear as: hostname&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pressing &#039;?&#039; will display a list of commands.  &lt;br /&gt;
&amp;lt;TAB&amp;gt; will auto-complete unambiguous partial commands.&lt;br /&gt;
&lt;br /&gt;
The access point default username is &#039;Cisco&#039; and the default password is &#039;Cisco&#039;.&lt;br /&gt;
&lt;br /&gt;
To return the wireless base-stations to factory settings, power off the device, then -- &lt;br /&gt;
while holding the &#039;mode&#039; button down -- power the wireless device back up.  &lt;br /&gt;
Continue to hold the &#039;mode&#039; button down for a few seconds, then release.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wireless Topology&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
Suggested wireless topology; at this point, only units 1-3 have been configured.&lt;br /&gt;
&lt;br /&gt;
                       (- ~ ~ ~ ~ ~ -)     v ~ ~ v ~ ~ v ~ ~ v&lt;br /&gt;
  [ GOD network ] ---- |             | --- |     |     |     |&lt;br /&gt;
                       RB           NRB    AP    R     R     R&lt;br /&gt;
&lt;br /&gt;
                       #1            #2    #3    #4    #5    #6&lt;br /&gt;
&lt;br /&gt;
     RB : Root-bridge&lt;br /&gt;
     NRB: Non-root bridge&lt;br /&gt;
     AP : Root access point&lt;br /&gt;
     R  : Wireless repeater.&lt;br /&gt;
                                       Wireless MAC       Ethernet MAC		channel&lt;br /&gt;
     #1  -- bridge-a	10.1.0.2 &amp;amp; 1   00:26:cb:6a:8d:b0  88:43:e1:d1:fd:ac     1	\ 1300-series&lt;br /&gt;
     #2  -- bridge-b    10.1.0.4 &amp;amp; 3   00:23:5e:0b:6b:40  00:23:5e:99:56:02     1	/&lt;br /&gt;
     #3  -- field-ap    10.1.0.6 &amp;amp; 5   00:14:69:2d:4a:10  00:14:6a:40:44:49     6	\  &lt;br /&gt;
     #4  -- repeater-1  10.1.0.8 &amp;amp; 7                                            11	  1200-series&lt;br /&gt;
     #5  -- repeater-2  10.1.0.10 &amp;amp; 9   		  00:19:E8:8C:77:AC     13&lt;br /&gt;
     #6  -- repeater-3  10.1.0.12 &amp;amp; 11              	  00:14:69:ee:3b:ab     8                      	/&lt;br /&gt;
     #7  -- repeater-4  10.1.0.13                         00:13:80:ec:bb:b8	5&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These are only suggested IPs; at present, they are all using DHCP to establish their own IP, and these&lt;br /&gt;
have not yet been configured in the AD.&lt;br /&gt;
&lt;br /&gt;
Ideally, the repeaters will also be configured such that wired devices attached to them &lt;br /&gt;
will be bridged onto the crew network.  (Note: this has security implications - we don&#039;t want&lt;br /&gt;
players to be able to do this!)&lt;br /&gt;
&lt;br /&gt;
[ In practice, this appears not to be supported? ]&lt;br /&gt;
&lt;br /&gt;
Performance&lt;br /&gt;
-----------&lt;br /&gt;
&lt;br /&gt;
At Odyssey E1, 2013, bridge-[a/b] and the field-ap were all configured and test-deployed:&lt;br /&gt;
&lt;br /&gt;
  * bridge-a was propped up on a desk in GOD&lt;br /&gt;
  * bridge-b was propped up on a box outside the bar, in the ~middle of the IC field.&lt;br /&gt;
&lt;br /&gt;
This was an initial test, but it proved to be unexpectedly successful.  Despite there being in the way:&lt;br /&gt;
 &lt;br /&gt;
  * Most of GOD&lt;br /&gt;
  * A wet hedgerow&lt;br /&gt;
  * Several (dampened) tents&lt;br /&gt;
  * A number of people milling about&lt;br /&gt;
  * A fair distance&lt;br /&gt;
&lt;br /&gt;
... a solid signal could be established between the two bridge units, despite not having&lt;br /&gt;
done any careful alignment.  (Perhaps we were just lucky?)&lt;br /&gt;
&lt;br /&gt;
&#039;show dot11 statistics client-traffic&#039; shows:&lt;br /&gt;
&lt;br /&gt;
27-0026.cb6a.8db0 pak in 12503 bytes in 2295602 pak out 4385 bytes out 693295&lt;br /&gt;
      dup 0 decrpyt err 0 mic mismatch 0 mic miss 0&lt;br /&gt;
      tx retries 1159 data retries 1158 rts retries 1&lt;br /&gt;
      signal strength 74 signal quality 18&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Configuring units&lt;br /&gt;
-----------------&lt;br /&gt;
&lt;br /&gt;
[] Common&lt;br /&gt;
&lt;br /&gt;
 * Enter admin mode&lt;br /&gt;
     - Gain privileged access: &amp;quot;enable&amp;quot;&lt;br /&gt;
     - The default username and password is &#039;Cisco&#039;.&lt;br /&gt;
 * Enter config mode.&lt;br /&gt;
     - Enter (configuration) context: &amp;quot;configure terminal&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 XXX This doesn&#039;t work, or least, doesn&#039;t appear to have the desired effect.&lt;br /&gt;
 XXX Skip this for now.&lt;br /&gt;
 XXX * Set admin password&lt;br /&gt;
 XXX   - Set password: &amp;quot;enable password NEWPASSWORD&amp;quot;&lt;br /&gt;
 XXX&lt;br /&gt;
 * Set the local hostname:&lt;br /&gt;
     - Set hostname: &amp;quot;hostname NEWHOSTNAME&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note: this will change the default prompt from &#039;ap&#039; to the hostname you specify.   &lt;br /&gt;
&lt;br /&gt;
 * Configure AP to use a broadcast NTP time signal:&lt;br /&gt;
     - Enable the SNTP client, to listen to the first broadcast signal:&lt;br /&gt;
       &amp;quot;sntp broadcast client&amp;quot;&lt;br /&gt;
 * Configure AP to present a login banner:&lt;br /&gt;
     - Set the login banner:&lt;br /&gt;
       &amp;quot; &lt;br /&gt;
Profound Decisions: Network administrators only beyond this point.&lt;br /&gt;
#&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Generate RSA keys for use with SSH:&lt;br /&gt;
     - &amp;quot;crypto key generate rsa general-keys label SSH&amp;quot;&lt;br /&gt;
     - When prompted, say, &#039;2048&#039;.&lt;br /&gt;
 * Set version of SSH to use:&lt;br /&gt;
     - &amp;quot;ip ssh version 2&amp;quot;&lt;br /&gt;
 * Enable SSH by telling it to use the &#039;SSH&#039; RSA keypair:&lt;br /&gt;
     - &amp;quot;ip ssh rsa keypair-name SSH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
XXX&lt;br /&gt;
XXX Note: While logs suggest that this is successful, testing has shown that&lt;br /&gt;
XXX       the APs are not listening on port 22 for SSH.  Some investigation still required.&lt;br /&gt;
XXX&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
 * Configure AP to maintain a network map:&lt;br /&gt;
     - Enable network-map generation: &amp;quot;dot11 network-map 1&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Configure AP with the PDCREW wireless network details:&lt;br /&gt;
     - Mint the new SSID: &amp;quot;dot11 ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the shared secret to connect to this AP:&lt;br /&gt;
       &amp;quot;authentication open&amp;quot;&lt;br /&gt;
       &amp;quot;authentication key-management wpa&amp;quot;&lt;br /&gt;
       &amp;quot;wpa-psk ascii PASSWORD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
NOTE: The WPA-PSK has to be 8 characters or longer.&lt;br /&gt;
&lt;br /&gt;
     - Allow to be used as an infrastructure ssid&lt;br /&gt;
      &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
     - Set the SSID to be announced:&lt;br /&gt;
       &amp;quot;guest-mode&amp;quot;&lt;br /&gt;
     - Exit from SSID sub-mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 * Turn the radio on, and add the PDCREW SSID to it:&lt;br /&gt;
     - Select a radio interface to add the SSID to: &lt;br /&gt;
       &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Tell the wireless system to use correct regional settings:&lt;br /&gt;
       &amp;quot;world-mode dot11d country-code GB outdoor&amp;quot;&lt;br /&gt;
     - Set the radio to optimise for range (as opposed to speed)&lt;br /&gt;
       &amp;quot;speed range&amp;quot;&lt;br /&gt;
     - Set the power settings to locally-permitted maximums.&lt;br /&gt;
       &amp;quot;power local cck maximum&amp;quot;&lt;br /&gt;
       &amp;quot;power local ofdm maximum&amp;quot;&lt;br /&gt;
     - Set to channel 1:&lt;br /&gt;
       &amp;quot;channel 1&amp;quot;&lt;br /&gt;
     - Turn the radio on:&lt;br /&gt;
       &amp;quot;no shutdown&amp;quot;&lt;br /&gt;
     - Configure encryption mode ciphers:&lt;br /&gt;
       &amp;quot;encryption mode ciphers tkip&amp;quot;&lt;br /&gt;
     - enable extensions:&lt;br /&gt;
	&amp;quot;dot11 extension aironet&amp;quot;&lt;br /&gt;
     - Add the SSID to this radio:&lt;br /&gt;
       &amp;quot;ssid PDCREW&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
&lt;br /&gt;
  * Configure the ethernet port&lt;br /&gt;
     - select interface&lt;br /&gt;
      &amp;quot;interface FastEthernet 0&amp;quot;&lt;br /&gt;
     - Set the ip address&lt;br /&gt;
       &amp;quot;ip address 10.1.0.x 255.0.0.0&amp;quot;&lt;br /&gt;
     - Exit SSID configuration mode: &amp;quot;exit&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
  * Enable spanning-tree protocol on the local bridge:&lt;br /&gt;
     - bridge 1 protocol ieee&lt;br /&gt;
&lt;br /&gt;
[] Root bridge&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a root bridge role:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Non-root bridge&lt;br /&gt;
&lt;br /&gt;
 * Specify that the PDCREW network is the one to connect to:&lt;br /&gt;
     - Enable configuration mode: &amp;quot;configuration terminal&amp;quot;&lt;br /&gt;
     - Select the PDCREW network: &amp;quot;dot11 ssid PDCREW&amp;quot;    &lt;br /&gt;
     - Specify that it should be used: &amp;quot;infrastructure-ssid optional&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 * Configure radio to operation in a non-root bridge role:&lt;br /&gt;
     - Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     - Set role: &amp;quot;station-role non-root bridge wireless-clients&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Field AP&lt;br /&gt;
&lt;br /&gt;
  * The AP will, by default, operate in a root access-point mode.&lt;br /&gt;
&lt;br /&gt;
[] Repeater&lt;br /&gt;
&lt;br /&gt;
 XXX This section is as-yet untested.&lt;br /&gt;
&lt;br /&gt;
 * Configure radio to operation in a repeater role:&lt;br /&gt;
     3. Select 2.4Ghz radio: &amp;quot;interface dot11radio 0&amp;quot;&lt;br /&gt;
     4. Set role: &amp;quot;station-role repeater&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[] Finish&lt;br /&gt;
&lt;br /&gt;
 * Review the current SSID list:&lt;br /&gt;
   - &amp;quot;show running-config ssid PDCREW&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
dot11 ssid PDCREW&lt;br /&gt;
   authentication open&lt;br /&gt;
   authentication key-management wpa&lt;br /&gt;
   guest-mode&lt;br /&gt;
   wpa-psk ascii 7 140716081E013D7D76&lt;br /&gt;
end&lt;br /&gt;
&lt;br /&gt;
 * Show the network-map:&lt;br /&gt;
     1. show dot11 network-map&lt;br /&gt;
&lt;br /&gt;
 * Show live configuration:&lt;br /&gt;
     1. show running-config&lt;br /&gt;
 &lt;br /&gt;
 * Commit live configuration as the new default:&lt;br /&gt;
     1. copy running-config startup-config&lt;br /&gt;
&lt;br /&gt;
 * Show neighbouring Cisco equipment:&lt;br /&gt;
     1. show cdp neighbors [detail]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:Footer&amp;diff=2045</id>
		<title>Imperial:Footer</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:Footer&amp;diff=2045"/>
		<updated>2016-11-22T13:39:26Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Removing Ian&amp;#039;s email to avoid deluges of spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;row-fluid&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span4&amp;gt;&lt;br /&gt;
= More About Empire =&lt;br /&gt;
* [[Contact Profound Decisions|Contact us]]&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire/ Empire Blogs]&lt;br /&gt;
* [http://www.youtube.com/user/ProfoundDecisionsLRP Profound Decisions Video Feed]&lt;br /&gt;
&amp;lt;/span4&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span4&amp;gt;&lt;br /&gt;
= Profound Decisions =&lt;br /&gt;
* [http://www.profounddecisions.co.uk/ Home]&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire/ Empire Website]&lt;br /&gt;
* [http://www.profounddecisions.co.uk/event/Tickets Booking]&lt;br /&gt;
&amp;lt;/span4&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span4&amp;gt;&lt;br /&gt;
= Social =&lt;br /&gt;
* [https://www.facebook.com/pages/Empire-LRP/136575943105061 Empire Facebook Page]&lt;br /&gt;
* [https://www.facebook.com/groups/214459878654071/ Empire Facebook Group]&lt;br /&gt;
&amp;lt;/span4&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/row-fluid&amp;gt;&lt;br /&gt;
&amp;lt;hr/&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Skin by Ian and [http://twitter.github.com/bootstrap/ Bootstrap]. Built on [http://mediawiki.org MediaWiki].&amp;lt;br&amp;gt;[[Terms and conditions]]&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=1627</id>
		<title>Plot creation process</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=1627"/>
		<updated>2015-08-19T22:08:50Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
This page is designed to help the writers - and everyone involved with creating and running plot at Empire understand what the process is and how it works.&lt;br /&gt;
&lt;br /&gt;
Producing plot for a large game is a difficult process. With thirty writers and 2000 participants, we need to have a single process for organizing costume, NPCs, props, ribbons for items, debriefs for NPCs. Ultimately the process is designed to help writers; otherwise when you come to run your plot requiring 40 NPCs to dress in Brass Coast costume for a quest - you will discover that all the NPCs are out, all the Brass Coast costume is out and all the quest slots are filled.&lt;br /&gt;
&lt;br /&gt;
==Ethos==&lt;br /&gt;
The writer is central to the ethos for the writing and running plot at events. The [[plot support]] team are here to help, but the default assumption is that the writer will carry out all the steps needed to write and run their plot. As a writer, the responsibility for ensuring that your plot has been approved and timetabled and the right costume, props, and ribbons are ready lies with you. We don&#039;t necessarily expect one person to do all these things, we are here to help and we encourage writers to work together in teams - but the responsibility to ensure that it is done lies with the writer.&lt;br /&gt;
&lt;br /&gt;
We&#039;ve chosen this approach for several reasons. This approach will allow us to scale what we do to run more plot by adding more writers to our team over time. However it should also ensure that the key decisions taken about a plot, timing, budget, briefing, etc - are made by the writer who created it rather than by someone else. And finally it should mean that the writer is able to drive the plot process to ensure that their plot gets approved and run at events.&lt;br /&gt;
&lt;br /&gt;
==Teams==&lt;br /&gt;
We encourage all Empire plot writers to get a team together if they can. There are many advantages to writing plot as part of a team - you have like-minded friends that you can discuss the plot with as you create it. If you can&#039;t make an event, or you&#039;re busy at an event when a question about your plot comes in, then a fellow team member can cover for you.&lt;br /&gt;
&lt;br /&gt;
More importantly, running plot at an Empire event requires a wide range of skills. We don&#039;t assume that a single writer has all those skills, but if you have a team of people then they can cover the skills needed between them. Actually &#039;&#039;writing&#039;&#039; plot is just one part of what is needed to get your plot to run. The best teams will include people who are good with costume, props, briefing and debriefing, time-tabling and logistics, even if some of those people don&#039;t actually &#039;&#039;write&#039;&#039; the plot your team runs.&lt;br /&gt;
&lt;br /&gt;
Wherever we talk about a plot writer on this page, we&#039;re also referring to their team if they are part of one. &lt;br /&gt;
&lt;br /&gt;
==Plot Support==&lt;br /&gt;
The [[plot support]] team is a central team whose core job is to help the writers run the plot they have created. There are several steps involved in producing plot at an event and we realize that some writers or teams will not feel enthusiastic or capable of doing them all.&lt;br /&gt;
&lt;br /&gt;
You can&#039;t divest yourself of the responsibility for a plot - it&#039;s still down to the writer to ensure that their plot runs, but you can get help with any stage of the process. The plot support team includes people who are experienced with costume and props and can help advise you how to source the things you need for your plot. They are familiar with our IT systems and can help you get the ribbons and items your plot needs as well as brief and debrief your plot. Some members of the team may be able to brief a plot for you - or just help you find NPCs to play the roles.&lt;br /&gt;
&lt;br /&gt;
Whatever you need to do to get your plot to run, the plot support team are here to help.&lt;br /&gt;
&lt;br /&gt;
==Ten Steps==&lt;br /&gt;
We&#039;ve divided the plot creation process into ten steps and laid them out in a rough sequential order for ease of reading. All writers need to follow the process, but individual writers can work through the steps in the order that suits them best. Some writers like to buy a beautiful prop and create a plot around that; some writers will want to get the basics of their plot approved before spending time putting it on the wiki.&lt;br /&gt;
&lt;br /&gt;
==Stage 1 - Write Some Plot==&lt;br /&gt;
Any member of crew who wants to get involved in writing plot for Empire events is welcome to do so. Experience can help, but it is far from essential and a good knowledge of the setting is likely to be just as useful as a decade of experience writing plot for other games. What is essential is to make sure that you read the [[plot style guide]] first. We hope that you will also find the [[plot tools]] invaluable for giving you ideas and showing you elements of the setting you can use to turn those ideas into plots.&lt;br /&gt;
&lt;br /&gt;
The best members of the plot support team to talk to about your plot are Andy Rafferty and Matt Pennington. Both have lots of experience creating plot for large events and Andy is the ultimate authority for questions about the Empire setting. &lt;br /&gt;
&lt;br /&gt;
==Stage 2 - Put it on the Wiki==&lt;br /&gt;
We have a single central platform for plot - the [http://www.profounddecisions.co.uk/empireplotwiki/Main_Page plot wiki]. Before you can attempt to run your plot at an event, you must have documented the plot on its own page on the plot wiki. You can&#039;t get final approval for any plot until this is done.&lt;br /&gt;
&lt;br /&gt;
Most members of the plot support team will be able to help you use the plot wiki. If you are having a specific problem then [mailto:aquarion@profounddecisions.co.uk Aquarion] (Nicholas Avenell) is the best person to talk to.&lt;br /&gt;
&lt;br /&gt;
===NPC Stats===&lt;br /&gt;
You need to include stats for any NPCs or monsters that are needed for your plot. You can specify the individual skills an NPC has or just give a general description (e.g. 8 pt magician) to indicate the rough things you want. It is very rare in Empire for a plot to need an NPC to be particularly powerful but if it is essential then you must itemize their individual skills.&lt;br /&gt;
&lt;br /&gt;
If you need stats for a monster for a quest or battle, then the best thing to do is to choose a standard creature from the bestiary on the plot wiki. If there is nothing on the wiki that suits your purpose then you can create a new creature, but if you do this then we will need to check it for consistency with the setting and to ensure the creature&#039;s stats are play balanced.&lt;br /&gt;
&lt;br /&gt;
===Ribbons, Rituals and Items===&lt;br /&gt;
If your plot requires any game items, like magical items, potions, herbs, mana crystals, coins, resources or bourse resources, then you need to specify these on the page for your plot on the wiki. A sensible amount of resources to include for a small plot is equivalent to the amount of resources a player would get after one downtime; 10 ingots, 7 mana crytals, 14 herbs or 9 crowns. A bigger plot might include twice as many resources or substitute some resources for potions and magical items.&lt;br /&gt;
&lt;br /&gt;
If your plot needs one or more magical items then the best thing to do is to pick suitable items from the [http://www.profounddecisions.co.uk/empire-wiki/Magic_Items standard list] on the player wiki. If there is nothing on the wiki that suits your purpose then you can create a rare or unique item, but if you do this then you will have to specify clearly what you want the item to do. We cannot check, approve, and produce a magical item unless we know what you are proposing.&lt;br /&gt;
&lt;br /&gt;
There is a similar process to go through if your plot involves one or more [http://www.profounddecisions.co.uk/empire-wiki/Ritual_list rituals]. If the NPCs are performing a ritual, or have already done so, then the best thing to do is to pick suitable rituals from the standard list on the player wiki. If there is nothing suitable then you can create a new ritual, but as with magical items, you must specify clearly what the ritual will do.&lt;br /&gt;
&lt;br /&gt;
===Divination Responses===&lt;br /&gt;
When your plot is in the field, it will be interrogated by the players. They will use the tools at their disposal, usually divination rituals, to find out more information about your plot. Players ritual are handled by the field refs - who will process it and then radio the plot support team for an answer.&lt;br /&gt;
&lt;br /&gt;
If you are available (in the plot room or on a radio) - then the plot support team will pass the request to you. If you are not available then the team will create a response to the ritual using the details provided in your plot brief. The more detail here - the easier it will be for them to create the response you would want. &lt;br /&gt;
&lt;br /&gt;
Common Rituals that the players will cast to find out more are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Swim_Leviathan&#039;s_Depth Swim Leviathan&#039;s Depth] - Allows them to ask Leviathan why something is happening.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Bright_Lantern_of_Ophis Bright Lantern of Ophis] - Allows them to analyze a magical effect.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/The_Eye_of_the_High_Places The Eye of the High Places] - Allows them to analyze magical effects in a large area.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Eyes_of_the_Sun_and_Moon Eyes of the Sun and Moon] - Tells them about military forces in a territory.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Shadowed_Glass_of_Sung Shadowed Glass of Sung] and [http://www.profounddecisions.co.uk/empire-wiki/Clear_Lens_of_the_Eternal_River Clear Lens of the Eternal River] - Analyze an area for clues. These rituals are most useful on a quest but might be used to explore any location or &#039;scene&#039; where something has happened.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Skein_of_Years Skein of Years] - Explores the past history of a ribboned item.&lt;br /&gt;
&lt;br /&gt;
==Stage 3 - Get it Approved==&lt;br /&gt;
Your plot &#039;&#039;&#039;must&#039;&#039;&#039; be approved by the plot support team before it can run at an event. To approve a plot we need to check that it is consistent with the existing setting - the campaign &#039;&#039;and&#039;&#039; the rules, and that it follows the plot style guidelines. It is good practice to chat to the plot support team about any unusual elements, new parts of the setting, new rules, etc as soon as possible. The earlier that we can give you feedback on your plot, the easier it will be to make sure that it is approved without any problems.&lt;br /&gt;
&lt;br /&gt;
Although you can get a green light from the plot support team to develop a plot we can&#039;t provide final approval until we all the details are fully documented on the wiki. To get your plot approved you &#039;&#039;must&#039;&#039; proactively approach the plot support team and ask them to approve your plot for you. You may need to speak to multiple depending on what elements you have included in your plot.&lt;br /&gt;
&lt;br /&gt;
===The Setting===&lt;br /&gt;
The members of the team to talk to about the setting are Andy Raff and Matt Pennington. The best way to get Matt is to email him, the best way to get Andy is to PM him or post on the [https://www.facebook.com/groups/EmpirePlot/ Empire plot Facebook group]. If you have a skype account (or can make one) then you can grab both Matt and Andy on skype and discuss your plot with them. It is much quicker to get plot approved this way, as you can quickly explain your plot and talk through any difficult elements. It is also much easier to provide feedback this way.&lt;br /&gt;
&lt;br /&gt;
===The Rules===&lt;br /&gt;
Graeme Jamieson and Nicholas Taylor are the best people to talk to about any part of your plot that involves unusual rules such as non-standard magical items, rituals or creatures that are not in the bestiary on the wiki. You can contact them both by [mailto:empire.rules@profounddecisions.co.uk email] or by posting on the Empire plot facebook group.&lt;br /&gt;
&lt;br /&gt;
==Stage 4 - Costume and Props==&lt;br /&gt;
Profound Decisions have a large wardrobe of basic costume, including weapons and armour. If your plot needs specific costume or props then you will need to source these. The best place to try and do this is on the [https://www.facebook.com/groups/243111769153902/ Empire sewing circle Facebook group]. This group contains capable volunteers who make costume for Profound Decisions as well as helping us source new items.&lt;br /&gt;
&lt;br /&gt;
If we need to pay a professional to make an item then the starting point is to see if one of the existing professionals who work with Profound Decisions can do the job for you. Folks like Sean Maguire, Darren Stocker, Andy Rimmer, and Mandala all make weapons, Doug Strand makes leather goods and Rosemary Warner and Esther Reeves both make costume. If these people can&#039;t help then consider the traders who trade at our events, all of whom are likely to be helpful.&lt;br /&gt;
&lt;br /&gt;
Each writer, or writing team, will be allocated their own budget by Matt Pennington. This budget is for the four Empire events for that year and it is up to you how you allocate it for the plots you are developing and running for that year. It will be allocated based on your track record of running plot at Empire - the more plot you run, the more budget you&#039;ll get. If you don&#039;t spend all your budget then you can carry it over to the next year.&lt;br /&gt;
&lt;br /&gt;
The best people from plot support to talk to about our existing costume stores are Vicky (Victoria O&#039;connell) or Leah Tardival. Both will also be able to give advice on what sort of costumes and props you might need, what they might need to look like and where to go to order them.&lt;br /&gt;
&lt;br /&gt;
==Stage 5 - Makeup and Prosthetics==&lt;br /&gt;
Empire has a dedicated make-up team that is led by Agnes Eklund. The team have an existing store of make-up and basic prosthetics and has experience making and ordering new prosthetics. If your plot requires only standard make-up, for example orcs or characters with lineage then Agnes&#039; team will usually be able to handle this for you without much warning provided they are free. If your plot requires new prosthetics or a complex make-up job then it is essential that you talk to Agnes early about your needs if you want her team to be able to help you at the event.&lt;br /&gt;
&lt;br /&gt;
With multiple writers, the make-up team are always in demand, but they are especially busy preparing for the big battles on Saturday and Sunday morning. It is essential to avoid time-tabling a complex make-up effect for this time unless you have special dispensation directly from Agnes to do so.&lt;br /&gt;
&lt;br /&gt;
==Stage 6 - Timetabling your Plot==&lt;br /&gt;
Once your plot has received final approval, then you need to add it to the plot timetable for an event. The timetable will be a google spreadsheet that all the writers and members of plot support have access to. The critical element when timetabling plot is to ensure that there are sufficient NPCs available.&lt;br /&gt;
&lt;br /&gt;
NPCs on the timetable are allocated on a first come first served basis. It is best to get your plot written and approved early so that you can add it to the timetable. If your plot needs NPCs but the timetable is already full, then you will have to wait until the next event to run the plot. If the plot requires a quest slot then you will need to indicate this by writing the plot against one of the available quest slots on the spreadsheet.&lt;br /&gt;
&lt;br /&gt;
Your plot may not require any NPCs from the pool in the plot room. For example, there are existing NPCs that you may be able to make use of in your plot, such as the bards, civil servants, egregores, and magistrates. If this is the case then you can run your plot at any time, but it must still be timetabled, so that we can see when the plot is running. Please add it to the appropriate column on the spreadsheet and leave the NPC requirement blank.&lt;br /&gt;
&lt;br /&gt;
You will need to make your best estimate of how many hours your NPCs will be out for. If your estimate is too short it will cause problems for other writers, but too long will mean your NPCs have nothing to do once they return to the plot room. Chessy (Michelle Taylor) is the best person from plot support to talk if you need help timetabling your plot.&lt;br /&gt;
&lt;br /&gt;
For more detailed instructions on filling in the plot timetable successfully, see [[Plot Timetable Instructions]].&lt;br /&gt;
&lt;br /&gt;
==Stage 7 - Assigning NPCs==&lt;br /&gt;
You can leave assigning NPCs to your plot to the day of the event. If you have timetabled your plot correctly then the NPCs you need should be ready to play the role at the appropriate time in the plot room. You can take them to one side, get them briefed, and then send them out.&lt;br /&gt;
&lt;br /&gt;
If you want specific individuals to play NPC roles for you in one of your plots, then you&#039;ll need to chat to them to arrange that. We have a large pool of volunteers who NPC full time at events who are organized into teams of approximately five. If you need a small group of NPCs then you can chat to the team leader. If you just need one or two people then it is best to speak to them direct. It is wise to check that any individual you speak to has not agreed to be in another plot that is running at the same time.&lt;br /&gt;
&lt;br /&gt;
Assigning NPCs in advance can be very effective. It means you can pick people who are familiar with the role or at least that part of the setting. You can give them the brief before the event, making things much quicker on the day and you may well find your plot benefits from allowing them to have some input and development on the role.&lt;br /&gt;
&lt;br /&gt;
Fluff (Ben Dixon) or Vicky (Victoria O&#039;Connell) are the best people from the plot support team to provide help with assigning NPCs either in advance or on the day.&lt;br /&gt;
&lt;br /&gt;
==Stage 8 - Briefing NPCs==&lt;br /&gt;
Your NPCs will need to be briefed before they can enact your plot. Written briefs are incredibly useful, as they provide invaluable documentation and help speed up briefing before the event and on the day. However you don&#039;t need to produce a full written brief if that is not your style, provided that your plot write up includes the essential details.&lt;br /&gt;
&lt;br /&gt;
Fluff (Ben Dixon) or Vicky (Victoria O&#039;Connell) are the best people from the plot support team to help with briefing NPCs on the day.&lt;br /&gt;
&lt;br /&gt;
==Stage 9 - Debriefing NPCs==&lt;br /&gt;
When your NPCs return to the plot room they will be asked by the plot support team to put a debrief of their plot on to the plot wiki. The debriefs are added using the debrief button provided by the plot template which appears on your wiki page. If you need specific questions answered by the NPCs then you will need to ensure that you are there when the NPCs get back and debrief the plot.&lt;br /&gt;
&lt;br /&gt;
For Quests the Skirmish Team will provide an overall Quest debrief in addition to any specific details provided by the NPCs&lt;br /&gt;
&lt;br /&gt;
Debriefing is important because it allows us to track what plots ran and what the outcomes were. It is critically important for game consistency that we get good quality debriefs. Everyone involved in the plot process, writers, plot support, and NPCs should be aware of the importance of getting good debriefs.&lt;br /&gt;
&lt;br /&gt;
==Stage 10 - Player Follow-up==&lt;br /&gt;
The Empire campaign specifically prohibits free text downtime - players are &#039;&#039;prohibited&#039;&#039; from trying to follow up a plot in downtime. It is worth bearing this in mind when writing a plot.&lt;br /&gt;
&lt;br /&gt;
However there are things the players can do to chase a plot has left the field. The most common are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Call_Winged_Messenger Call Winged Messenger] - Send a message to a named NPC.&lt;br /&gt;
* Create a missive to an Eternal - Send a message to a named Eternal which has provided them a way to do so - e.g. Missive to Sadogua. &lt;br /&gt;
** If the Eternal you are working with does not currently have a defined communication mechanism, and you want the players to be able to communicate with them, you will need to give one out with your plot - this might be an item that gives them a one-shot ability to send a message, an arcane projection which allows them to send a ritual message, or if you are confident that you will be able to support communication with this Eternal over the long term, a ritual text of such a ritual or a longer-duration item that lets them send multiple messages.&lt;br /&gt;
&lt;br /&gt;
These requests will come to a field ref - who will process the request and then refer it back to the plot support team.&lt;br /&gt;
&lt;br /&gt;
The plot support team will attempt to identify the plot writer best suited to deal with any player follow-up. Missives sent to eternals and letters sent to NPCs by winged messenger will be put in the post-board in plot. There is a box for each plot team where they can collect their post from. Unidentified plot will be added to a single box marked &amp;quot;unknown&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you find a piece of plot follow-up in your box that is nothing to do with any of your plots, then please move it to the &amp;quot;unknown&amp;quot; box. Plot support will empty this box after the event and try to chase it up with the whole plot team using the Facebook writers group.&lt;br /&gt;
&lt;br /&gt;
Players may also commission a [http://www.profounddecisions.co.uk/empire-wiki/Historical_research historical research] request through the Imperial Senate. This results in a report collated by NPC civil servants who spend the period between events trawling archives and libraries all over the Empire. Some research requests will find no useful information, but you may be asked to write a research request result related to one of your plots, or to provide enough details that someone else can write one. A research request is a useful tool because it allows you to help players drive your plot forward, and can be used to reveal additional information about the background; point to a quest or unexpected avenue to pursue the quest; or even provide leads to an entirely new plot, depending on the nature of the research.&lt;br /&gt;
&lt;br /&gt;
==Contact Details==&lt;br /&gt;
* [https://www.facebook.com/Hobbes00uk Facebook Matt Pennington] or [mailto:matt@profounddecisions.co.uk matt@profounddecisions.co.uk] &lt;br /&gt;
* [https://www.facebook.com/andy.raff.1?fref=ts&amp;amp;ref=br_tf Facebook Andy Raff]&lt;br /&gt;
&lt;br /&gt;
{{Plot Further Reading}}&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Nilus&amp;diff=791</id>
		<title>Nilus</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Nilus&amp;diff=791"/>
		<updated>2014-07-17T11:21:05Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Created page with &amp;quot;Aquarion&amp;#039;s Civil Servant. Full biography and plot hooks at [http://www.profounddecisions.co.uk/empireplotwiki/Character:Nilus the plot wiki]&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Aquarion&#039;s Civil Servant. Full biography and plot hooks at [http://www.profounddecisions.co.uk/empireplotwiki/Character:Nilus the plot wiki]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=790</id>
		<title>Civil servants</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=790"/>
		<updated>2014-07-17T11:18:09Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Institutional Civil Servants */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[Category:Civil Service]]&lt;br /&gt;
&lt;br /&gt;
==Institutional Civil Servants==&lt;br /&gt;
These civil servants are linked to specific Imperial Institutions to ensure their smooth operation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Civil Servant&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Institutions&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| [[Adeta]] || Brass Coast || Sam Sutton || Head of Civil Service&lt;br /&gt;
|-&lt;br /&gt;
| [[Abronsius|Chancellor Abronsius Eldenheart]] || Urizen || Tom Francis || Academy&lt;br /&gt;
|- &lt;br /&gt;
| [[Mila Baraslava]] || Varushka || Kate Forster || Synod / Senate / Hub Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[John of Meade]] || Marches || Harry Harrold || Senate &lt;br /&gt;
|-&lt;br /&gt;
| [[Angelo|Angelo i Cenezia i Riqueza]] || Brass Coast || Daniel Williams || Synod / Historical Research&lt;br /&gt;
|-&lt;br /&gt;
| [[Merlot]] || League || Paul Wilder || Elections Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[Khaytanus Everwatch]] || Urizen || James Littlewood || Conclave / Academy&lt;br /&gt;
|-&lt;br /&gt;
| [[Pavel|Pavel Gregorivitch Milyukov]] || Varushka || Liam Spinage || Military Council &lt;br /&gt;
|-&lt;br /&gt;
| [[Marta|Marta Vaskovich Kovar]] || Varushka || Elinor Kershaw || Bourse / Academy &lt;br /&gt;
|-&lt;br /&gt;
| [[Nilus]] || Urizen || Aquarion || Senate / Audit&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Imperial Magistracy==&lt;br /&gt;
These civil servants co-ordinate the militia and are responsible for administering trials and Imperial justice. They are often found near the Hub.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
| &#039;&#039;&#039;Magistrate&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| [[Karkovitch|Stanislav Karkovich]] || Varushka || Jon Creek || Criminal / Constitutional / Religious law&lt;br /&gt;
|-&lt;br /&gt;
| [[Avedon|Avedon de Remourics]] || Dawn || Oliver Facey || Criminal / Religious Law&lt;br /&gt;
|-&lt;br /&gt;
| [[Marchello|Marchello Murchev]] || League || Mike Pye || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Grimmer|Grimmer Reinholz]] || Wintermark || Martin Verran || General &lt;br /&gt;
|-&lt;br /&gt;
| [[John Upwold]] || Marches || Richard Squires || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Gideon]] || Highguard || Tom Butterworth || General&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Ancilliary Civil Servants==&lt;br /&gt;
These individual are not always present in the field at Anvil but may come to the field to deal with specific tasks:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Name&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| Abraham || Highguard || Matt Pennington || Constitutional Court&lt;br /&gt;
|-&lt;br /&gt;
| The Auctioneer || Marches || Adam Buxton || Auctioneer / Bourse&lt;br /&gt;
|- &lt;br /&gt;
| Barak of Haros || Highguard || David Sheridan || Past Life Visions &lt;br /&gt;
|- &lt;br /&gt;
| Wylfa Bechod || Navarr || Dom Carroll || Past Life Visions&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=789</id>
		<title>Plot creation process</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=789"/>
		<updated>2014-07-17T07:54:44Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
This page is designed to help the writers - and everyone involved with creating and running plot at Empire understand what the process is and how it works.&lt;br /&gt;
&lt;br /&gt;
Producing plot for a large game is a difficult process. What works well for a small game with two writers and thirty players cannot be scaled to thirty writers and 2000 participants. We need to have a central process for organizing costume, NPCs, props, ribbons for items, debriefs for NPCs. Otherwise - when you come to run your plot requiring 40 NPCs to dress in Brass Coast costume for a quest - you will discover that all the NPCs are out, all the Brass Coast costume is out and all the quest slots are filled.&lt;br /&gt;
&lt;br /&gt;
Please make every effort to work with the process. If you are having problems talk to any of the people involved in managing the process and we will try and help sort out the problems for you. Please do not try and bypass the process.&lt;br /&gt;
&lt;br /&gt;
==Stage 1 - Write Some Plot==&lt;br /&gt;
You can write some plot at any time and chat to other people in PD about elements of it. You should look at your plot and ask yourself sensible questions about who you might want to discuss the plot with:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Plot Actuation (Kol, Liza)&#039;&#039;&#039; - Is the plot going to need a lot of people, take a long time to run, or need quest slots?&lt;br /&gt;
* &#039;&#039;&#039;Campaign (Andy)&#039;&#039;&#039; - Does the plot need new campaign elements adding to support it?&lt;br /&gt;
* &#039;&#039;&#039;Costume (Pru)&#039;&#039;&#039; - Does the plot need any specific props or costume?&lt;br /&gt;
* &#039;&#039;&#039;Prosthetics (Mim)&#039;&#039;&#039; - Does the plot need any specific prosthetics?&lt;br /&gt;
* &#039;&#039;&#039;Plot Writers (All writers)&#039;&#039;&#039; - Does the plot impact or overlap with other plots being written/run?&lt;br /&gt;
* &#039;&#039;&#039;Skirmish Team (Rich, James, Emma)&#039;&#039;&#039; - Can the plot be run as a quest, does it need pyros, smoke or lighting?&lt;br /&gt;
&lt;br /&gt;
You don&#039;t have to talk to anyone at this stage, but chatting informally to people will help get guidance with the plot and avoid problems later.&lt;br /&gt;
&lt;br /&gt;
==Stage 2 - Put it on the Wiki==&lt;br /&gt;
You need to type it up and put it on the wiki. We need a single central platform for plot - and the [http://www.profounddecisions.co.uk/empireplotwiki/Main_Page plot wiki] is it. We realize the plot wiki does not fit everyone - but we can&#039;t operate a different process for each writer - that way madness lies. So... the plot wiki is the next stage.&lt;br /&gt;
&lt;br /&gt;
If you&#039;re struggling to use the plot wiki then talk to anyone of the IT literate folk - other wiki users, Andy, Aquarion - anyone and we&#039;ll help as much as we can. If you really can&#039;t use the wiki, see if you can team up with someone who can use the wiki and see if they can help you get it on the wiki.&lt;br /&gt;
&lt;br /&gt;
On the page for your plot you need to add the following text:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{PlotThread|team=Team Farscape|author=Chris Edwards|name=Deal with the Devil|status=Draft}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Substitute your plot team name, your name and the plot name for the above obviously.&lt;br /&gt;
&lt;br /&gt;
At this stage your plot is still informal - a &amp;quot;stub&amp;quot; effectively. No-one is going to look at it, approve it, run it, or even allow it to be run. It is on the wiki so that you can share it with people, get input if you want it - and critically so you can prepare it for the next stage. If you want feedback on the plot then it is down to you to ask people for that feedback. &lt;br /&gt;
&lt;br /&gt;
===Signs and Portents===&lt;br /&gt;
You might want to add a vision to your plot at this time. [http://www.profounddecisions.co.uk/empire-wiki/Signs_and_Portents Signs and Portents] is a commonly cast ritual that draws from a pool of pre-prepared visions. By creating a vision to add to this pool you can foreshadow your plot, and include clues for the players to interpret that might help them interact with it. This is a great way to provide plot exposition or some context or introduction for your plot.&lt;br /&gt;
&lt;br /&gt;
===Include Vital Details===&lt;br /&gt;
If you have specific requirements for the plot - props, costumes, prosthetics, set dressing, manpower - anything specific that the plot needs to run, then make sure it is clearly identified in the page you have written for the plot. Use bullet points if possible - bullet point lists make &#039;&#039;everything&#039;&#039; better.&lt;br /&gt;
&lt;br /&gt;
For Quests there is a [http://www.profounddecisions.co.uk/empireplotwiki/Quest_Template template] to help you provide the information the Skirmish Team will need to run your quest in the way you want. Two key roles for Quests are: &lt;br /&gt;
&lt;br /&gt;
* the Hook - normally an NPC that tells the players when and where the quest is happening &lt;br /&gt;
* the Guide - an NPC that will liaise between the players and Plot Actuation or Skirmish Team i.e. the IC player wrangler (this could be the Nations Egregore or the Hook in many cases)&lt;br /&gt;
&lt;br /&gt;
When you are happy that your plot is complete and you are ready for it to run then you need tag the plot.&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right; width: 250px; margin: 10px; padding: 10px; border-width:5px; border-style:double; border-radius: 5px;&amp;quot;&amp;gt;&amp;lt;h3 style=&amp;quot;margin-top:0&amp;quot;&amp;gt;Deadline&amp;lt;/h3&amp;gt; You must submit your plot for approval 10 days before the Friday that the event begins. Plot submitted after this date will not be run at that event.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Stage 3 - Add Next Event and Awaiting Approval Tags==&lt;br /&gt;
You need to add two tags to your wiki page.&lt;br /&gt;
&lt;br /&gt;
The first should have the name of the next event - or the event that you want your plot to run at. The event names are defined by their sequence in the year and the year they are running. e.g. first event in 2013 is &amp;quot;E1-2013&amp;quot;.  The third event in 2014 is &amp;quot;E3-2014&amp;quot;&lt;br /&gt;
&lt;br /&gt;
To create a tag you add the following text anywhere to your page: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{Category:E3-2014}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This tag is used by the Plot Actuation team to find plot that may be running at the next event - so they can prepare a timetable - allocate NPCs, sort costume, etc, etc, etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- The second tag should say &amp;quot;Awaiting Approval&amp;quot; - the wiki code for this is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{Awaiting Approval}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt; --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can set this by changing the &amp;quot;Status&amp;quot; in the PlotThread text you added earlier, and you should change it to &amp;quot;Awaiting Approval&amp;quot;, like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{PlotThread|team=Team Farscape|author=Chris Edwards|name=Deal with the Devil|status=Awaiting Approval}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This tag is used by Matt and Andy so they can find your plot and check it for consistency with the campaign.&lt;br /&gt;
&lt;br /&gt;
==Stage 4 - Push for Approval==&lt;br /&gt;
You need to get your plot approved by Matt Pennington and Andy Raff. This process is driven by &#039;&#039;you&#039;&#039;, the writer.&lt;br /&gt;
&lt;br /&gt;
You need to drive this process as both Matt and Andy are scatterbrained and unable to manage time or projects. Basically just prod one of them repeatedly until it happens. An email to Matt is a good place to start, but regular prompting on Facebook is even more potent and difficult to ignore. The [https://www.facebook.com/#!/groups/EmpirePlot/ plot facebook group] is a good place to poke Andy Raff who spends too much time on Facebook. If you don&#039;t get a response, wait a day... then poke again. Feel free to cut and paste the link for the wiki page with your plot on it - and post that at Matt until he does the job.&lt;br /&gt;
&lt;br /&gt;
Matt is busy and responds to problems based on how much he is getting harassed to get them done. This description is not efficient or optimal but it is &#039;&#039;true&#039;&#039;. You will not annoy Matt by harassing him with &amp;quot;Check my Plot&amp;quot; requests - you will simply get your plot checked and approved faster...&lt;br /&gt;
&lt;br /&gt;
Once Matt or Andy has approved the plot - they will change the tag from &amp;quot;Awaiting Approval&amp;quot; to &amp;quot;Approved&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Plot Approval is a conveyor belt process initiated by you.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Request Approval&#039;&#039;&#039; - Email or PM Matt and Andy. &lt;br /&gt;
* &#039;&#039;&#039;24 hours later&#039;&#039;&#039; - send a second request if you have not had a response.&lt;br /&gt;
* &#039;&#039;&#039;48 hours after second request&#039;&#039;&#039; - issue Matt and Andy with a final demand.&lt;br /&gt;
* &#039;&#039;&#039;48 hours after the final demand&#039;&#039;&#039; - plot automatically approved.&lt;br /&gt;
&lt;br /&gt;
If you drive this process by prodding Matt and Andy then your plot will be approved within 5 days of being submitted. If Matt and Andy can&#039;t get their shit sorted and get you a response after your third message - then your plot gets automatically approved.&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right; width: 250px; margin: 10px; padding: 10px; border-width:5px; border-style:double; border-radius: 5px;&amp;quot;&amp;gt;&amp;lt;h3 style=&amp;quot;margin-top:0&amp;quot;&amp;gt;Bypassing the Process&amp;lt;/h3&amp;gt;&amp;lt;p&amp;gt;If you have a good source for costumes or props or a specific NPC you&#039;d like to use then talk to the relevant member of the plot room about your ideas. Plot actuation is a difficult job and they will appreciate the help.&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin-bottom:0;&amp;quot;&amp;gt;Please don&#039;t bypass the process and do it yourself - that causes major problems for other members of the team when they try and allocate NPCs, quest slots, ref ritual outcomes, etc. Talk to the plot actuation team - they are there to help you run your plot.&amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Stage 5 - Plot Actuation==&lt;br /&gt;
The Plot Actuation team will read through your plot and check it for missing elements that they need to run the plot. Potential missing elements are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Item Ribbons&#039;&#039;&#039; - If a plot needs a ribbon they need the precise details of what goes on the ribbon.&lt;br /&gt;
* &#039;&#039;&#039;NPC Stats&#039;&#039;&#039; - If an NPC needs notable stats they will need specifying.&lt;br /&gt;
&lt;br /&gt;
Once the Plot Actuation team have checked your plot and are ready to run it they will change the &amp;quot;Approved&amp;quot; category tag to &amp;quot;Running&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
When you see this tag appear then you know that your plot is timetabled to run - and that plot actuation team are going to ensure that sufficient costumes, props, and NPCs to run the plot. The plot actuation team have to balance the demands of all the plots being run over the weekend. They may discuss the requirements with you - but ultimately they have the final say on what resources can be allocated to a plot. If you are concerned that their estimation is not sufficient then discuss that with them.&lt;br /&gt;
&lt;br /&gt;
The Plot Actuation Team will finalize all the logistical arrangements that are required for your plot to run. If your plot needs resources, coin, cards or ribbons then they will prepare them. If the plot needs props, costumes, prosthetics or set-dressing - then the plot actuation team will sort them.&lt;br /&gt;
&lt;br /&gt;
==Stage 6 - Preparing the Timetable==&lt;br /&gt;
The Plot Actuation Team will prepare a timetable for all the plot that we are running out for an event. This will be a google document spreadsheet.&lt;br /&gt;
&lt;br /&gt;
Creating the spreadsheet is enormously hard work and takes a lot of time. There are a huge number of different variables that have to be juggled as plots are being sanctioned. At present the goal is to deliver the timetable for the 1pm Friday that the event starts. As the system improves, the Plot Actuation Team will endeavour to deliver the timetable earlier.&lt;br /&gt;
&lt;br /&gt;
==Stage 7 - Briefing NPCs==&lt;br /&gt;
You need to be ready to brief your NPCs for your plot. The plot actuation team prepare the things you need for your plot - but they will not brief and run your plot for you. So you will need to be present in the plot room 20 minutes before your plot is due to go out - otherwise it will not go out.&lt;br /&gt;
&lt;br /&gt;
Once you get to the plot room, liaise with a member of the plot actuation team and they will tell you who is monstering your plot. You must then brief the NPCs.&lt;br /&gt;
&lt;br /&gt;
This includes NPCs that are the Hook or specific NPCs on Quests. The Skirmish team will stat generic monsters and brief them with any details on your plot doc but you will need to give more detailed briefs for any specific NPCs in your Quest.&lt;br /&gt;
&lt;br /&gt;
Note the Hook for a quest is timetabled separately to the Quest and go out hours or even days before the quest, you will need to be there to brief both parts. If the Guide is not an Egregore or the Hook then they will need to be briefed at least an hour before the quest is due.&lt;br /&gt;
&lt;br /&gt;
==Stage 8 - In The Field==&lt;br /&gt;
When your plot is in the field, it will be interrogated by the players. They will use the tools at their disposal to find out more information about your plot. There are various rituals they can perform to find things out or to cause things to happen in response to your plot. These requests will come to a field ref - who will process the request and then refer it back to the plot actuation team.&lt;br /&gt;
&lt;br /&gt;
The plot actuation team will attempt to answer the question. If you are available (in the plot room or on a radio) - then they will pass the request to you. If you are not available then they will attempt to respond to the player action using the details provided in your plot brief. The more detail here - the easier it will be for them to respond in the way you want.&lt;br /&gt;
&lt;br /&gt;
Common Rituals that the players will cast to find out more are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Swim_Leviathan&#039;s_Depth Swim Leviathan&#039;s Depth] - Allows them to ask Leviathan why something is happening.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Bright_Lantern_of_Ophis Bright Lantern of Ophis] - Allows them to analyze a magical effect.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/The_Eye_of_the_High_Places The Eye of the High Places] - Allows them to analyze magical effects in a large area.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Eyes_of_the_Sun_and_Moon Eyes of the Sun and Moon] - Tells them about military forces in a territory.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Shadowed_Glass_of_Sung Shadowed Glass of Sung] and [http://www.profounddecisions.co.uk/empire-wiki/Clear_Lens_of_the_Eternal_River Clear Lens of the Eternal River] - Analyze an area for clues. These rituals are most useful on a quest but might be used to explore any location or &#039;scene&#039; where something has happened.&lt;br /&gt;
&lt;br /&gt;
==Stage 9 - Debriefing NPCs==&lt;br /&gt;
When your NPCs return to the plot room they will be asked by plot actuation to put a debrief on their plot on to the plot wiki. The debriefs are added using the debrief button provided by the plot template which appears on your wiki page. If you need specific questions answered by the NPCs then you will need to ensure that you are there when the NPCs get back and debrief the plot.&lt;br /&gt;
&lt;br /&gt;
For Quests the Skirmish Team will provide an overall Quest debrief in addition to any specific details provided by the NPCs&lt;br /&gt;
&lt;br /&gt;
Debriefing is important because it allows us to track what plots ran and what the outcomes were. It is critically important for game consistency that we get good quality debriefs. Everyone involved in the plot process, writers, plot actuation, and NPCs should be aware of the importance of getting good debriefs.&lt;br /&gt;
&lt;br /&gt;
==Stage 10 - Player Follow-up==&lt;br /&gt;
The Empire campaign specifically prohibits free text downtime - players are &#039;&#039;prohibited&#039;&#039; from trying to follow up a plot in downtime. It is worth bearing this in mind when writing a plot.&lt;br /&gt;
&lt;br /&gt;
However there are things the players can do to chase a plot has left the field. The most common are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Call_Winged_Messenger Call Winged Messenger] - Send a message to a named NPC.&lt;br /&gt;
* Create a missive to an Eternal - Send a message to a named Eternal&lt;br /&gt;
&lt;br /&gt;
These requests will come to a field ref - who will process the request and then refer it back to the plot actuation team.&lt;br /&gt;
&lt;br /&gt;
The plot actuation team will attempt to identify the plot writer best suited to deal with any player follow-up. Messages set to eternals and letters sent by winged messenger will be put in the post-board in plot. There is a box for each plot team where they can collect their post from. Unidentified plot will be added to a single box marked &amp;quot;unknown&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you find a piece of plot follow-up in your box that is nothing to do with any of your plots, then please move it to the &amp;quot;unknown&amp;quot; box. Plot Actuation team will empty this box after the event and try to chase it up with the whole plot team using the Facebook writers group.&lt;br /&gt;
&lt;br /&gt;
Players may also commission a [http://www.profounddecisions.co.uk/empire-wiki/Historical_research historical research] request through the Imperial Senate. This results in a report collated by NPC civil servants who spend the period between events trawling archives and libraries all over the Empire. Some research requests will find no useful information, but you may be asked to write a research request result related to one of your plots, or to provide enough details that someone else can write one. A research request is a useful tool because it allows you to help players drive your plot forward, and can be used to reveal additional information about the background; point to a quest or unexpected avenue to pursue the quest; or even provide leads to an entirely new plot, depending on the nature of the research.&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
The following summarizes the division of responsibilities in the process of creating, approving and running plot at Empire.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Write plot&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Add plot to wiki&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Make requirements clear&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Request appoval&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Approve plot&#039;&#039;&#039; - Matt and Andy&lt;br /&gt;
* &#039;&#039;&#039;Source costumes, props, prosthetics, set dressing&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Allocate NPCs, quest slots, vision tents&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Source resources, cards, coins, ribbons&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Timetable plot&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Brief NPCs&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Run Quests (including statting monsters)&#039;&#039;&#039; - Skirmish Team&lt;br /&gt;
* &#039;&#039;&#039;Respond to player action&#039;&#039;&#039; - the plot writer if available, otherwise Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Debrief NPCs&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Debrief Quests&#039;&#039;&#039; - Skirmish Team&lt;br /&gt;
* &#039;&#039;&#039;Allocate player follow-up&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
&lt;br /&gt;
==Contact Details==&lt;br /&gt;
* [https://www.facebook.com/Hobbes00uk Facebook Matt Pennington] or [mailto:matt@profounddecisions.co.uk matt@profounddecisions.co.uk] &lt;br /&gt;
* [https://www.facebook.com/andy.raff.1?fref=ts&amp;amp;ref=br_tf Facebook Andy Raff]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=784</id>
		<title>Plot creation process</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Plot_creation_process&amp;diff=784"/>
		<updated>2014-07-10T09:02:50Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Overview==&lt;br /&gt;
This page is designed to help the writers - and everyone involved with creating and running plot at Empire understand what the process is and how it works.&lt;br /&gt;
&lt;br /&gt;
Producing plot for a large game is a difficult process. What works well for a small game with two writers and thirty players cannot be scaled to thirty writers and 2000 participants. We need to have a central process for organizing costume, NPCs, props, ribbons for items, debriefs for NPCs. Otherwise - when you come to run your plot requiring 40 NPCs to dress in Brass Coast costume for a quest - you will discover that all the NPCs are out, all the Brass Coast costume is out and all the quest slots are filled.&lt;br /&gt;
&lt;br /&gt;
Please make every effort to work with the process. If you are having problems talk to any of the people involved in managing the process and we will try and help sort out the problems for you. Please do not try and bypass the process.&lt;br /&gt;
&lt;br /&gt;
==Stage 1 - Write Some Plot==&lt;br /&gt;
You can write some plot at any time and chat to other people in PD about elements of it. You should look at your plot and ask yourself sensible questions about who you might want to discuss the plot with:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Plot Actuation (Kol, Liza)&#039;&#039;&#039; - Is the plot going to need a lot of people, take a long time to run, or need quest slots?&lt;br /&gt;
* &#039;&#039;&#039;Campaign (Andy)&#039;&#039;&#039; - Does the plot need new campaign elements adding to support it?&lt;br /&gt;
* &#039;&#039;&#039;Costume (Pru)&#039;&#039;&#039; - Does the plot need any specific props or costume?&lt;br /&gt;
* &#039;&#039;&#039;Prosthetics (Mim)&#039;&#039;&#039; - Does the plot need any specific prosthetics?&lt;br /&gt;
* &#039;&#039;&#039;Plot Writers (All writers)&#039;&#039;&#039; - Does the plot impact or overlap with other plots being written/run?&lt;br /&gt;
&lt;br /&gt;
You don&#039;t have to talk to anyone at this stage, but chatting informally to people will help get guidance with the plot and avoid problems later.&lt;br /&gt;
&lt;br /&gt;
==Stage 2 - Put it on the Wiki==&lt;br /&gt;
You need to type it up and put it on the wiki. We need a single central platform for plot - and the [http://www.profounddecisions.co.uk/empireplotwiki/Main_Page plot wiki] is it. We realize the plot wiki does not fit everyone - but we can&#039;t operate a different process for each writer - that way madness lies. So... the plot wiki is the next stage.&lt;br /&gt;
&lt;br /&gt;
If you&#039;re struggling to use the plot wiki then talk to anyone of the IT literate folk - other wiki users, Andy, Aquarion - anyone and we&#039;ll help as much as we can. If you really can&#039;t use the wiki, see if you can team up with someone who can use the wiki and see if they can help you get it on the wiki.&lt;br /&gt;
&lt;br /&gt;
On the page for your plot you need to add the following text:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{PlotThread|team=Team Farscape|author=Chris Edwards|name=Deal with the Devil|status=Draft}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Substitute your plot team name, your name and the plot name for the above obviously.&lt;br /&gt;
&lt;br /&gt;
At this stage your plot is still informal - a &amp;quot;stub&amp;quot; effectively. No-one is going to look at it, approve it, run it, or even allow it to be run. It is on the wiki so that you can share it with people, get input if you want it - and critically so you can prepare it for the next stage. If you want feedback on the plot then it is down to you to ask people for that feedback. &lt;br /&gt;
&lt;br /&gt;
===Signs and Portents===&lt;br /&gt;
You might want to add a vision to your plot at this time. [http://www.profounddecisions.co.uk/empire-wiki/Signs_and_Portents Signs and Portents] is a commonly cast ritual that draws from a pool of pre-prepared visions. By creating a vision to add to this pool you can foreshadow your plot, and include clues for the players to interpret that might help them interact with it. This is a great way to provide plot exposition or some context or introduction for your plot.&lt;br /&gt;
&lt;br /&gt;
===Include Vital Details===&lt;br /&gt;
If you have specific requirements for the plot - props, costumes, prosthetics, set dressing, manpower - anything specific that the plot needs to run, then make sure it is clearly identified in the page you have written for the plot. Use bullet points if possible - bullet point lists make &#039;&#039;everything&#039;&#039; better.&lt;br /&gt;
&lt;br /&gt;
When you are happy that your plot is complete and you are ready for it to run then you need tag the plot.&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right; width: 250px; margin: 10px; padding: 10px; border-width:5px; border-style:double; border-radius: 5px;&amp;quot;&amp;gt;&amp;lt;h3 style=&amp;quot;margin-top:0&amp;quot;&amp;gt;Deadline&amp;lt;/h3&amp;gt; You must submit your plot for approval 10 days before the Friday that the event begins. Plot submitted after this date will not be run at that event.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Stage 3 - Add Next Event and Awaiting Approval Tags==&lt;br /&gt;
You need to add two tags to your wiki page.&lt;br /&gt;
&lt;br /&gt;
The first should have the name of the next event - or the event that you want your plot to run at. The event names are defined by their sequence in the year and the year they are running. e.g. first event in 2013 is &amp;quot;E1 - 2013&amp;quot;.  The third event in 2014 is &amp;quot;E3 - 2014&amp;quot;&lt;br /&gt;
&lt;br /&gt;
To create a tag you add the following text anywhere to your page: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{Category:E3 - 2014}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This tag is used by the Plot Actuation team to find plot that may be running at the next event - so they can prepare a timetable - allocate NPCs, sort costume, etc, etc, etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- The second tag should say &amp;quot;Awaiting Approval&amp;quot; - the wiki code for this is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{Awaiting Approval}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt; --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can set this by changing the &amp;quot;Status&amp;quot; in the PlotThread text you added earlier, and you should change it to &amp;quot;Awaiting Approval&amp;quot;, like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;box&amp;gt;&amp;lt;nowiki&amp;gt;{{PlotThread|team=Team Farscape|author=Chris Edwards|name=Deal with the Devil|status=Awaiting Approval}}&amp;lt;/nowiki&amp;gt;&amp;lt;/box&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This tag is used by Matt and Andy so they can find your plot and check it for consistency with the campaign.&lt;br /&gt;
&lt;br /&gt;
==Stage 4 - Push for Approval==&lt;br /&gt;
You need to get your plot approved by Matt Pennington and Andy Raff. This process is driven by &#039;&#039;you&#039;&#039;, the writer.&lt;br /&gt;
&lt;br /&gt;
You need to drive this process as both Matt and Andy are scatterbrained and unable to manage time or projects. Basically just prod one of them repeatedly until it happens. An email to Matt is a good place to start, but regular prompting on Facebook is even more potent and difficult to ignore. The [https://www.facebook.com/#!/groups/EmpirePlot/ plot facebook group] is a good place to poke Andy Raff who spends too much time on Facebook. If you don&#039;t get a response, wait a day... then poke again. Feel free to cut and paste the link for the wiki page with your plot on it - and post that at Matt until he does the job.&lt;br /&gt;
&lt;br /&gt;
Matt is busy and responds to problems based on how much he is getting harassed to get them done. This description is not efficient or optimal but it is &#039;&#039;true&#039;&#039;. You will not annoy Matt by harassing him with &amp;quot;Check my Plot&amp;quot; requests - you will simply get your plot checked and approved faster...&lt;br /&gt;
&lt;br /&gt;
Once Matt or Andy has approved the plot - they will change the tag from &amp;quot;Awaiting Approval&amp;quot; to &amp;quot;Approved&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Plot Approval is a conveyor belt process initiated by you.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Request Approval&#039;&#039;&#039; - Email or PM Matt and Andy. &lt;br /&gt;
* &#039;&#039;&#039;24 hours later&#039;&#039;&#039; - send a second request if you have not had a response.&lt;br /&gt;
* &#039;&#039;&#039;48 hours after second request&#039;&#039;&#039; - issue Matt and Andy with a final demand.&lt;br /&gt;
* &#039;&#039;&#039;48 hours after the final demand&#039;&#039;&#039; - plot automatically approved.&lt;br /&gt;
&lt;br /&gt;
If you drive this process by prodding Matt and Andy then your plot will be approved within 5 days of being submitted. If Matt and Andy can&#039;t get their shit sorted and get you a response after your third message - then your plot gets automatically approved.&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right; width: 250px; margin: 10px; padding: 10px; border-width:5px; border-style:double; border-radius: 5px;&amp;quot;&amp;gt;&amp;lt;h3 style=&amp;quot;margin-top:0&amp;quot;&amp;gt;Bypassing the Process&amp;lt;/h3&amp;gt;&amp;lt;p&amp;gt;If you have a good source for costumes or props or a specific NPC you&#039;d like to use then talk to the relevant member of the plot room about your ideas. Plot actuation is a difficult job and they will appreciate the help.&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;margin-bottom:0;&amp;quot;&amp;gt;Please don&#039;t bypass the process and do it yourself - that causes major problems for other members of the team when they try and allocate NPCs, quest slots, ref ritual outcomes, etc. Talk to the plot actuation team - they are there to help you run your plot.&amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Stage 5 - Plot Actuation==&lt;br /&gt;
The Plot Actuation team will read through your plot and check it for missing elements that they need to run the plot. Potential missing elements are:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Item Ribbons&#039;&#039;&#039; - If a plot needs a ribbon they need the precise details of what goes on the ribbon.&lt;br /&gt;
* &#039;&#039;&#039;NPC Stats&#039;&#039;&#039; - If an NPC needs notable stats they will need specifying.&lt;br /&gt;
&lt;br /&gt;
Once the Plot Actuation team have checked your plot and are ready to run it they will change the &amp;quot;Approved&amp;quot; category tag to &amp;quot;Running&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
When you see this tag appear then you know that your plot is timetabled to run - and that plot actuation team are going to ensure that sufficient costumes, props, and NPCs to run the plot. The plot actuation team have to balance the demands of all the plots being run over the weekend. They may discuss the requirements with you - but ultimately they have the final say on what resources can be allocated to a plot. If you are concerned that their estimation is not sufficient then discuss that with them.&lt;br /&gt;
&lt;br /&gt;
The Plot Actuation Team will finalize all the logistical arrangements that are required for your plot to run. If your plot needs resources, coin, cards or ribbons then they will prepare them. If the plot needs props, costumes, prosthetics or set-dressing - then the plot actuation team will sort them.&lt;br /&gt;
&lt;br /&gt;
==Stage 6 - Preparing the Timetable==&lt;br /&gt;
The Plot Actuation Team will prepare a timetable for all the plot that we are running out for an event. This will be a google document spreadsheet.&lt;br /&gt;
&lt;br /&gt;
Creating the spreadsheet is enormously hard work and takes a lot of time. There are a huge number of different variables that have to be juggled as plots are being sanctioned. At present the goal is to deliver the timetable for the 1pm Friday that the event starts. As the system improves, the Plot Actuation Team will endeavour to deliver the timetable earlier.&lt;br /&gt;
&lt;br /&gt;
==Stage 7 - Briefing NPCs==&lt;br /&gt;
You need to be ready to brief your NPCs for your plot. The plot actuation team prepare the things you need for your plot - but they will not brief and run your plot for you. So you will need to be present in the plot room 20 minutes before your plot is due to go out - otherwise it will not go out.&lt;br /&gt;
&lt;br /&gt;
Once you get to the plot room, liaise with a member of the plot actuation team and they will tell you who is monstering your plot. You must then brief the NPCs.&lt;br /&gt;
&lt;br /&gt;
==Stage 8 - In The Field==&lt;br /&gt;
When your plot is in the field, it will be interrogated by the players. They will use the tools at their disposal to find out more information about your plot. There are various rituals they can perform to find things out or to cause things to happen in response to your plot. These requests will come to a field ref - who will process the request and then refer it back to the plot actuation team.&lt;br /&gt;
&lt;br /&gt;
The plot actuation team will attempt to answer the question. If you are available (in the plot room or on a radio) - then they will pass the request to you. If you are not available then they will attempt to respond to the player action using the details provided in your plot brief. The more detail here - the easier it will be for them to respond in the way you want.&lt;br /&gt;
&lt;br /&gt;
Common Rituals that the players will cast to find out more are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Swim_Leviathan&#039;s_Depth Swim Leviathan&#039;s Depth] - Allows them to ask Leviathan why something is happening.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Bright_Lantern_of_Ophis Bright Lantern of Ophis] - Allows them to analyze a magical effect.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/The_Eye_of_the_High_Places The Eye of the High Places] - Allows them to analyze magical effects in a large area.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Eyes_of_the_Sun_and_Moon Eyes of the Sun and Moon] - Tells them about military forces in a territory.&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Shadowed_Glass_of_Sung Shadowed Glass of Sung] and [http://www.profounddecisions.co.uk/empire-wiki/Clear_Lens_of_the_Eternal_River Clear Lens of the Eternal River] - Analyze an area for clues. These rituals are most useful on a quest but might be used to explore any location or &#039;scene&#039; where something has happened.&lt;br /&gt;
&lt;br /&gt;
==Stage 9 - Debriefing NPCs==&lt;br /&gt;
When your NPCs return to the plot room they will be asked by plot actuation to put a debrief on their plot on to the plot wiki. The debriefs are added using the debrief button provided by the plot template which appears on your wiki page. If you need specific questions answered by the NPCs then you will need to ensure that you are there when the NPCs get back and debrief the plot.&lt;br /&gt;
&lt;br /&gt;
Debriefing is important because it allows us to track what plots ran and what the outcomes were. It is critically important for game consistency that we get good quality debriefs. Everyone involved in the plot process, writers, plot actuation, and NPCs should be aware of the importance of getting good debriefs.&lt;br /&gt;
&lt;br /&gt;
==Stage 10 - Player Follow-up==&lt;br /&gt;
The Empire campaign specifically prohibits free text downtime - players are &#039;&#039;prohibited&#039;&#039; from trying to follow up a plot in downtime. It is worth bearing this in mind when writing a plot.&lt;br /&gt;
&lt;br /&gt;
However there are things the players can do to chase a plot has left the field. The most common are:&lt;br /&gt;
&lt;br /&gt;
* [http://www.profounddecisions.co.uk/empire-wiki/Call_Winged_Messenger Call Winged Messenger] - Send a message to a named NPC.&lt;br /&gt;
* Create a missive to an Eternal - Send a message to a named Eternal&lt;br /&gt;
&lt;br /&gt;
These requests will come to a field ref - who will process the request and then refer it back to the plot actuation team.&lt;br /&gt;
&lt;br /&gt;
The plot actuation team will attempt to identify the plot writer best suited to deal with any player follow-up. Messages set to eternals and letters sent by winged messenger will be put in the post-board in plot. There is a box for each plot team where they can collect their post from. Unidentified plot will be added to a single box marked &amp;quot;unknown&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you find a piece of plot follow-up in your box that is nothing to do with any of your plots, then please move it to the &amp;quot;unknown&amp;quot; box. Plot Actuation team will empty this box after the event and try to chase it up with the whole plot team using the Facebook writers group.&lt;br /&gt;
&lt;br /&gt;
Players may also commission a [http://www.profounddecisions.co.uk/empire-wiki/Historical_research historical research] request through the Imperial Senate. This results in a report collated by NPC civil servants who spend the period between events trawling archives and libraries all over the Empire. Some research requests will find no useful information, but you may be asked to write a research request result related to one of your plots, or to provide enough details that someone else can write one. A research request is a useful tool because it allows you to help players drive your plot forward, and can be used to reveal additional information about the background; point to a quest or unexpected avenue to pursue the quest; or even provide leads to an entirely new plot, depending on the nature of the research.&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
The following summarizes the division of responsibilities in the process of creating, approving and running plot at Empire.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Write plot&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Add plot to wiki&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Make requirements clear&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Request appoval&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Approve plot&#039;&#039;&#039; - Matt and Andy&lt;br /&gt;
* &#039;&#039;&#039;Source costumes, props, prosthetics, set dressing&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Allocate NPCs, quest slots, vision tents&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Source resources, cards, coins, ribbons&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Timetable plot&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Brief NPCs&#039;&#039;&#039; - the plot writer&lt;br /&gt;
* &#039;&#039;&#039;Respond to player action&#039;&#039;&#039; - the plot writer if available, otherwise Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Debrief NPCs&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
* &#039;&#039;&#039;Allocate player follow-up&#039;&#039;&#039; - Plot Actuation Team&lt;br /&gt;
&lt;br /&gt;
==Contact Details==&lt;br /&gt;
* [https://www.facebook.com/Hobbes00uk Facebook Matt Pennington] or [mailto:matt@profounddecisions.co.uk matt@profounddecisions.co.uk] &lt;br /&gt;
* [https://www.facebook.com/andy.raff.1?fref=ts&amp;amp;ref=br_tf Facebook Andy Raff]&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=MediaWiki:Loginprompt&amp;diff=707</id>
		<title>MediaWiki:Loginprompt</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=MediaWiki:Loginprompt&amp;diff=707"/>
		<updated>2014-04-29T13:53:17Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You must have cookies enabled to log in to {{SITENAME}}.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--div class=&amp;quot;alert&amp;quot;&amp;gt;Note: Use your [http://www.profounddecisions.co.uk Profound Decisions website] username and password to access this wiki&amp;lt;/div--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=MediaWiki:Loginprompt&amp;diff=706</id>
		<title>MediaWiki:Loginprompt</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=MediaWiki:Loginprompt&amp;diff=706"/>
		<updated>2014-04-29T13:51:52Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Created page with &amp;quot;You must have cookies enabled to log in to {{SITENAME}}.  &amp;lt;div class=&amp;quot;alert&amp;quot;&amp;gt;Note: Use your [http://www.profounddecisions.co.uk Profound Decisions website] username and passwo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You must have cookies enabled to log in to {{SITENAME}}.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;alert&amp;quot;&amp;gt;Note: Use your [http://www.profounddecisions.co.uk Profound Decisions website] username and password to access this wiki&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Photography&amp;diff=703</id>
		<title>Photography</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Photography&amp;diff=703"/>
		<updated>2014-04-29T09:04:15Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTITLE__&lt;br /&gt;
{{Stub}}&lt;br /&gt;
&lt;br /&gt;
==Guidelines for non-photography crew==&lt;br /&gt;
&lt;br /&gt;
==Wiki Imagery==&lt;br /&gt;
&lt;br /&gt;
===Copyrighted Material===&lt;br /&gt;
&lt;br /&gt;
It should go without saying that we do not want imagery on the wiki that we do not have permission to use. The default assumption should be that you cannot use an image unless you explicitly have evidence to show that you can. Merely being available on the internet does not make an image &#039;fair game&#039; for use on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There are several ways that you can ensure an image is ok for use on the wiki:&#039;&#039;&#039;&lt;br /&gt;
# Use an image from a crew photographer. Anyone who edits the wiki can email photography crew to get access to a library of images suitable for wiki use. This has the benefit of filling the wiki full of images from the game world.&lt;br /&gt;
# Obtain permission from the photographer and display their information within a special category page on the wiki. All images from that photographer should then have the standard accreditation template inserted.&lt;br /&gt;
# Use an image with the correct [http://creativecommons.org creative commons] license. Crucially we must use creative commons licenses that allow for commercial use. In addition all images with creative commons licenses must be attributed properly. Some websites have the ability to search images tagged with creative commons licenses - [https://www.flickr.com/search/advanced/ Flickr is particularly good for this]. Make sure you also tick the &#039;find content to use commercially&#039; box. However a little common sense is required here - not all images tagged with a creative commons license will have been done so legally. Just because you take a picture of something in a museum for example, does not mean that you can distribute it for commercial use (check the individual terms of the entrance ticket).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Images that are not ok to use on the wiki:&#039;&#039;&#039; &lt;br /&gt;
# Images where you have no idea of the author.&lt;br /&gt;
# Images taken as screenshots from film and TV.&lt;br /&gt;
# Creative Commons images that display the icon showing a dollar sign with a line through. These images are not ok for commercial use.&lt;br /&gt;
&lt;br /&gt;
===Attribution===&lt;br /&gt;
&lt;br /&gt;
Following best practices for attribution are important. If you cannot give all the following information then it&#039;s possible that the image shouldn&#039;t be used on the wiki:&lt;br /&gt;
* Title&lt;br /&gt;
* Author&lt;br /&gt;
* Source&lt;br /&gt;
* License&lt;br /&gt;
&lt;br /&gt;
====Known photographers====&lt;br /&gt;
&lt;br /&gt;
====Creative Commons====&lt;br /&gt;
&lt;br /&gt;
Images licensed under creative commons need to be [http://wiki.creativecommons.org/Marking/Users attributed in a particular way]. Here&#039;s an example:&lt;br /&gt;
{{CaptionedImage|file=2922935829 79a1e52fac z.jpg|title=Medieval Beekeeper|caption=A Medieval Beekeeper|centre|width=600}}&lt;br /&gt;
If you check the file page the following attribution is included:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;[https://www.flickr.com/photos/archeon/2922935829/in/photolist-5shNZk-75SYPY-fb4DT6-EDHab-4LkcDB-ewFAGj-tVQXC-6kwEoz-5yswsU-7VuHoM-6dCbgW-5spvNA-bBzKPJ-4XmgRj-6EJ5Xi-8ELZZg-gbXRR-7c5yBQ-Rr28y-4MdQkS-fpreTN-9hCqvc-7roNkF-e8CEiC-fL2D5Z-9xmQgw-abHh8M-5Rvpfj-bw9umB-3ssCj-8kGgbB-dgMMve-kqY4sC-4MVVUf-dZBPk-5nYUXr-4FGoSS-4XGveX-3iXBoa-5nPfh8-cBBecC-4S6S8S-fHDVLC-6f4wYM-Q7pSd-4v24sY-kAvqBV-a1m2Xv-eJTA4P-6THox Medieval Beekeeper]&amp;quot; by [https://www.flickr.com/photos/archeon/ Hans Splinter] is licensed under [https://creativecommons.org/licenses/by-nd/2.0/ CC BY-ND 2.0].&lt;br /&gt;
&lt;br /&gt;
Or in other words: &#039;&#039;&#039;&amp;quot;TITLE&amp;quot; by ARTIST is licensed under LICENSE.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Including these details allow the content creators to find where their work is being used on the internet, as well as to fulfil the terms of the license that we are using the images under.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Photography&amp;diff=702</id>
		<title>Photography</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Photography&amp;diff=702"/>
		<updated>2014-04-29T09:03:55Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Stub}}&lt;br /&gt;
&lt;br /&gt;
==Guidelines for non-photography crew==&lt;br /&gt;
&lt;br /&gt;
==Wiki Imagery==&lt;br /&gt;
&lt;br /&gt;
===Copyrighted Material===&lt;br /&gt;
&lt;br /&gt;
It should go without saying that we do not want imagery on the wiki that we do not have permission to use. The default assumption should be that you cannot use an image unless you explicitly have evidence to show that you can. Merely being available on the internet does not make an image &#039;fair game&#039; for use on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;There are several ways that you can ensure an image is ok for use on the wiki:&#039;&#039;&#039;&lt;br /&gt;
# Use an image from a crew photographer. Anyone who edits the wiki can email photography crew to get access to a library of images suitable for wiki use. This has the benefit of filling the wiki full of images from the game world.&lt;br /&gt;
# Obtain permission from the photographer and display their information within a special category page on the wiki. All images from that photographer should then have the standard accreditation template inserted.&lt;br /&gt;
# Use an image with the correct [http://creativecommons.org creative commons] license. Crucially we must use creative commons licenses that allow for commercial use. In addition all images with creative commons licenses must be attributed properly. Some websites have the ability to search images tagged with creative commons licenses - [https://www.flickr.com/search/advanced/ Flickr is particularly good for this]. Make sure you also tick the &#039;find content to use commercially&#039; box. However a little common sense is required here - not all images tagged with a creative commons license will have been done so legally. Just because you take a picture of something in a museum for example, does not mean that you can distribute it for commercial use (check the individual terms of the entrance ticket).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Images that are not ok to use on the wiki:&#039;&#039;&#039; &lt;br /&gt;
# Images where you have no idea of the author.&lt;br /&gt;
# Images taken as screenshots from film and TV.&lt;br /&gt;
# Creative Commons images that display the icon showing a dollar sign with a line through. These images are not ok for commercial use.&lt;br /&gt;
&lt;br /&gt;
===Attribution===&lt;br /&gt;
&lt;br /&gt;
Following best practices for attribution are important. If you cannot give all the following information then it&#039;s possible that the image shouldn&#039;t be used on the wiki:&lt;br /&gt;
* Title&lt;br /&gt;
* Author&lt;br /&gt;
* Source&lt;br /&gt;
* License&lt;br /&gt;
&lt;br /&gt;
====Known photographers====&lt;br /&gt;
&lt;br /&gt;
====Creative Commons====&lt;br /&gt;
&lt;br /&gt;
Images licensed under creative commons need to be [http://wiki.creativecommons.org/Marking/Users attributed in a particular way]. Here&#039;s an example:&lt;br /&gt;
{{CaptionedImage|file=2922935829 79a1e52fac z.jpg|title=Medieval Beekeeper|caption=A Medieval Beekeeper|centre|width=600}}&lt;br /&gt;
If you check the file page the following attribution is included:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;[https://www.flickr.com/photos/archeon/2922935829/in/photolist-5shNZk-75SYPY-fb4DT6-EDHab-4LkcDB-ewFAGj-tVQXC-6kwEoz-5yswsU-7VuHoM-6dCbgW-5spvNA-bBzKPJ-4XmgRj-6EJ5Xi-8ELZZg-gbXRR-7c5yBQ-Rr28y-4MdQkS-fpreTN-9hCqvc-7roNkF-e8CEiC-fL2D5Z-9xmQgw-abHh8M-5Rvpfj-bw9umB-3ssCj-8kGgbB-dgMMve-kqY4sC-4MVVUf-dZBPk-5nYUXr-4FGoSS-4XGveX-3iXBoa-5nPfh8-cBBecC-4S6S8S-fHDVLC-6f4wYM-Q7pSd-4v24sY-kAvqBV-a1m2Xv-eJTA4P-6THox Medieval Beekeeper]&amp;quot; by [https://www.flickr.com/photos/archeon/ Hans Splinter] is licensed under [https://creativecommons.org/licenses/by-nd/2.0/ CC BY-ND 2.0].&lt;br /&gt;
&lt;br /&gt;
Or in other words: &#039;&#039;&#039;&amp;quot;TITLE&amp;quot; by ARTIST is licensed under LICENSE.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Including these details allow the content creators to find where their work is being used on the internet, as well as to fulfil the terms of the license that we are using the images under.&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Template:Stub&amp;diff=701</id>
		<title>Template:Stub</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Template:Stub&amp;diff=701"/>
		<updated>2014-04-29T09:03:29Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: Created page with &amp;quot;&amp;lt;div class=&amp;quot;alert&amp;quot;&amp;gt;This is a placeholder page for content that PD are actively working on.&amp;lt;/div&amp;gt;&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div class=&amp;quot;alert&amp;quot;&amp;gt;This is a placeholder page for content that PD are actively working on.&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=694</id>
		<title>Civil servants</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=694"/>
		<updated>2014-04-28T15:38:59Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Institutional Civil Servants */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[Category:Civil Service]]&lt;br /&gt;
&lt;br /&gt;
==Institutional Civil Servants==&lt;br /&gt;
These civil servants are linked to specific Imperial Institutions to ensure their smooth operation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Civil Servant&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Institutions&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| [[Adeta]] || Brass Coast || Sam Sutton || Head of Civil Service&lt;br /&gt;
|-&lt;br /&gt;
| [[Abronsius|Chancellor Abronsius Eldenheart]] || Urizen || Tom Francis || Academy&lt;br /&gt;
|- &lt;br /&gt;
| [[Mila Baraslava]] || Varushka || Kate Forster || Synod / Senate / Hub Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[John of Meade]] || Marches || Harry Harrold || Senate &lt;br /&gt;
|-&lt;br /&gt;
| [[Angelo|Angelo i Cenezia i Riqueza]] || Brass Coast || Daniel Williams || Synod / Historical Research&lt;br /&gt;
|-&lt;br /&gt;
| [[Merlot]] || League || Paul Wilder || Elections Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[Khaytanus Everwatch]] || Urizen || James Littlewood || Conclave / Academy&lt;br /&gt;
|-&lt;br /&gt;
| [[Pavel|Pavel Gregorivitch Milyukov]] || Varushka || Liam Spinage || Military Council &lt;br /&gt;
|-&lt;br /&gt;
| [[Marta|Marta Vaskovich Kovar]] || Varushka || Elinor Kershaw || Bourse / Academy &lt;br /&gt;
|-&lt;br /&gt;
| [[Nileus|L. Nileus]] || Urizen || Aquarion || Senate&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Imperial Magistracy==&lt;br /&gt;
These civil servants co-ordinate the militia and are responsible for administering trials and Imperial justice. They are often found near the Hub.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
| &#039;&#039;&#039;Magistrate&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| [[Karkovitch|Stanislav Karkovich]] || Varushka || Jon Creek || Criminal / Constitutional / Religious law&lt;br /&gt;
|-&lt;br /&gt;
| [[Avedon|Avedon de Remourics]] || Dawn || Oliver Facey || Criminal / Religious Law&lt;br /&gt;
|-&lt;br /&gt;
| [[Marchello|Marchello Murchev]] || League || Mike Pye || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Grimmer|Grimmer Reinholz]] || Wintermark || Martin Verran || General &lt;br /&gt;
|-&lt;br /&gt;
| [[John Upwold]] || Marches || Richard Squires || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Gideon]] || HighGuard || Tom Butterworth || General&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Ancilliary Civil Servants==&lt;br /&gt;
These individual are not always present in the field at Anvil but may come to the field to deal with specific tasks:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Name&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| Moses || Highguard || Matt Pennington || Constitutional Court&lt;br /&gt;
|-&lt;br /&gt;
| The Auctioneer || Marches || Adam Buxton || Auctioneer / Bourse&lt;br /&gt;
|- &lt;br /&gt;
| Barak of Haros || Highguard || David Sheridan || Past Life Visions &lt;br /&gt;
|- &lt;br /&gt;
| Wylfa Bechod || Navarr || Dom Carroll || Past Life Visions&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:LeftBar&amp;diff=692</id>
		<title>Imperial:LeftBar</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:LeftBar&amp;diff=692"/>
		<updated>2014-04-25T08:56:01Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;nav-list&amp;gt;&lt;br /&gt;
  &amp;lt;nav-header&amp;gt;Wiki Editors&amp;lt;/nav-header&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:UserLogin|Login]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:RecentChanges|Recent Changes]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:ListFiles|List Files]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:Upload|Upload File]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;&amp;lt;historylink&amp;gt;Page History&amp;lt;/historylink&amp;gt;&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
&amp;lt;/nav-list&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:LeftBar&amp;diff=686</id>
		<title>Imperial:LeftBar</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Imperial:LeftBar&amp;diff=686"/>
		<updated>2014-04-24T14:03:46Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;nav-list&amp;gt;&lt;br /&gt;
  &amp;lt;nav-header&amp;gt;Wiki Editors&amp;lt;/nav-header&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:UserLogin|Login]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:RecentChanges|Recent Changes]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:ListFiles|List Files]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[[Special:Upload|Upload File]]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
  &amp;lt;nav-item&amp;gt;[{{fullurl:{{urlencode:{{FULLPAGENAME}}}}|offset={{CURRENTTIMESTAMP}}&amp;amp;action=history&amp;amp;limit=1}} Page History]&amp;lt;/nav-item&amp;gt;&lt;br /&gt;
&amp;lt;/nav-list&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=658</id>
		<title>Civil servants</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=658"/>
		<updated>2014-04-10T20:25:07Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Institutional Civil Servants */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[Category:Civil Service]]&lt;br /&gt;
&lt;br /&gt;
==Institutional Civil Servants==&lt;br /&gt;
These civil servants are linked to specific Imperial Institutions to ensure their smooth operation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Civil Servant&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Institutions&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| [[Adeta]] || Brass Coast || Sam Sutton || Head of Civil Service&lt;br /&gt;
|-&lt;br /&gt;
| [[Abronsius|Chancellor Abronsius Eldenheart]] || Urizen || Tom Francis || Academy&lt;br /&gt;
|- &lt;br /&gt;
| [[Mila Baraslava]] || Varushka || Kate Forster || Synod / Senate / Hub Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[John of Meade]] || Marches || Harry Harrold || Senate &lt;br /&gt;
|-&lt;br /&gt;
| [[Angelo|Angelo i Cenezia i Riqueza]] || Brass Coast || Daniel Williams || Synod / Historical Research&lt;br /&gt;
|-&lt;br /&gt;
| [[Merlot]] || League || Paul Wilder || Elections Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[Khaytanus Everwatch]] || Urizen || James Littlewood || Conclave / Academy&lt;br /&gt;
|-&lt;br /&gt;
| [[Pavel|Pavel Gregorivitch Milyukov]] || Varushka || Liam Spinage || Military Council &lt;br /&gt;
|-&lt;br /&gt;
| [[Marta|Marta Vaskovich Kovar]] || Varushka || Elinor Kershaw || Bourse / Academy &lt;br /&gt;
|-&lt;br /&gt;
| [[Elgar|Elgar Nithenhow]] || Urizen || Dave Jones || Bourse&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Imperial Magistracy==&lt;br /&gt;
These civil servants co-ordinate the militia and are responsible for administering trials and Imperial justice. They are often found near the Hub.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
| &#039;&#039;&#039;Magistrate&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| [[Karkovitch|Stanislav Karkovich]] || Varushka || Jon Creek || Criminal / Constitutional / Religious law&lt;br /&gt;
|-&lt;br /&gt;
| [[Avedon|Avedon de Remourics]] || Dawn || Oliver Facey || Criminal / Religious Law&lt;br /&gt;
|-&lt;br /&gt;
| [[Marchello|Marchello Murchev]] || League || Mike Pye || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Grimmer|Grimmer Reinholz]] || Wintermark || Martin Verran || General &lt;br /&gt;
|-&lt;br /&gt;
| [[John Upwold]] || Marches || Richard Squires || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Gideon]] || HighGuard || Tom Butterworth || General&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Ancilliary Civil Servants==&lt;br /&gt;
These individual are not always present in the field at Anvil but may come to the field to deal with specific tasks:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Name&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| Moses || Highguard || Matt Pennington || Constitutional Court&lt;br /&gt;
|-&lt;br /&gt;
| The Auctioneer || Marches || Adam Buxton || Auctioneer / Bourse&lt;br /&gt;
|- &lt;br /&gt;
| Barak of Haros || Highguard || David Sheridan || Past Life Visions &lt;br /&gt;
|- &lt;br /&gt;
| Wylfa Bechod || Navarr || Dom Carroll || Past Life Visions&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=657</id>
		<title>Civil servants</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=Civil_servants&amp;diff=657"/>
		<updated>2014-04-10T20:24:51Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: /* Institutional Civil Servants */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[Category:Civil Service]]&lt;br /&gt;
&lt;br /&gt;
==Institutional Civil Servants==&lt;br /&gt;
These civil servants are linked to specific Imperial Institutions to ensure their smooth operation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Civil Servant&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Institutions&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| [[Adeta]] || Brass Coast || Sam Sutton || Head of Civil Service&lt;br /&gt;
|-&lt;br /&gt;
| [[Abronsius|Chancellor Abronsius Eldenheart]] || Urizen || Tom Francis || Academy&lt;br /&gt;
|- &lt;br /&gt;
| Mila Baraslava || Varushka || Kate Forster || Synod / Senate / Hub Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[John of Meade]] || Marches || Harry Harrold || Senate &lt;br /&gt;
|-&lt;br /&gt;
| [[Angelo|Angelo i Cenezia i Riqueza]] || Brass Coast || Daniel Williams || Synod / Historical Research&lt;br /&gt;
|-&lt;br /&gt;
| [[Merlot]] || League || Paul Wilder || Elections Co-ordinator&lt;br /&gt;
|-&lt;br /&gt;
| [[Khaytanus Everwatch]] || Urizen || James Littlewood || Conclave / Academy&lt;br /&gt;
|-&lt;br /&gt;
| [[Pavel|Pavel Gregorivitch Milyukov]] || Varushka || Liam Spinage || Military Council &lt;br /&gt;
|-&lt;br /&gt;
| [[Marta|Marta Vaskovich Kovar]] || Varushka || Elinor Kershaw || Bourse / Academy &lt;br /&gt;
|-&lt;br /&gt;
| [[Elgar|Elgar Nithenhow]] || Urizen || Dave Jones || Bourse&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Imperial Magistracy==&lt;br /&gt;
These civil servants co-ordinate the militia and are responsible for administering trials and Imperial justice. They are often found near the Hub.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
| &#039;&#039;&#039;Magistrate&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| [[Karkovitch|Stanislav Karkovich]] || Varushka || Jon Creek || Criminal / Constitutional / Religious law&lt;br /&gt;
|-&lt;br /&gt;
| [[Avedon|Avedon de Remourics]] || Dawn || Oliver Facey || Criminal / Religious Law&lt;br /&gt;
|-&lt;br /&gt;
| [[Marchello|Marchello Murchev]] || League || Mike Pye || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Grimmer|Grimmer Reinholz]] || Wintermark || Martin Verran || General &lt;br /&gt;
|-&lt;br /&gt;
| [[John Upwold]] || Marches || Richard Squires || General&lt;br /&gt;
|-&lt;br /&gt;
| [[Gideon]] || HighGuard || Tom Butterworth || General&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Ancilliary Civil Servants==&lt;br /&gt;
These individual are not always present in the field at Anvil but may come to the field to deal with specific tasks:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| &#039;&#039;&#039;Name&#039;&#039;&#039; || &#039;&#039;&#039;Nation&#039;&#039;&#039; || &#039;&#039;&#039;Crew Name&#039;&#039;&#039; || &#039;&#039;&#039;Specialism&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| Moses || Highguard || Matt Pennington || Constitutional Court&lt;br /&gt;
|-&lt;br /&gt;
| The Auctioneer || Marches || Adam Buxton || Auctioneer / Bourse&lt;br /&gt;
|- &lt;br /&gt;
| Barak of Haros || Highguard || David Sheridan || Past Life Visions &lt;br /&gt;
|- &lt;br /&gt;
| Wylfa Bechod || Navarr || Dom Carroll || Past Life Visions&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
	<entry>
		<id>https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:WW_VDAendpages.pdf&amp;diff=199</id>
		<title>File:WW VDAendpages.pdf</title>
		<link rel="alternate" type="text/html" href="https://www.profounddecisions.co.uk/mediawiki-crew-pd/index.php?title=File:WW_VDAendpages.pdf&amp;diff=199"/>
		<updated>2014-02-14T15:44:22Z</updated>

		<summary type="html">&lt;p&gt;Aquarion: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Aquarion</name></author>
	</entry>
</feed>