Looking for some assistance on my first GL router, Flint 2. My tech vocabulary is limited so I apologize in advance if I do not understand what is being asked or suggested to me at first.
We are on Xfinity 1gb service. I had a Motorola modem/ router but realized it's age and not truly getting the full 1gb+ of service. I opted to get a new modem and router setup. I have the Arris S34, dang that thing is hot to the touch, as the modem. I had another router that started with "A" but one day it decided to stop broadcasting in 5g and would not do so for over 2 hours. (also found that router is known for doing that) Lost some productivity that day. So, I returned that and after some research found the Flint 2 is a good router. I would like to get the Flint 3 but I needed it the next day.
So, now I have Arris S34 connected to Gl iNet Flint 2. The combination has worked but I had the Wifi go down twice now. Modem is up and running but the router, twice, stopped broadcasting. Not the two hours plus like the other router but for a few minutes. I turn both off and on and that seems to resolve it
I read somewhere that Xfinity, since this is a residence and not a commerical location, the DCN or DHCP address can change. They are not static but dynamic so the DCN or DHCP can change when needed. Excuse me if I got the terms wrong. I'm not 100% sure if that is the case but this is why I am here asking for assistance.
Both times it has happened, we were not working so no real loss there but still annoying and concerning that it might happen during the work day.
What does this community suggest? and any good suggestions how to proceed with setting up the router further than I have would be appreciated as well. I got to the internet and that is about as far as I got with the router. I tried searching before posting but didn't see specific answers to what I am working with.
I do have the logs if it is necessary for helping.
So it's not clear to me if it's the Wi-Fi side of the Flint v2 or if it's Flint v2 'choking' on getting a new IP assigned (via a 'DHCP renewal') from Xfinity (the ISP on the Wide Area Network/WAN) or if the ISP is flaky. Do you have any computers you can keep connected to the Flint v2 via an ethernet cable? That would help to check & isolate the problem should it occur again.
One thing to look at is to see how many other Wi-Fi access points (APs) your Flint v2 is contending against:
Aside from that, yeah, let's see some logs. They might turn up something relevant. When you post them be sure to redact anything sensitive.
Format the output using ``` on the lines before & after
Yes, as mentioned by 9b9e... , please export the logs and share them with us after the issue occurs (Wi-Fi of Flint 2 is not searchable on phone/laptop).
That way we can check further to see what happened.
Also, it is worth checking if the power supply of Flint 2 is stable or not.
If it's just a few minutes of Wi-Fi loss and can be recovered automatically (without having to manually go to the Admin Panel to on and off the Wi-Fi), it sounds more like an issue with an unstable power supply.
This looks more than odd. The router was up for ~2 min then wan started sending DHCP renewal requests. That's... non-optimal.
line 428, system.log
Tue Aug 5 09:51:59 2025 daemon.notice netifd: Interface 'wan' is now up
ln. 528
Tue Aug 5 09:53:30 2025 daemon.notice netifd: wan (10956): udhcpc: sending renew to 0.0.0.0
Tue Aug 5 09:53:45 2025 daemon.notice netifd: wan (10956): udhcpc: sending renew to 0.0.0.0
Tue Aug 5 09:53:52 2025 daemon.notice netifd: wan (10956): udhcpc: sending renew to 0.0.0.0
Tue Aug 5 09:53:55 2025 daemon.notice netifd: wan (10956): udhcpc: sending renew to 0.0.0.0
Tue Aug 5 09:53:56 2025 daemon.notice netifd: wan (10956): udhcpc: sending renew to 0.0.0.0
Tue Aug 5 09:53:56 2025 daemon.notice netifd: wan (10956): udhcpc: lease lost, entering init state
Tue Aug 5 09:53:56 2025 daemon.notice netifd: Interface 'wan' has lost the connection
It's just the first thing I noticed. It lost the DHCP-assigned IP to the Flint v2's WAN interface in about 2min. Then it couldn't get a new one. It could also be the upstream, in this case the ISP's modem presumably, flaking out.
DHCP leases are typically good for hours if not days.
Would, if it happens again, turning the modem and router off and on like I did the last time be the thing to do/test or should I try leaving it on? Given the "2 min then" line. I do not have an ISP supplied modem but one I purchased about a month ago.
To answer will.qiu, I haven't seen any power supply issues but will keep an eye on that as well.
See, that's just it: all thing being equal you shouldn't have to power cycle like this during the day, I'd certainly expect. I use home connections/ISPs too but with their supplied modems. My logs show I've had seven WAN outages so far this year lasting anywhere from 6 minutes to 5 hours all just or well after midnite. That leads me to believe it's a service window outage from the ISP. IDK about your area, obviously.
There is a feature in the GL GUI under Network -> Multi-WAN -> Ethernet Status Track that can ping a remote/WAN-side server. The notifications only show when you're logged into the GUI though. See the docs link below.
There is a way to ping a remote server & if the response fails over (x) minutes/periods the Flint v2 can automatically reboot itself but that takes some advanced setup. It's not terribly difficult but it does use a far more minimalist GUI to initially set it up ('LuCI'). The software package is luci-app-watchcat. That feature also would not show up anywhere within the GL GUI either so you'd have to keep aware it's always running.
All that said & again, this ISP DHCP/WAN IP lease/renewal 'glitch' in the logs is the first thing I noticed in your logs. Regardless I would, at a minimum, keep a computer with a cable connection to the Flint v2. That way should it happen again you can quickly flip the cable over to the modem & see if you can get a direct WAN-side IP from the ISP. 'Process of elimination' & all that.
This could all be caused by a setting somewhere in your modem that just isn't quite right for your ISP's network config. That's just speculation but stranger things have happened.
I'm learning as I am going so, take it as that. I found the information for my modem, logged in and found event log.
What I found is from Aug 5th, starting around 22:30 (furthest back it would go) until today at 19:00 local time, I have had 40+ "critical" events noted to be: "No Ranging Response received - T3 time-out". Odd that none caused internet issues or seemed to.
I guess next step is calling Xfinity. Sorry to waste time but thank you for your help.