DDoS attacks continue to be a wide-spread problem on the internet. Their size has grown over the past few years to where BGP Blackholing to reduce collateral damage has become widespread.
One of the things I noticed when I received a 32-bit ASN was that I was unable to use my ASN in my BGP communities.
If you’re using Slack then you should already know how easy it is to integrate almost anything into slack using its web APIs. If you’re not already using Slack, what are you waiting for?
Yesterday morning the company I own, Hextet Systems, was assigned AS 395089 from ARIN’s pool of ASNs. By mid-afternoon I had turned up BGP with my first uptream for IPv6, and was advertising a /44.
Earlier this month the local Internet Exchange I’m involved with received some reports of spam coming from the MBIX Peering LAN IP space.
Normally an Internet Exchange’s Peering LAN IP space is not announced to the world via BGP.
I recently renamed my internal LAN domain name. For some crazy reason I’d thought .int was not a public TLD and didn’t check at all before using that before the last time I renamed my internal LAN.