Difference between revisions of "Equipment/Boole"

From London Hackspace Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
{{EquipmentInfobox
 
{{EquipmentInfobox
 
|name=Boole <!-- Name of the item. -->
 
|name=Boole <!-- Name of the item. -->
|image=Hackspace_Unknown.png <!-- Image of the item. Leave with placeholder image if none exists. -->
+
|image=BorgLHS.jpg <!-- Image of the item. Leave with placeholder image if none exists. -->
 
|model=Nexcom DNA1110 <!-- Model -->
 
|model=Nexcom DNA1110 <!-- Model -->
 
|category=Equipment <!-- Main category. Please leave alone to keep item in this category -->
 
|category=Equipment <!-- Main category. Please leave alone to keep item in this category -->

Revision as of 11:39, 20 December 2014

Boole
BorgLHS.jpg
Model Nexcom DNA1110
Sub-category Systems
Status Good working order
Training requirement yes
Training link Unknown
ACnode no
Owner LHS
Origin donation from Tgreer
Location Basement rack
Maintainers Sysadmin team

A 1U Intel Atom machine in the rack in the basement, specs etc here

Boole is our core router, has both FTTC lines connected to it. DHCP and DNS server.

Issues

On boot unbound can fail to start due to ipv6 dad not finishing in time for it to bind to it's ipv6 address, see this:

http://lists.debian.org/debian-devel/2012/11/msg00038.html I added sleep 10 to the unbound init scripts.


We have have installed the latest version of the rp-pppoe ppp plugin so we can use a 1508 byte mtu to avoid having to do mss clamping.


Sometimes we lose the ipv6 default route, doing poff a-and-a ; pon a-and-a makes it work again, but we don't know the underlying cause.