expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-24 16:21:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update IP addresses to reflect fact that tattyhut network is 192.168.200.x - online edit of handbook/computing/netconfig.html

Browse Source
This commit is contained in:
Expo on server 2023-07-03 03:14:31 +01:00
parent 2db3a48032
commit df1acfc8b8
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
handbook/computing/netconfig.html
View File

@ -38,7 +38,7 @@ still upright and have not been knocked sideways.
<h3>The potato hut wifi</h3> <h3>The potato hut wifi</h3>
<p>The potato hut wiFi has <a href="https://www.howtogeek.com/334935/what-is-an-ssid-or-service-set-identifier/">SSID</a> "tattyhut" with our usual cavey:beery password. Like almost every other wifi anywhere it is running DHCP and allocating IP addresses to your device. <p>The potato hut wiFi has <a href="https://www.howtogeek.com/334935/what-is-an-ssid-or-service-set-identifier/">SSID</a> "tattyhut" with our usual cavey:beery password. Like almost every other wifi anywhere it is running DHCP and allocating IP addresses to your device.
<p>The DHCP system is issuing IP4 addresses of the form <samp>192.168.1.x</samp> where x is a number between 11 and 199 with a lifetime of 48 hours. <p>The DHCP system is issuing IP4 addresses of the form <samp>192.168.200.x</samp> where x is a number between 11 and 199 with a lifetime of 48 hours.
<p>The <em>Expo laptops</em> acquire a dynamic local address of this form, as does any other laptop or phone connecting to this wifi. <p>The <em>Expo laptops</em> acquire a dynamic local address of this form, as does any other laptop or phone connecting to this wifi.
<h3>How it works - in words</h3> <h3>How it works - in words</h3>
@ -51,7 +51,7 @@ Ignore the backup copy in /home/expo/fakenet.
<h4>Wifi/router Netgear WNDR4000</h4> <h4>Wifi/router Netgear WNDR4000</h4>
<p>The Netgear ethernet/wifi hub holds the radio transceiver that provides the wifi coverage inside the potato hut. <p>The Netgear ethernet/wifi hub holds the radio transceiver that provides the wifi coverage inside the potato hut.
It has an <a href="https://manualmachine.com/netgear/wndr4000/816208-user-manual/">online manual</a> but it needs no configuration at all during expo. Just turn it on at the beginning of expo and off again at the end. It has an <a href="https://manualmachine.com/netgear/wndr4000/816208-user-manual/">online manual</a> but it needs no configuration at all during expo. Just turn it on at the beginning of expo and off again at the end.
<p>The webpage control panel (which you should never need or touch) is accessed by connecting a laptop to the wifi or using the <var>expo laptop</var> on the ethernet and bringing up a web browser to <a href="http://192.168.1.1">http://192.168.1.1</a> with username 'admin' and the usual expo cavey:beery password. The password is also written on the underneath of the box. <p>The webpage control panel (which you should never need or touch) is accessed by connecting a laptop to the wifi or using the <var>expo laptop</var> on the ethernet and bringing up a web browser to <a href="http://192.168.200.1">http://192.168.200.1</a> with username 'admin' and the usual expo cavey:beery password. The password is also written on the underneath of the box.
<h5>TL-WR841N</h5> <h5>TL-WR841N</h5>
<figure class="onright" > <figure class="onright" >
@ -59,7 +59,7 @@ Ignore the backup copy in /home/expo/fakenet.
<br><figcaption>TL-WR841N sockets and switches</figcaption> <br><figcaption>TL-WR841N sockets and switches</figcaption>
</figure> </figure>
<p>In 2023 we will also have a backup wifi/router in Austria, a £20 <a href="https://www.expertreviews.co.uk/tp-link/1401766/tp-link-tl-wr841n-review">TL-WR841N</a> belonging to Wookey which is configured identically to the Netgear device except that the username is 'root' not 'admin'. It would be good to test this so we could give ARM their WNDR4000 back, and the TP-link router can become expo's. <p>In 2023 we will also have a backup wifi/router in Austria, a <a href="https://www.expertreviews.co.uk/tp-link/1401766/tp-link-tl-wr841n-review">TL-WR841N</a> belonging to Wookey which is configured identically to the Netgear device except that the username is 'root' not 'admin'. It would be good to test this so we could give ARM their WNDR4000 back, and the TP-link router can become expo's.
<p>One important difference is that the ethernet cable from the netbook is plugged into the blue socket on the WR841N (it is yellow on the Netgear), and the 4 white sockets on the Netgear are 4 yellow sockets on the WR841N. A word of warning: the WR841N has been flashed with new firmware (openWRT) and so any documentation you may read in online manuals for it will be wrong: notably the reset and wifi on/off buttons don't have any effect, and the lights don't flash in the way the manuals say they do. There is also no USB socket, no 5Ghz, slower ethernet (100Mbps not 1Gbps) and the wifi range out to the tents is probably worse than the Netgear wifi. <p>One important difference is that the ethernet cable from the netbook is plugged into the blue socket on the WR841N (it is yellow on the Netgear), and the 4 white sockets on the Netgear are 4 yellow sockets on the WR841N. A word of warning: the WR841N has been flashed with new firmware (openWRT) and so any documentation you may read in online manuals for it will be wrong: notably the reset and wifi on/off buttons don't have any effect, and the lights don't flash in the way the manuals say they do. There is also no USB socket, no 5Ghz, slower ethernet (100Mbps not 1Gbps) and the wifi range out to the tents is probably worse than the Netgear wifi.
<h4>Alfa wifi device</h4> <h4>Alfa wifi device</h4>
@ -73,18 +73,18 @@ Ignore the backup copy in /home/expo/fakenet.
<p>To understand how the network is configured, you need to realise that we have to manage these different 'networks': <p>To understand how the network is configured, you need to realise that we have to manage these different 'networks':
<ul> <ul>
<li><samp>192.168.2.x</samp> The Gasthof wifi network <li><samp>192.168.2.x</samp> The Gasthof wifi network
<li><samp>192.168.1.x</samp> The potato hut wifi network <li><samp>192.168.200.x</samp> The potato hut wifi network
<li><samp>10.0.x.y</samp> The network on the short bit of cable connecting the netbook with the Netgear box. <li><samp>10.0.1.x</samp> The network on the short bit of cable connecting the netbook with the Netgear box.
<li>The network on the longer length of cable connecting the Netgear box with the <var>expo laptop</var> (and sometimes the printer). <li>The network on the longer length of cable connecting the Netgear box with the <var>expo laptop</var> (and sometimes the printer).
</ul> </ul>
We bridge the hut wifi with the hut ethernet cable to the <var>expo laptop</var> so they are both <samp>192.168.1.x</samp>, but this is a matter of choice. This is configured inside the wifi/router using the webpage control panel. We bridge the hut wifi with the hut ethernet cable to the <var>expo laptop</var> so they are both <samp>192.168.200.x</samp>, but this is a matter of choice. This is configured inside the wifi/router using the webpage control panel.
<h4>Where the DNS happens</h4> <h4>Where the DNS happens</h4>
<p> DNS is what connects a computer name (such as <var>expo.survex.com</var>) with an internet address (such as <samp>78.129.164.125</samp>). To make the internet work, we need to tell every laptop and phone where to find a DNS nameserver, or what machine to ask in order to get DNS queries forwarded to a DNS nameserver. <p> DNS is what connects a computer name (such as <var>expo.survex.com</var>) with an internet address (such as <samp>78.129.164.125</samp>). To make the internet work, we need to tell every laptop and phone where to find a DNS nameserver, or what machine to ask in order to get DNS queries forwarded to a DNS nameserver.
<p>The DNS configuration happens in the netbook, using dnsmasq. The Netgear box just forwards DNS queries to the netbook, and tells laptops connected to the hut wifi to use that too. <p>The DNS configuration happens in the netbook, using dnsmasq. The Netgear box just forwards DNS queries to the netbook, and tells laptops connected to the hut wifi to use that too.
<h4>Where the DHCP happens</h4> <h4>Where the DHCP happens</h4>
<p>DHCP is what decides what the <samp>x</samp> is when the wifi issues an address that a laptop must use when it connects to the wifi as <samp>192.168.1.x</samp>. <p>DHCP is what decides what the <samp>x</samp> is when the wifi issues an address that a laptop must use when it connects to the wifi as <samp>192.168.200.x</samp>.
<p>We have done this in two different ways: <p>We have done this in two different ways:
<ol> <ol>
<li>2017-2019 : in the netbook. <li>2017-2019 : in the netbook.
@ -92,7 +92,8 @@ We bridge the hut wifi with the hut ethernet cable to the <var>expo laptop</var>
</ol> </ol>
<p>1. The benefit of doing it in the Netgear box is that you get to play with a graphical web interface not text files. But also you can test that the Netgear box is working separately from everything else. <p>1. The benefit of doing it in the Netgear box is that you get to play with a graphical web interface not text files. But also you can test that the Netgear box is working separately from everything else.
<p>2. The benefit of doing it in the netbook is that all the configuration is in the same place, and you only have to learn one way of doing things instead of having to use text files <em>and</em> a web interface. Also, by making the Netgear box completely dumb, it is swap-replaceable if it dies with no reconfiguration required. <p>2. The benefit of doing it in the netbook is that all the configuration is in the same place, and you only have to learn one way of doing things instead of having to use text files <em>and</em> a web interface. Also, by making the Netgear box completely dumb, it is swap-replaceable if it dies with no reconfiguration required.
<p>The DHCP is configured to issue IP addresses with <samp>x</samp> between 10 and 199, i.e. laptops and phones will get IP addresses between <samp>192.168.1.10</samp> and <samp>192.168.1.199</samp>. These may change after 12 hours. <p>The DHCP is configured to issue IP addresses with <samp>x</samp> between 10 and 199, i.e. laptops and phones will get IP addresses between <samp>192.168.200.10</samp> and <samp>192.168.200.199</samp>. These may change after 12 hours.
<p>The router itself is <samp>192.168.200.1</samp>
<h4>Interfaces</h4> <h4>Interfaces</h4>
@ -100,9 +101,9 @@ We bridge the hut wifi with the hut ethernet cable to the <var>expo laptop</var>
<p>The netbook has two network interfaces: the Alfa wifi antenna (which is 'wlan1' and has an address issued by the Gasthof wifi system using DHCP) plugged into a USB socket, and the netbook's ethernet cable socket (eth0) which is configured to have the address <samp>10.0.1.2</samp>. <p>The netbook has two network interfaces: the Alfa wifi antenna (which is 'wlan1' and has an address issued by the Gasthof wifi system using DHCP) plugged into a USB socket, and the netbook's ethernet cable socket (eth0) which is configured to have the address <samp>10.0.1.2</samp>.
wlan0 on the netbook is the internal wifi. wlan0 on the netbook is the internal wifi.
<p>The Netgear box has its yellow ethernet cable socket set to the address <samp>10.0.1.1</samp>. The four other ethernet sockets are all on the address range <samp>192.168.1.x</samp> and the wifi network interface is set to <samp>192.168.1.1</samp> also in the network <samp>192.168.1.x</samp>. <p>The Netgear box has its yellow ethernet cable socket set to the address <samp>10.0.1.1</samp>. The four other ethernet sockets are all on the address range <samp>192.168.200.x</samp> and the wifi network interface is set to <samp>192.168.200.1</samp> also in the network <samp>192.168.200.x</samp>.
<p>So the ethernet cable between the Netgear box and the netbook is <samp>10.0.1.1</samp> at the Netgear end and <samp>10.0.1.2</samp> at the netbook end. Nothing else uses any number like <samp>10.0.x.y</samp>. <p>So the ethernet cable between the Netgear box and the netbook is <samp>10.0.1.1</samp> at the Netgear end and <samp>10.0.1.2</samp> at the netbook end. Nothing else uses any number like <samp>10.0.1.x</samp>.
<h4 style="color: red">When it all goes wrong</h4> <h4 style="color: red">When it all goes wrong</h4>
@ -387,7 +388,7 @@ the Gasthof. We continued with the wifi service in the hut but now it also conne
<p>Also during winter 2023/23 Wookey upgraded the operating system on the Acer Aspire One netbook from the ancient Debian Wheezy it had been running to a decently almost-modern Debian distribution. This required much coaxing. <p>Also during winter 2023/23 Wookey upgraded the operating system on the Acer Aspire One netbook from the ancient Debian Wheezy it had been running to a decently almost-modern Debian distribution. This required much coaxing.
<h4>History of the scripts</h4> <h4>History of the scripts</h4>
<p>The structure of the system was created by Wookey in 2013 who used the fakenet principle and the netbook to run training sessions for the Cave Survey Group in the UK. [This is why the script has an extra level of parameter setting that might seem necessary: it has 'csg' and 'expo' options, but the two configurations have diverged so much over the years that this is merely a fossil.] <p>The structure of the system was created by Wookey in 2013 who used the fakenet principle and the netbook to run training sessions in caving huts with no internet connection for the Cave Survey Group in the UK. [This is why the script has an extra level of parameter setting that might seem unnecessary: it has 'csg' and 'expo' options, but the two configurations have diverged so much over the years that this is merely a fossil.]
<p>The part of the script that logs into the Gasthof wifi was written by Mark Shinwell in 2017 and re-edited by Sam Wenham in 2019. Wookey made it more robust on expo in 2022. <p>The part of the script that logs into the Gasthof wifi was written by Mark Shinwell in 2017 and re-edited by Sam Wenham in 2019. Wookey made it more robust on expo in 2022.
<hr /> <hr />