User Tools

Site Tools


serverhosting

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
serverhosting [2018-10-31 19:20] – [Acceptable Use Policy] timserverhosting [2023-01-19 18:31] (current) – [Setup] simon
Line 9: Line 9:
 ===== Network ===== ===== 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)   * 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 ===== ===== Power =====
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. 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. Hacklab may retain netflows (network traffic metadata) for up to 30 days, for the purpose of investigating network abuse reports.
- 
- 
 ===== Setup ===== ===== Setup =====
  
Line 49: Line 47:
     * 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.     * 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 public IPs from the Server LAN (one IPv4 per member, but as many IPv6 as needed) and link them to the device.
 +    * If you're using incoming/outgoing SMTP then refer to [[sysadmin:smtp]] to allow this traffic (which is blocked by default).
   * DNS:   * DNS:
     * Local DNS: is driven from NetBox data.     * 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:   * 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.     * 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.
serverhosting.1541013631.txt.gz · Last modified: 2018-10-31 19:20 by tim

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki