Until recently IP network operators were encouraged to set up so-called "bogon address filters" at the edge of their networks. These filters were intended to discard all incoming traffic where the source address in the IP header was from a block of addresses that was known to be unallocated. The inference was that a matching packet was either an unintentional leak from some privately addressed network domain or was generated using source address spoofing. In either case there is no point in delivering the packet, since it comes from a demonstrably fictitious source.
We started beta-testing User Defined Measurements (UDM) for RIPE Atlas. The first results are encouraging and we are receiving useful feedback from happy users.
We are proud to announce that over 1024 RIPE Atlas probes are now active, distributed over the whole world! This is an important milestone. It was one of our goals for 2011, and we achieved it!
RIPE Atlas can now test packet flows from more than 1000 vantage points on the Internet. We took a quick look at anycast traffic to DNS root name servers. There is a lot of interesting signal in this data.
In this article, we report about a one-day measurement of the RPKI and BGP infrastructure.
Since the RIPE NCC launched its Resource Certification service, there is a steady increase in the number of prefixes covered by certificates.
In this article we will be delving into the behaviour of the Linux implementation of TCP, and looking at the way in which TCP establishes a connection. There are socket options in Linux that cause the TCP handshake to behave in a rather curious way.
RIPE Atlas provides a view of 126.96.36.199/16 from the data plane. Can packets actually get there and back? Please find the results in this article.
The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We looked at three ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.