Deer Park in Stillorgan Co. Dublin. Taken on my Samsung Galaxy Note II, lunchtime, Monday November 18th 2013.
Thoughts, ramblings and rants…
Some very useful RIPE database links that I was recently shown include:
Connecting to a Soekris box from your computer via a console cable is a DTE to DTE connection and so you need to purchase or make up a null modem cable. This page on RS232 serial null modem cable wiring proved invaluable.
With the documentation above, I created a null modem with loop back handshaking cable using two wire-able female DB9-to-RJ45 converters and a standard straight-through network cable following the pin positions in the above link.
To locally connect and loop back  pins  1+4+6 and 7+8, I snipped those wires, striped the ends and just twisted together and covered with electrical tape. Pin 5 is connected to its opposite number and you only then need to ensure that pins 2 and 3 are crossed over.
This worked a charm with my USB serial port. After I tried about a dozen various unlabeled console cables I have lying around that is…
I’m surprised. Pleasantly so; actually, exuberantly so. I thought the battle was lost and that democracy here in Ireland would have taken a hit today. But, in the words of a friend, every time I lose faith in the Irish electorate, they suck me back in.
In a – if you were to look at recent opinion polls – shock result, the Irish electorate voted by 51.7% to retain our second house, Seanad Éireann.
I have some reflections on this:
Anyway, it’s a great result and the right result. I look forward to reform.
Update 2019: we now use PrivateBin a lot. It is a self-hosted, minimalist, open source online pastebin where the server has zero knowledge of pasted data.
Pastebin has been a valuable tool for years – to the extent that pastebin it has entered the common lexicon of sysadmins, network engineers and developers.
There are, however, a few notable alternatives:
$ traceroute -m 60 216.81.59.173 | curl -F 'sprunge=<-' http://sprunge.us http://sprunge.us/THie
Check out the result at http://sprunge.us/THie.
And she does it more eloquently than I did:
http://www.youtube.com/watch?v=zZUo_BodGgc
Because I was asked, I will be voting YES in the referendum to establish a Court of Appeal. Primarily because there is now a four year waiting list for appeals to the Supreme Court and justice delayed is justice denied.
What’s it all about? Succinctly: There are two main streams of law in Ireland – criminal and civil. We already have a Court of Criminal Appeal but we have no court of civil appeal. Because of this, all civil law appeals go directly to the Supreme Court resulting in a backlog of 4 years. There are only eight judges on the Supreme Court and they generally sit in minimum groups of three. As you might imagine, the waiting list is not shrinking but growing considerably. This referendum seeks to establish a Court of Appeal for civil cases (and also allowing the Supreme Court to reassign existing cases on the waiting list to this new court as it sees fit). This new court will sit between the High Court and the Supreme Court.
Allow me to elaborate on some of the reasons why I am in favor of this referendum as well dispel some myths and untruths:
For these, any many other reasons, I will be voting YES in the referendum to establish a Court of Appeal. I hope you do likewise.
–
The contents of this posting may be used freely in whole, part or edited without attribution. Get the message out!
There’s very little good about the Seanad in its current form; it’s been broken for a long long time. So, why save it? Here’s why:
For these, any many other reasons, I will be voting NO in the referendum to abolish Seanad Éireann. I hope you do likewise.
—
The contents of this posting may be used freely in whole, part or edited without attribution. Get the message out!
Because they’re realised that the internet is full of trolls, idiots and spambots. And, seriously, who could blame them. It seems that science fact is something that can be debated with references to debunked or pseudo-scientific research (or even the Bible) in areas such as evolution and climate change.
Quite worryingly, they talk about recent research in which a fractious minority wields enough power to skew a reader’s perception of a story though the comments that follow it – and, with this, came to the decision to switch off the nut jobs:
If you carry out those results to their logical end–commenters shape public opinion; public opinion shapes public policy; public policy shapes how and whether and what research gets funded–you start to see why we feel compelled to hit the “off” switch.
Over in INEX we run a route server cluster which alleviates the burden of setting up bilateral peering sessions for the more than 80% of the members that use them. The current hardware is now about six years old and we have a forklift upgrade in the works.
BGP allows for MD5 authentication between clients (using the TCP MD5 signature option, see RFC 2385) and – while recently obsoleted in RFC 5925 – it is still widely used in shared LAN mediums such as IXPs; primarily to prevent packet spoofing and session hijacking via recycled IP addresses.
Our current route server implementation runs on FreeBSD which does not support TCP MD5 in its stock kernel (you are required to compile a custom kernel – see below for details). Additionally, specifying the session MD5 is not done in the BGP daemon configuration but separately in the IPsec configuration. Lastly, our current FreeBSD version has no support for TCP MD5 Â over IPv6. These have all led to unnecessarily complex configurations and a degree of confusion.
Because of this, we decided to test up to date Linux and FreeBSD versions for native IPv4 and IPv6 TCP MD5 support with Bird and Quagga (our route server daemons of choice).
In each case, BGP sessions were tested for:
For Linux, the platform chosen was Ubuntu 12.04 LTS with the stock 3.2.0-40-generic kernel.
tcpdump -M xxx;
The results -Â everything worked and worked as expected:
Summary: Linux will support TCP MD5 nativily for IPv4 and IPv6 when using Quagga or Bird.
For FreeBSD, we used the latest production release of 9.1. TCP MD5 support is not compiled in by default so a custom kernel must be built with the additional options of:
options TCP_SIGNATURE options IPSEC device crypto device cryptodev
In addition to this, the MD5 shared secrets need to be added to the IPsec SA/SD database via the setkey
utility or, preferably, via the /etc/ipsec.conf
file which, for example, would contain entries for IPv4 and IPv6 addresses such as:
add 192.0.2.1 192.0.2.2 tcp 0x1000 -A tcp-md5 "supersecret1"; add 2001:db8::1 2001:db8::2Â tcp 0x1000 -A tcp-md5 "supersecret2";
where the addresses ending in .1/:1
are local and .2/:2
are the BGP neighbor addresses. This file can be processed by setting ipsec_enable="YES"
in /etc/rc.conf
and executing /etc/rc.d/ipsec reload
.
tcpdump -M xxx;
The results – almost everything worked and worked as expected:
setkey
/ ipsec.conf
– setting it (or not) in the Quagga and Bird config has no effect so long as it is set via setkey
(but is useful for documentation purposes). However, trying to set it in Quagga without having rebuilt the kernel will result in an error.Summary:Â FreeBSD will support TCP MD5 via a custom kernel and setkey
/ ipsec.conf
for IPv4 and IPv6. Note that there is an additional complexity when changing or removing MD5 passwords as these need to be amended / deleted via setkey
which can put an extra burden on automatic route server configuration generators.