SkyQ boxes are notoriously problematic on business-grade networks for three reasons:

1. Multicast flooding — SkyQ uses multicast for video distribution. Without proper IGMP snooping, this traffic floods every port on the switch, consuming bandwidth and CPU.
2. Built-in WiFi hotspot — The main SkyQ box creates its own WiFi network. If any client connects to both the SkyQ WiFi and the main property WiFi, frames can loop back to the switch via the SkyQ's Ethernet port, triggering loopback detection.
3. WiFi mesh on Mini boxes — SkyQ Mini boxes connect to the main box via coax, but can also use WiFi mesh. If a Mini has both Ethernet and WiFi active simultaneously, it creates a bridging loop.

┌─────────────────────┐     ┌──────────────────────┐
│   Main SkyQ Box     │─────│  C1300 Switch (gi13)  │
│  (WiFi Hotspot OFF) │     │  VLAN 99 Access Port  │
└─────────┬───────────┘     └──────────┬───────────┘
          │ Coax                       │
    ┌─────┴──────┐                    │
    │            │                    │ Trunk
┌───┴────┐  ┌───┴────┐               │
│ Mini 1 │  │ Mini 2 │               │
│ (WiFi  │  │ (WiFi  │      ┌────────┴────────┐
│ only)  │  │ only)  │      │  VLAN 1 (LAN)   │
└────────┘  └────────┘      │  VLAN 99 (SkyQ) │
                            └─────────────────┘
                

Isolate SkyQ traffic onto its own VLAN to prevent multicast flooding the main LAN.

Step 1 — Create the VLAN:

switch183577# configure
switch183577(config)# vlan 99
switch183577(config-vlan)# name SkyQ
switch183577(config-vlan)# exit
                

Step 2 — Configure the SkyQ port as an access port on VLAN 99:

switch183577(config)# interface gi13
switch183577(config-if)# description Main SkyQ Box
switch183577(config-if)# switchport mode access
switch183577(config-if)# switchport access vlan 99
switch183577(config-if)# exit
                

Step 3 — Configure uplink as a trunk carrying both VLANs:

switch183577(config)# interface gi48
switch183577(config-if)# description Uplink to pfSense
switch183577(config-if)# switchport mode trunk
switch183577(config-if)# switchport trunk allowed vlan 1,99
switch183577(config-if)# exit
                

IGMP Snooping ensures multicast traffic (SkyQ video streams) is only forwarded to ports that have explicitly requested it, rather than flooding all ports.

Step 1 — Enable IGMP Snooping globally:

switch183577(config)# ip igmp snooping
                

Step 2 — Enable IGMP Snooping on the SkyQ VLAN:

switch183577(config)# ip igmp snooping vlan 99
                

Step 3 — Configure the IGMP Querier on VLAN 99:

switch183577(config)# ip igmp snooping querier
switch183577(config)# ip igmp snooping querier address 10.0.99.1
switch183577(config)# ip igmp snooping querier vlan 99
                

Replace 10.0.99.1 with an appropriate IP address for the SkyQ VLAN subnet.

Step 4 — (Optional) Configure the VLAN interface for routing:

switch183577(config)# interface vlan 99
switch183577(config-if)# ip address 10.0.99.1 255.255.255.0
switch183577(config-if)# no shutdown
switch183577(config-if)# exit
                

Cisco Catalyst 1300 switches have built-in loopback detection that works independently of STP. This is your best defence against SkyQ WiFi bridging loops.

Enable loopback detection on SkyQ ports:

switch183577(config)# interface gi13
switch183577(config-if)# loopback-detection enable
switch183577(config-if)# exit
                

Or apply to all ports globally:

switch183577(config)# loopback-detection enable
                

Check loopback detection status:

switch183577# show loopback-detection
                

View log entries for loopback events:

switch183577# show logging | include loopback
                

A complete set of diagnostic commands for the Catalyst 1300:

Quick diagnostic flow when investigating network drops:

# 1. Check if STP is flapping
show spanning-tree

# 2. Check loopback detection (SkyQ boxes often trigger this)
show loopback-detection

# 3. Check system logs for port events
show logging

# 4. Check for MAC flapping (same MAC on multiple ports)
show mac address-table

# 5. Check for physical layer errors (bad cabling)
show interfaces counters