<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>linx on Me &amp; Life</title><link>https://karlaustin.com/tags/linx/</link><description>Recent content in linx on Me &amp; Life</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Sat, 04 Mar 2017 18:41:30 +0000</lastBuildDate><atom:link href="https://karlaustin.com/tags/linx/index.xml" rel="self" type="application/rss+xml"/><item><title>Peertools: Automated notification of unsolicited BGP Open requests at peering points</title><link>https://karlaustin.com/posts/peertools-automating-notification-of-potential-peers/</link><pubDate>Sat, 04 Mar 2017 18:41:30 +0000</pubDate><guid>https://karlaustin.com/posts/peertools-automating-notification-of-potential-peers/</guid><description>The Problem When you connect to an internet peering exchange, the IP addresses you&amp;rsquo;re given for your interfaces will most likely have been used by someone else prior to you, that has left the exchange.
This means, because we&amp;rsquo;re not all good at housekeeping, that you&amp;rsquo;ll end up with ISPs trying to open up BGP sessions with your routers and if you&amp;rsquo;re not firewalling them out then you&amp;rsquo;ll end up with a lot of messages about BGP Opens being received from unconfigured neighbours.</description></item></channel></rss>