<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Looking Glass · routerjockey</title>
    <link>https://routerjockey.com/looking-glass/</link>
    <atom:link href="https://routerjockey.com/looking-glass/feed.xml" rel="self" type="application/rss+xml"/>
    <description>A curated feed of news from the networking industry, picked by Tony Mattke.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 09:01:06 -0500</lastBuildDate>

    <!--
      This file IS the Looking Glass feed. The site publishes it unchanged at
      /looking-glass/feed.xml and renders the /looking-glass/ reader from it.

      Add new items at the top, newest first, and bump lastBuildDate.
      Every item needs:
        title        the source's headline, as published
        link, guid   the article URL (guid = link, isPermaLink="true"),
                     tracking parameters (utm_*) stripped
        pubDate      RFC 822, when the item was added HERE, not when the
                     source published it
        source       url = the publication's home page, text = its name
        category     one topic: routing, security, automation, wireless,
                     dns, industry, cloud, events
        description  the excerpt the reader shows. The source's OWN words
                     only, never ours: its RSS summary or its opening
                     paragraph, at most ~120 words, with trailing
                     "Read more" links removed. Never the full article.
    -->

    <item>
      <title>Tech Firms Dismantle Botnet That Turned 1.3M TV Boxes Into Proxies</title>
      <link>https://krebsonsecurity.com/2026/11/tech-firms-dismantle-botnet-that-turned-1-3m-tv-boxes-into-proxies/</link>
      <guid isPermaLink="true">https://krebsonsecurity.com/2026/11/tech-firms-dismantle-botnet-that-turned-1-3m-tv-boxes-into-proxies/</guid>
      <pubDate>Wed, 04 Nov 2026 09:01:06 -0500</pubDate>
      <source url="https://krebsonsecurity.com/">Krebs on Security</source>
      <category>security</category>
      <description>Google said today it worked with industry partners to dismantle a botnet made up of more than 1.3 million Android TV set-top boxes that ship with malicious software which secretly rents the user’s Internet connection out to strangers and conducts advertising fraud. Experts involved in the takedown say the action is likely to sever the botnet’s access to more than 10 million additional compromised systems, including other Internet of Things (IoT) products such as Android-based healthcare devices and karaoke machines.</description>
    </item>

    <item>
      <title>The EVPN trust challenge: How to detect and contain internal MAC hijacks</title>
      <link>https://blog.apnic.net/2026/10/28/the-evpn-trust-challenge-how-to-detect-and-contain-internal-mac-hijacks/</link>
      <guid isPermaLink="true">https://blog.apnic.net/2026/10/28/the-evpn-trust-challenge-how-to-detect-and-contain-internal-mac-hijacks/</guid>
      <pubDate>Wed, 04 Nov 2026 09:01:05 -0500</pubDate>
      <source url="https://blog.apnic.net/">APNIC Blog</source>
      <category>routing</category>
      <description>Guest Post: EVPN MAC mobility enables seamless workload movement, but it can also amplify the impact of MAC spoofing. A forged MAC address can redirect traffic across the fabric through BGP, making access-layer controls, route-reflector visibility, and MAC-move monitoring critical defences.</description>
    </item>

    <item>
      <title>North Korean fake job interview led to $6.3B Binance heist</title>
      <link>https://www.theregister.com/security/2026/11/03/north-korean-fake-job-interview-led-to-63b-binance-heist/5307398</link>
      <guid isPermaLink="true">https://www.theregister.com/security/2026/11/03/north-korean-fake-job-interview-led-to-63b-binance-heist/5307398</guid>
      <pubDate>Wed, 04 Nov 2026 08:53:16 -0500</pubDate>
      <source url="https://www.theregister.com/">The Register</source>
      <category>security</category>
      <description>'It was not a single isolated breach or a simple phishing incident,' exchange says</description>
    </item>

    <item>
      <title>Cisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Software Remote Access SSL VPN Tunnel Denial of Service Vulnerability</title>
      <link>https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75</link>
      <guid isPermaLink="true">https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75</guid>
      <pubDate>Wed, 04 Nov 2026 08:53:15 -0500</pubDate>
      <source url="https://sec.cloudapps.cisco.com/security/center/">Cisco Security Advisory</source>
      <category>security</category>
      <description>A vulnerability in the Remote Access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition. This vulnerability is due to logic errors when secondary authentication is configured on a tunnel group. An attacker could exploit this vulnerability by sending a crafted request when connecting to the SSL remote access VPN. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.</description>
    </item>

    <item>
      <title>Feedback wanted: routeviews.cloud, a free BGP event viewer built on Route Views data</title>
      <link>https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/7Y3JQJYX7DZAFSYRZQ4DM76DFA2CH4HB/</link>
      <guid isPermaLink="true">https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/7Y3JQJYX7DZAFSYRZQ4DM76DFA2CH4HB/</guid>
      <pubDate>Wed, 04 Nov 2026 08:53:14 -0500</pubDate>
      <source url="https://lists.nanog.org/">NANOG</source>
      <category>routing</category>
      <description>I've been building a side project and would appreciate feedback from people who look at BGP data for a living... It is an independent project, not affiliated with the University of Oregon Route Views project. It is built on their public MRT archive (all collectors, RIBs and updates).</description>
    </item>

    <item>
      <title>The Post-AI Security Floor</title>
      <link>https://danielmiessler.com/blog/post-ai-security-floor</link>
      <guid isPermaLink="true">https://danielmiessler.com/blog/post-ai-security-floor</guid>
      <pubDate>Tue, 03 Nov 2026 12:48:30 -0500</pubDate>
      <source url="https://danielmiessler.com/">Daniel Miessler</source>
      <category>security</category>
      <description>I have some critical recommendations that I think every person and company should follow as we all go through The Hackening together.</description>
    </item>

    <item>
      <title>Help Me Make the BGP Labs Even Better</title>
      <link>https://blog.ipspace.net/2026/11/bgp-labs-further-reading/</link>
      <guid isPermaLink="true">https://blog.ipspace.net/2026/11/bgp-labs-further-reading/</guid>
      <pubDate>Tue, 03 Nov 2026 12:44:28 -0500</pubDate>
      <source url="https://blog.ipspace.net/">ipSpace.net</source>
      <category>routing</category>
      <description>I decided to add “Further Reading” sections to BGP lab exercises, containing links to vendor documentation and useful related blog posts. I naively expected to offload the job to Claude, commit the results, and move on. The “related blog posts” were a piece of cake; precise links to relevant vendor documentation turned out to be more of a challenge. TL&amp;DR: I would love to get your suggestions for further reading as PRs in the BGP Labs repo.</description>
    </item>

    <item>
      <title>HN849: Meter Acquires Packet Pushers</title>
      <link>https://packetpushers.net/podcasts/heavy-networking/hn849-meter-acquires-packet-pushers/</link>
      <guid isPermaLink="true">https://packetpushers.net/podcasts/heavy-networking/hn849-meter-acquires-packet-pushers/</guid>
      <pubDate>Tue, 03 Nov 2026 14:00:00 -0500</pubDate>
      <source url="https://packetpushers.net/">Packet Pushers</source>
      <category>industry</category>
      <description>Packet Pushers has been acquired by Meter. On this special Heavy Networking episode, guest host Scott Robohn talks with Ethan Banks and Anil Varanasi, CEO of Meter, about the acquisition. Ethan and Anil explain how this relationship will work (including full editorial independence for Packet Pushers), why it was the best move for Packet Pushers...</description>
    </item>

    <item>
      <title>Introducing Zero Wire, a hub for investigating critical Internet vulnerabilities</title>
      <link>https://blog.cloudflare.com/zero-wire/</link>
      <guid isPermaLink="true">https://blog.cloudflare.com/zero-wire/</guid>
      <pubDate>Tue, 03 Nov 2026 10:30:00 -0500</pubDate>
      <source url="https://blog.cloudflare.com/">Cloudflare Blog</source>
      <category>security</category>
      <description>Zero Wire on Cloudflare Radar pairs plain-language briefings with global attack telemetry and remediation steps. Triage critical CVEs faster and decide how to protect your infrastructure.</description>
    </item>





    <item>
      <title>[Announcement] Archival of junipernetworks.junos Collection &amp; Migration to juniper.device</title>
      <link>https://forum.ansible.com/t/44869</link>
      <guid isPermaLink="true">https://forum.ansible.com/t/44869</guid>
      <pubDate>Fri, 30 Oct 2026 09:00:00 -0400</pubDate>
      <source url="https://forum.ansible.com/">Ansible Forum</source>
      <category>automation</category>
      <description>As part of the joint effort between Juniper Networks and the Red Hat Ansible Networking team, we are announcing the archival of the junipernetworks.junos collection and the official transition to the new consolidated collection: juniper.device. This decision follows the ongoing consolidation work to unify Junos modules, simplify maintenance, and ensure long-term compatibility with the Ansible Automation Platform (AAP).</description>
    </item>

  </channel>
</rss>
