Differences

This shows you the differences between two versions of the page.

--- serverhosting [2017-06-22 13:27] – tim
+++ serverhosting [2024-10-03 18:50] (current) – simon
@@ Line 9: / Line 9: @@
 ===== Network =====
-Hacklab's internet is provided by [[https://hubs.net.uk/|HUBS]]. Each member may use:
+Hacklab's internet is provided by [[https://www.commsworld.com/our-network|Fluency]]. Each member may use:
-  * one public IPv4 address (from 185.34.62.0/27)
+  * at least one public IPv4 address (from 209.16.157.0/24)
   * many private IPv4 addresses (from 10.38.41.0/24)
-  * lots of public IPv6 addresses (from 2a04:5d00:70:1::/64)
+  * lots of public IPv6 addresses (from 2a04:5d00:70:1::/64 or 2a00:a600:6:1::/64)
 ===== Power =====
@@ Line 29: / Line 29: @@
 ===== Alternatives =====
-Virtual machines are available on //lithium//. Please ask Tim if you would like one.
+Virtual machines are available on //titanium//. See [[private:virtual_machines]] for details.
 ===== Acceptable Use Policy =====
@@ Line 37: / Line 37: @@
 As a guide, anything that a normal hosting provider would allow should be okay. If your application or content would cause problems at another provider then you should discuss this with directors or the membership first.
-Tor has been discussed previously and there were a number of objections on ethical and reputational grounds. Tor nodes are unlikely to be approved and should not be operated on our network.
+Tor has been discussed previously and there were a number of arguments on ethical and reputational grounds, both for and against running nodes. A consensus has not been reached on the matter. Further discussion would be required before running a node.
+Hacklab may retain netflows (network traffic metadata) for up to 30 days, for the purpose of investigating network abuse reports.
 ===== Setup =====
@@ Line 46: / Line 48: @@
     * Create a device entry for your server and record the location where it will be installed. For non-rack devices, the server will usually go on the shelving.
     * Allocate public IPs from the Server LAN (one IPv4 per member, but as many IPv6 as needed) and link them to the device.
+    * Allocate a switch port in [[ehana]] and ask a sysadmin to connect the interface on your server to the port on the switch in NetBox.
+    * If you're using incoming/outgoing SMTP then refer to [[sysadmin:smtp]] to allow this traffic (which is blocked by default).
   * DNS:
     * Local DNS: is driven from NetBox data.
-    * Internet DNS: forward entries are up to you, reverse entries should be requested from Tim.
+    * Internet DNS: forward entries are up to you, reverse entries are managed by NetBox. (Fluency IPv6 reverse DNS has to be requested manually via Texaport.)
   * Install:
     * Rack devices should be installed securely. If you don't have rails, get permission to stack on another person's server and don't stack multiple unsecured servers.
     * Route power cables at the right-side of the rack (view from the rear) and use cable ties to keep them neat and tidy. If you have dual PSUs, only connect one of them (dual PSUs will use more power, and there is limited benefit as we don't have independent power sources).
-    * Route network cables to the left-side of the rack and connect to a Server LAN port. Record the port used in NetBox or [[https://wiki.edinburghhacklab.com/ehana|EHANA]] (depending on the switch).
+    * Route network cables to the left-side of the rack and connect to a Server LAN port. Record the port used in NetBox or [[https://wiki.edinburghhacklab.com/ehana|EHANA]] (depending on the switch). If a new port needs to be configured, ask someone who is familiar with the switch to help.
+    * If the shelving is used, then use the switch and power strips on the shelf. Tie your cables neatly.
     * Label your server with your name, and the server name (matching the one in NetBox).