Possible cause of and solution for Stadium Edit app cannot connect or loses connection

[tcamuso]

My brother opened ticket #496504 to report this issue.
He was told by Line6 that he's not the only one seeing this problem, but there are not very many.
I went to see him yesterday to help him out, because I'm not having that problem.

His Stadium is connected to the WiFi and logged into his Line6 account.
His Laptop is connected to the same WiFi and logged into his Line6 account.
However, the Laptop CANNOT see the Stadium, or loses connection to it after a few minutes.
So, the Laptop can connect to Line6 through the WiFi, and the Stadium can connect to Line6 through the WiFi,
but they cannot Connect to each other.

I submitted all the information to CoPilot AI, including info on the router and ISP.
Here is CoPilot's analysis of the situation and suggestions for solutions.

Issue:
Stadium editor cannot connect or loses connectivity after a few minutes even though the Stadium remains fully online. The failure is isolated to LAN discovery, not Wi‑Fi or internet connectivity.
 

Environment:

• Stadium on Wi‑Fi

• Windows 11 editor

• ISP: Fidium

• Router: Adtran 854‑series gateway (Fidium standard)

• LAN subnet: 192.168.40.x

• Stadium maintains valid IP and Line 6 login at all times
   

Observed Behavior:

• Editor initially cannot find the Stadium or loses connection after a few minutes.

• Stadium’s Wi‑Fi remains stable (no DHCP loss, no reassociation)

• Stadium retains internet access and Line6 account authentication

• Only local discovery fails; reboot sometimes temporarily restores it
   

Technical Analysis:
The Stadium editor appears to rely exclusively on multicast‑based service discovery (mDNS/SSDP‑style). Adtran 854 gateways used by Fidium aggressively prune or filter multicast and broadcast traffic after a short period of device uptime. This results in:

• Unicast traffic: unaffected

• Internet connectivity: unaffected

• Multicast discovery: silently dropped
   

This matches known behavior of Adtran 854 IGMP snooping, multicast filtering, and band‑steering logic.
 

Why Other Devices Don’t Exhibit the Issue:
Smart TVs and casting apps use cloud‑mediated discovery or Wi‑Fi Direct, not LAN multicast. They bypass the failure mode entirely.

Root Cause Summary:
Stadium remains reachable at L3, but the editor cannot rediscover it because the router suppresses L2/L3 multicast discovery packets after a few minutes.

Proposed Engineering‑Level Solutions:

•  Add a direct‑IP connection path in the editor (bypasses multicast entirely).

• Add cloud‑assisted discovery (similar to Google Cast).

• Add a unicast beacon or fallback discovery protocol to avoid reliance on multicast. 

Any of these would eliminate dependency on consumer‑grade router multicast behavior and resolve issues with ISP‑locked gateways like the Adtran 854.

 

[tcamuso]

Meanwhile, you can to add your own router and run it in Access Point (AP) mode.
This bypasses the gateway’s Wi‑Fi filtering while keeping the same LAN/subnet.

CoPilot AI instructions and suggestions follow.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Many ISP gateways (including Fidium’s Adtran 854) aggressively filter mDNS/multicast, which the Stadium editor depends on for device discovery. The Stadium stays online, but the editor loses sight of it. A simple, reliable fix is to add your own router and run it in Access Point (AP) mode.

How to Set Up a Secondary Router as an Access PointEmpty heading

1. Connect new router to ISP gateway

   • Ethernet from gateway LAN port → new router LAN/WAN (AP mode will clarify which).

2. Log into the new router’s UI

   • Connect to its default Wi‑Fi.

3. Enable “Access Point Mode”

   • Usually under Advanced Settings.

   • This disables routing/NAT and keeps everything on the same subnet.

4. Create a new SSID

   • Example: Stadium-AP

   • Use WPA2/WPA3.

5. Connect the Stadium + your computer to this new SSID

   • Both must be on the AP’s Wi‑Fi for clean mDNS.

This gives you a clean, multicast‑friendly Wi‑Fi segment without changing the rest of the home network.

Recommended Budget Routers (All Wi‑Fi 6, All mDNS‑Friendly)Empty heading

Model	Coverage	Price	Notes
NETGEAR R6700AX (AX1800)	~1,500 sq ft	$55–$70	Best value; strong 2.4 GHz; stable multicast
ASUS RT‑AX55 (AX1800)	~1,500–1,700 sq ft	$90–$110	Most configurable; excellent mDNS behavior
Linksys MR7350 (AX1800)	~1,700 sq ft	$60–$75	Good range; reliable multicast
TP‑Link Archer AX21 (AX1800)	~1,500 sq ft	$60–$80	Easy AP mode; very stable

 

[jpdennis]

On 1/16/2026 at 10:40 AM, tcamuso said:

Meanwhile, you can to add your own router and run it in Access Point (AP) mode.

 

tcamuso,

 

Thanks for the research and information.  I hadn't thought about the issue with the default ISP routers wi-fi network.  I disable the ISP wi-fi system altogether and setup a mesh network on an independent router using a different subnet altogether.  Great information if I ever change my process.

 

jpd

[gbr13697]

On 1/17/2026 at 9:50 PM, jpdennis said:

 

tcamuso,

 

Thanks for the research and information.  I hadn't thought about the issue with the default ISP routers wi-fi network.  I disable the ISP wi-fi system altogether and setup a mesh network on an independent router using a different subnet altogether.  Great information if I ever change my process.

 

jpd

I do the same since I had problems with an ISP router being picky about what it would allow on the network.

[jpdennis]

On 1/18/2026 at 1:32 PM, gbr13697 said:

I do the same since I had problems with an ISP router being picky about what it would allow on the network.

 

gbr13697,

 

Funny story, I have setup many customer facing public wi-fi subnets for hotels, casino, etc.  It was quite a balancing act in regards to traffic shaping.  And thus my build of a secondary mesh wi-fi at home.  Thanks for the memory!  Enjoy the Stadium and play on!

 

jpd

[gbr13697]

On 1/20/2026 at 10:37 PM, jpdennis said:

 

gbr13697,

 

Funny story, I have setup many customer facing public wi-fi subnets for hotels, casino, etc.  It was quite a balancing act in regards to traffic shaping.  And thus my build of a secondary mesh wi-fi at home.  Thanks for the memory!  Enjoy the Stadium and play on!

 

jpd

I was already using mesh wifi but, when I got a router from my new ISP, my Ring Doorbell chimes stopped working along with several other items. I switched the new ISP router into "modem-only" mode and added a wired router before the mesh. And everything came back online.