expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 00:42:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

ip address updates

Browse Source
This commit is contained in:
Philip Sargent 2023-07-03 21:09:20 +01:00
parent e5f0eb9d4a
commit cedfdc2fd0
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
handbook/computing/netconfig.html
View File

@ -38,7 +38,8 @@ still upright and have not been knocked sideways.
<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 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 DHCP system is issuing IP4 addresses of the form <samp>192.168.200.x</samp> where x is a number between 50 and 199
with a lifetime of 12 hours (the backup router, the tp-link WRT41N, issues addresses of the form <samp>192.168.250.x</samp> instead).
<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>
@ -59,12 +60,12 @@ Ignore the backup copy in /home/expo/fakenet.
<br><figcaption>TL-WR841N sockets and switches</figcaption>
</figure>
<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>In 2023 we 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.
<h4>Alfa wifi device</h4>
<p>The Alfa AWUS036ACH is a high-power external wifi aerial to connect across the campsite to the gasthof. It uses the Realtek RTL8812AU chipset. Annoyingly this does not have a mainline kernel driver so we have to use a dkms driver '8812au'. This is not properly debianized so if you upgrade the kernel on the aspire it has to be rebuilt. The source and the rebuild scripts are in /home/expo/alfa-driver/morrownr. installing the kernel headers for the runing kernel, then running <tt>/home/expo/alfa-driver/morrownr/install-driver.sh NoPrompt</tt> will update it.
<p>I recommend not updating the kernel for the duration of expo.
<p>I recommend not updating the kernel for the duration of expo. We are getting 25-30 Mbit/s download speed with this device at the Acer Aspire netbook (3 July 2023).
<h4>IP6</h4>
<p>While you can use 5Ghz wifi and IP6 to connect within the hut, there is no IP6 connectivity to the external internet. Sorry. We are dependent on the Gasthof system for this. Use a phone and data roaming if you want it.
@ -88,17 +89,20 @@ We bridge the hut wifi with the hut ethernet cable to the <var>expo laptop</var>
<p>We have done this in two different ways:
<ol>
<li>2017-2019 : in the netbook.
<li>2022 : in the Netgear box.
<li>2022 : in the router (Netgear or tp-link) box.
</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 router 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>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 DHCP is configured to issue IP addresses with <samp>x</samp> between 50 and 199, i.e. laptops and phones will get IP addresses between <samp>192.168.200.50</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>
<p>We also have the address <samp>192.168.200.100</samp> reserved for the expo laptop <em>crowley</em> in both routers.
<h4>Interfaces</h4>
<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 192.168.2.x 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.
<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>.
@ -118,9 +122,7 @@ the black WiFi antennae on the small black Alfa box are still upright and have n
<p>The netbook attempts a reconnection every 60 seconds, so wait at least 2 minutes before doing anything. That is because when the netbook attempts a full reconnection it can take nearly a minute to rebuild everything.
<p>Test whether the netbook is actually running and responding by sitting at the <var>expo laptop</var> and logging into the netbook remotely. Do this in a terminal window:
<pre><code>ssh expo@tclaspire3.potato.hut</code></pre>
or
<pre><code>ssh expo@tclaspire3.hut</code></pre>
<pre><code>ssh expo@tclaspire3.potatohut</code></pre>
or
<pre><code>ssh expo@10.0.1.2</code></pre>
(The last of these may not actually work: this is a non-routable IP address.)