Xfinity Update Killed my WireGuard Servers?

Technical Support for Routers VPN, DNS, Leaks
1

I have 2 WireGuard servers that have been working flawlessly for more than a year until yesterday. Now it appears the Xfinity made some change that is blocking both of servers, with slightly different error messages.

Location 1 (my house)
Internet: Xfinity X1 with advanced security turned off and port forwarding on
Router: AX1800 Firmware 4.6.11 sitting behind the X1 (ethernet connection)
X1 IP set to 10.0.20.1, WireGuard set to 10.0.0.1/24 (no conflict)
Timezone: New York (correct)
IPv6 is turned OFF on the AX1800 (the error includes IPv6?)

Note: checking ipaddress.com I see both IPv4 and v6 addresses. I know this is common, I believe this is new for my account.

Error message: (includes IPv6???)
Sat Mar 22 15:13:43 2025 daemon.notice netifd: Interface 'wgserver' is now up
Sat Mar 22 15:13:43 2025 daemon.notice netifd: Network device 'wgserver' link is up
Sat Mar 22 15:13:43 2025 kern.info kernel: [ 4953.802736] IPv6: ADDRCONF(NETDEV_UP): wgserver: link is not ready
Sat Mar 22 15:13:43 2025 user.notice firewall: Reloading firewall due to ifup of wgserver (wgserver)

Location 2 (friend’s house)
Internet: Xfinity X1 with advanced security turned off and port forwarding on
WireGuard: MT3000 Firmware 4.7.4 sitting behind the X1 (ethernet connection)
X1 IP set to 10.0.0.1, WireGuard set to 10.20.0.1/24 (no conflict)
Timezone: New York (correct)
IPv6 is turned OFF on the MT3000

Error message:
Sat Mar 22 14:52:20 2025 daemon.notice netifd: Interface 'wgserver' is setting up now
Sat Mar 22 14:52:20 2025 daemon.notice netifd: Interface 'wgserver' is now up
Sat Mar 22 14:52:20 2025 daemon.notice netifd: Network device 'wgserver' link is up
Sat Mar 22 14:52:20 2025 user.notice firewall: Reloading firewall due to ifup of wgserver (wgserver)

2

Hello,

Both 2 logs reported no errors, and are some regular WG server startup information.

But indeed there is a little difference,

  1. My AXT1800 (v4.7.0) startup process (the first section is that IPv6 is not enabled, and the second section is that IPv6 is turned on) has not reported IPv6: ADDRCONF(NETDEV_UP): wgserver: link is not ready

    image
    image1060×346 14.5 KB

  2. MT3000 does not have issue, and these logs have no exceptions.

How about the situation of WG connection is? does it unable to connect on the external WG client?

Please refer to the following guide to check:

1 Like