Difference between revisions of "Equipment/Boole"
Jump to navigation
Jump to search
m |
|||
| Line 19: | Line 19: | ||
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] | 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] | ||
| − | Boole is our core router, has both FTTC lines connected to it. DHCP and DNS | + | Boole is our core router, has both FTTC lines connected to it. DHCP and DNS server. |
=== Issues === | === Issues === | ||
Revision as of 23:04, 11 September 2014
| Boole | |
|---|---|
 | |
| 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.