Cyconet Blog » routing

(old) L-root DNS Server “stolen” (for a short time)

cyco — Tue, 20 May 2008 08:20:02 +0000

After shutdown of the old L.ROOT-SERVERS.NET the IP address formerly associated with it, the IP continued to answere requests. More informations can be found at the ICANN Blog
UPDATE: Before bothering around, if you read the ICANN Blog, you realize that the issue was fixed very shortly. The whole problem is, that the file of the root DNS servers have to be keeped up to date. This issue should be fixed by operator of resolving nameservers (usually your ISP). A goody will be, to have this fixed by the next point release of debian, but it is NOT security critical.
Thanks Thijs for make me sensible that my article may misslead people who are not reading the referenced document.
UPDATE 2: A more technical description can also be found at Renesys Blog and a disussion how it is related to debian.

Routing Suite in an ISP environment?

cyco — Tue, 19 Feb 2008 23:21:10 +0000

Searching for an alternative for our old Cisco Border Router we are evaluating some software routing suites on “normal” server hardware.
First we tried Vyatta, but the routing software frequently crashed completly. Maybe this is fixed with VC4 Alpha 1, but we didn’t test that.
Next try was the development version (0.99.9) of quagga from Debian testing, but it looks like a peering with one of our cisco router fails after the hold timer expires.

2008/02/19 15:08:06 BGP: Performing BGP general scanning
2008/02/19 15:08:06 BGP: scanning IPv4 Unicast routing tables
2008/02/19 15:08:06 BGP: scanning IPv6 Unicast routing tables
2008/02/19 15:08:07 BGP: Import timer expired.
2008/02/19 15:08:13 BGP: 192.168.96.2 rcvd UPDATE w/ attr: nexthop 212.202.214.150, origin i, localpref 100, metric 0, path 20676 2914 2914 2914 2914 4755 4755 4755 4755 4755 9583
2008/02/19 15:08:13 BGP: 192.168.96.2 rcvd 124.7.35.0/24
2008/02/19 15:08:13 BGP: Zebra send: IPv4 route add 124.7.35.0/24 nexthop 212.202.214.150 metric 0
2008/02/19 15:08:17 BGP: 192.168.96.2 sending KEEPALIVE
2008/02/19 15:08:17 BGP: 192.168.96.2 KEEPALIVE rcvd
2008/02/19 15:08:17 BGP: %NOTIFICATION: received from neighbor 192.168.96.2 4/0 (Hold Timer Expired) 0 bytes
2008/02/19 15:08:17 BGP: %ADJCHANGE: neighbor 192.168.96.2 Down BGP Notification received

Any ideas are welcome … also some other routing suite alternatives.

Our Prefix did hit the routing table

cyco — Mon, 12 Dec 2005 09:54:16 +0000

On Friday at 11:47:19 +01:00 our prefix did hit the BGP routing tables …. So AS20646 managed to fix their filters.
Also the reverse delegation was set up today, so we took another step forward.

Routing Registry Training Course and irrtoolset

cyco — Tue, 29 Nov 2005 22:34:32 +0000

Last week I passed the course, what famouse news. ;-)

It is nice to know, what is needed to write ASN-, route-, aut-num objects and so on .. to autogenerate filterconfigs in theory. In the course, I got rtconfig segfaulting on the testground server. Yes .. thats good point to start. :(

This week I did modify our database objects and play around with rtconfig … as result … rtconfig didnt work as aspected. Many of the filterlists arent build, cause I got many “Warning: filter matches ANY/NOT ANY”. Maybe this an effect of our aut-num object, which reflects the outbound policy depending on downstream ASN with different prependings. But I’m unable to find any hints whats the real problem.
Maybe its rtconfig itself, cause I got it only running on debian/sarge with a backported package which I found there. The pkgsrc-package on NetBSD core dumped. Some investigation did unearth, that the irrtoolset depends on many old libs … how bad!

The question which comes to my mind … is anybody out there using irrtoolset in production??