Equipment/Boole: Difference between revisions

From London Hackspace Wiki
mNo edit summary
No edit summary
 
(24 intermediate revisions by 5 users not shown)
Line 4: Line 4:
|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 -->
|subcat=Systems <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one -->
|subcat=Defunct <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one -->
|status=Good working order <!-- Set to one of; Good working order, Faulty, Out of order, Under construction, Out of consumables, Scrapped, or Unknown -->
|status=Faulty <!-- Set to one of; Good working order, Faulty, Out of order, Under construction, Out of consumables, Scrapped, or Unknown -->
|consumables=<!-- Any items used up in normal operation, such as; ink, paper, saw-blades, cutting disks, oil, etc.. -->
|consumables=<!-- Any items used up in normal operation, such as; ink, paper, saw-blades, cutting disks, oil, etc.. -->
|accessories=<!-- Any items associated with the equipment but not consumable, such as; drill bits, safety gloves, goggles, etc.. -->
|accessories=<!-- Any items associated with the equipment but not consumable, such as; drill bits, safety gloves, goggles, etc.. -->
Line 13: Line 13:
|owner=LHS <!-- Provide a link to owners members page if other than LHS -->
|owner=LHS <!-- Provide a link to owners members page if other than LHS -->
|origin=donation from Tgreer <!-- If via pledge, please link to the completed pledge page on the wiki -->
|origin=donation from Tgreer <!-- If via pledge, please link to the completed pledge page on the wiki -->
|location=Basement rack. <!-- Floor, room/zone and location within that area -->
|location=first floor comms room<!-- Floor, room/zone and location within that area -->
|maintainers=Sysadmin team <!-- If someone is nominated as managing the upkeep of this item, please list them here. No links please; it currently breaks the template. -->
|maintainers=Sysadmin team <!-- If someone is nominated as managing the upkeep of this item, please list them here. No links please; it currently breaks the template. -->
|template_ver=1.1 <!-- Please do not change. Used for tracking out-of-date templates -->
|template_ver=1.1 <!-- Please do not change. Used for tracking out-of-date templates -->
}}
}}
A 1U Intel Atom machine in the rack in the basement, specs etc [http://www.nexcom.com/Products/network-and-communication-solutions/desktop-appliance/desktop-appliance/communication-gateway-dna-1110# here]


Is our core router, has both FTTC lines connected to it. DHCP and DNS server. Runs the spacefed node for the space and is an ldap server.


Also a netboot server, provides:
== NOTE: Boole is not currently in use ==
It started rebooting itself so routing was moved to [[Equipment/Norton]] to keep things running


* Diskless i386 and amd64 debian wheezy
== Previous Contents ==
* Rescue and Install for debian wheezy.
* partition magic
* memtest
* dban
* Voyage (a minimised debian disto that can run from readonly media) '''Warning''' : the Voyage auto install kernsl will '''reformat''' things they are booted on ''without prompting''.


Also runs ansible for setting up machines in the space.
Boole is named after [https://en.wikipedia.org/wiki/George_Boole George Boole] who was instrumental in differential equations and algebraic logic and ultimately leading to Boolean Algebra.  


=== Issues ===
Boole is a 1U Intel Atom machine ([http://www.nexcom.com/fildata/getpdf/15428b52-cba2-45f5-bccd-65a9239dd078 Nexcom DNA1110]) running [http://www.pfsense.org/ pfSense 2.4.]  The original hard drive used during 447 Hackney Road was replaced with an SSD as it was dead and we also wanted a router with as few moving parts as possible.


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 unboudn init scripts.
Boole's purpose is providing routing and network uplink services via its four gigabit ethernet ports.  It provides DNS, DHCP, and firewall services to the network.  


We have have installed the latest versio of the rp-pppoe ppp plugin so we can use a 1508 byte mtu to avoid having to do mss clamping.
= Info =
* IP: 10.0.20.1
* DNS: boole.london.hackspace.org.uk
* Operating System:  [https://www.pfsense.org/download/ pfSense 2.4 (Latest)]
* Access: Internal HTTPS & SSH (Infrastructure Team & Trustees) and externally via non-standard ssh port.


=== using Ansible with a Rasbperry Pi ===
= Stats =
Boole is a Nexcom DNA1110 system with the following:


<nowiki>
* [https://ark.intel.com/products/43517/Intel-Atom-Processor-D410-512K-Cache-1_66-GHz Intel Atom D410 single core dual thread 1.66ghz processor]
dd raspbian image (use the 02-09 one to avoid usb issues)
* 4 x 1Gigabit Intel 82853V Ethernet ports - One port for building-provided Internet, three ports for internal networking.
boot pi
* 2GB of DDR2 667/800 Memory
watch dhcp logs on boole
* 120GB Western Digital Green SATA SSD
ssh pi@ip
* Unused PCI Expansion Port
passwd: raspberry


sudo raspi-config
= Network =
update it
More information is kept in the [[Network]] section of this wiki.
expand filesystem
change password
boot to console
advanced options -> hostname


cd /etc/network
= Login =
edit interfaces to get a static ip
Members of the Admins [[LDAP]] group should be able to log into the web interface. This is achieved by allowing [[LDAP]] as a login source, and creating a group on PFSense names 'Admins' (matches the [[LDAP]] group name exactlywith admin privileges.
reboot
 
log into boole with ssh keys forwarded
 
add hostname to dns
add hostname to /etc/ansible/hosts in both the [lhshosts] and [rpis]
sections, and [doorbot] if it's a doorbot, make the syslocation="something sensible"
 
then:
 
if it's a replacement for an old machine then
ssh-keygen -R hostname
ssh-keygen -R hostname.lan.london.hackspace.org.uk
ssh-keygen -R ipv4 address (?)
ssh-keygen -R ipv6 address (?)
 
then:
 
cd /etc/ansible
ansible -v -s -u pi -k -m command -a "apt-get -y install python-apt" "hostname*"
ansible-playbook -u pi -s -k -l "perlman*" lhs/site.yml
 
The 2nd one will add our users, ssh keys, packages, etc etc.
 
notes:
 
not sure how resolv.conf gets setup, I thought having:
 
iface eth0 inet static
        [...]
        dns-nameservers 172.31.24.2
        dns-search lan.london.hackspace.org.uk
 
would sort it, but maybe that dosn't and we got lucky from dhcp?
 
the dns stuff in /etc/network/interfaces appears to be bogus and resolv.conf needs to be
done manually, add to ansible.
 
</nowiki>

Latest revision as of 22:02, 24 May 2021

Boole
Hackspace Unknown.png
Model Nexcom DNA1110
Sub-category Defunct
Status Faulty
Training requirement yes
Training link Unknown
ACnode no
Owner LHS
Origin donation from Tgreer
Location first floor comms room
Maintainers Sysadmin team


NOTE: Boole is not currently in use

It started rebooting itself so routing was moved to Equipment/Norton to keep things running

Previous Contents

Boole is named after George Boole who was instrumental in differential equations and algebraic logic and ultimately leading to Boolean Algebra.

Boole is a 1U Intel Atom machine (Nexcom DNA1110) running pfSense 2.4. The original hard drive used during 447 Hackney Road was replaced with an SSD as it was dead and we also wanted a router with as few moving parts as possible.

Boole's purpose is providing routing and network uplink services via its four gigabit ethernet ports. It provides DNS, DHCP, and firewall services to the network.

Info

  • IP: 10.0.20.1
  • DNS: boole.london.hackspace.org.uk
  • Operating System: pfSense 2.4 (Latest)
  • Access: Internal HTTPS & SSH (Infrastructure Team & Trustees) and externally via non-standard ssh port.

Stats

Boole is a Nexcom DNA1110 system with the following:

Network

More information is kept in the Network section of this wiki.

Login

Members of the Admins LDAP group should be able to log into the web interface. This is achieved by allowing LDAP as a login source, and creating a group on PFSense names 'Admins' (matches the LDAP group name exactly) with admin privileges.