Hi, I'm Iljitsch van Beijnum. This page has all posts about all subjects.
My first day on the job (so to speak) as contributing writer for Ars Technica I got to combine my two areas of interest: IPv6 and Apple. The Airport Extremes gained IPv6 capability, but this was not firewalled despite the box saying there's a firewall inside.
Permalink - posted 2007-02-15
OpenBSD, the security conscious sibling in the BSD operating system family, has its own BGP daemon implementation: OpenBGPD.
Permalink - posted 2007-01-30
As Zebra progress has been glacial, a group of people created a fork under the name Quagga. Quagga is more community-based and a somewhat better choice than Zebra in an operational environment.
Permalink - posted 2007-01-30
2006 was another busy year for the five Regional Internet Registries: together, they gave out 161.48 million IPv4 addresses, just shy of the 165.45 million given out in 2005 as measured on january first 2006. Lots more information in the 2006 IPv4 Address Use Report.
Permalink - posted 2007-01-01
2006 was another busy year for the five Regional Internet Registries: together, they gave out 161.48 million IPv4 addresses, just shy of the 165.45 million given out in 2005 as measured on january first 2006.
Permalink - posted 2007-01-01
If you want to use the BGP routing protocol, you need an Autonomous System number. These AS numbers were 16 bits in size until now, allowing for around 64000 ASes, and more than half of those have been given out already. To avoid problems when we run out of AS numbers, the IETF came up with modifications to BGP to allow for 32-bit AS numbers, as I explained in a posting about a year ago.
Obviously, at some point someone has to bite the bullet and start using one of these new AS numbers. This bullet biting may happen fairly soon, as the five Regional Internet Registries have all adopted, or are in the process of adopting, the following policy:
So what does this mean for people who run BGP today? Not all that much, really, because the changes to BGP to support the longer AS numbers are completely backward compatible. The only change is that you'll see the AS number 23456 appear in more and more places. In routers that don't yet support 32-bit ASes, the special 16-bit AS number 23456 shows up as a placeholder in places where a 32-bit AS is supposed to appear.
If you have scripts that perform AS-related operations on the Routing Registries (such as the RIPE database), you'll have to adjust your software to parse the new format for 32-bit AS numbers. They are written down as <16bits>.<16bits>, for instance, 3.1099 is a new 32-bit AS number and 0.23456 is the 32-bit version of AS 23456. However, this format isn't standardized so 32-bit AS numbers may show up differently in your router. Have a look at the RIPE announcement.
As soon as the first 32-bit AS number appears in the wild I'll report it here so you can check whether it shows up in its full 32-bit glory or as 23456. In the mean time, you may want to ask your router vendor for 32-bit AS support. At least one of the big vendors isn't implementing it in all of their lines just yet because they claim there is no customer demand for it.
Permalink - posted 2006-12-29