Equipment/Boole: Difference between revisions
From London Hackspace Wiki
PeterMeadows (talk | contribs) No edit summary |
PeterMeadows (talk | contribs) No edit summary |
||
Line 17: | Line 17: | ||
|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. | A 1U Intel Atom machine in the rack in the basement, specs etc [http://www.nexcom.eu/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 server. | Boole is our core router, has both FTTC lines connected to it. DHCP and DNS server. |
Revision as of 18:05, 21 January 2015
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.