Brand new XB7 gateway drops all connections every hour

@user_8c3815​ 

IPV6 might not be your issue though.  You are running high on downstream power.  That can potentially  cause a lot of com fails, even spontaneous reboots, so if you are trying renew a DHCPv6 lease, that conversation may break (82/24 errors) resulting in a temporary routing problem for your internal clients until that conversation can take place.  You aren't showing uncorrectable errors in that post, but I don't know if logging works on their stuff or not, or what it triggers on, and might not even trigger on UDP protocol (closed source firmware). 

Before you do anything, try to get the line back into spec: https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0   Power levels will drift over time as well. Try to get that downstream power between -7dBmV and +7dBmV (yes, you can see negative values).  If you search on amazon for "Forward path Attenuator", a cheap fix ($10-$15) may be a -6dB attenuator.  That knocks the downstream power down a bit without touching the upstream going out.  If it works better, great, if not, you're out $10 bucks.   You need to do something with the signal first anyway before debugging it.

The firewall is just telling you it blocked something.  It doesn't tell you what that was.  If you got a connection flaking out, it might be fragmented or runt packets driving up the counts along with the usual script kid/compromised cloud/compromised iot gear/compromised user traffic. 

@flatlander3​ Do you think the power thing is related to the IPv6 firewall logs? During a support call a few years ago when I last had Xfinity internet, the rep noticed something related and said "hold on let me change some power level in our system" and asked if it was fixed, but it didn't end up resolving it. It was a brand new house too. Regarding the adapter thing, shouldn't Xfinity pay for those?

@flatlander3​ It seems like it's not only the downstream power levels that are off, but the upstream. Here's how it looks today, some < 35

@user_8c3815​  Upsteam starts out low after a reboot and slowly increases as needed after a reboot to establish communication.  It adjusts itself.  When it creeps past 50 dBmV is typically when my stuff has issues.  If it started out high, you'd likely be having issues pushing signal out through a bad splitter or connector, but that doesn't seem to be happening.  That might point to another problem though.

If you look at your DHCPv6 attempts, that renew/rebind attempt?  It should happen on regular intervals.  Right down to the minute.  If they are working on stuff in your area, that duration might be really short -- an hour or so for a rebind, but in your case they are staggered at odd intervals.  That should happen at regular times, down to the minute.

You might be spontaneously rebooting too (look for the lights flashing on your gateway).  During boot, before the channels are connected and bonded together, a DHCP attempt to Xfinity to get your IP address will fail, and you will see that 82/24 error too because you got nothing from them (that's just part of the conversation that takes place).  It will retry, then, it must succeed at some point because it doesn't throw an error again.  The retry interval is unknown (closed source), and your crippled gear records no log of the retry.

You can have a tech come out.  Flip a coin with that.  They might install an attenuator, or they might look at it with their test gear and conclude it's fine -- normal for your neighborhood, or their gear may be more forgiving on signal.  What matters is what your gear sees and if it works or not.  There may be another issue with noise being injected on the line too they can find we can't see, or another problem.  Your gateway has no debugging capability for anything else.

When a drunken neighbor ran over the cable box in the neighborhood, my signal power suddenly shot up  when they "fixed the cable", and it was a quick fix for me.  That may or may not be the root cause of your issue, but for $10 bucks and no hassle, it could be something to try.  Screw it on the back of your gateway.     

As far as being able to debug and control the networking part if that doesn't fix the issue, you would need to bridge mode the gateway, and use something that can do that part.  Consumer routers just don't have much control and have no logging.  You can control everything with linux or BSD, and there are a couple of distributions out there that are already setup to be firewall/routers that make it easy.  

You do need to fix the signal part first, no matter how you do it, or it won't matter what you do.

Hello @user_8c3815 thanks for contacting our Xfinity Support Team over our Forums. We appreciate you reaching out to us and sharing the logs from your equipment. We see that you are having issues and we are here to be part of the solution. In order to get started, can you please send me a private message to Xfinity Support with your full name and full address by clicking the chat icon in the top right?