I've noticed that my GL.iNet travel router continuously sends out every 30 seconds "captive.apple.com" requests, even though I'm using it as a temporary replacement for my main router.
Could someone please help me with the following questions?
What is the main purpose of these constant "captive.apple.com" requests, especially since I don't own any Apple devices?
Is there a way to manually enable or disable these requests via the command line?
Could these requests potentially expose my travel router when using public WiFi at hotels or other access points?
Is the GL router connected to your upstream router in repeater mode?
If so, this log is appearing the router checking for the existence of a captive portal page on this WiFi, and the captive.apple.com is used for checking the reply only.
It is a feature of the firmware and cannot be removed and cannot be disabled.
It will not be exposed that you are using a travel router. Also, GL firmware now supports random MAC address which makes it difficult to track.
I appreciate your response and the valuable insights you've provided.
Before designating my travel router as the main router for temporary replacement, I connected it as a repeater using the highly user-friendly GL.iNet web UI.
During my routine traffic review, I observed constant requests to captive.apple.com, which led me to ponder whether it would be beneficial, performance-wise, to disable this feature when using the router as a main replacement.
Given your clarification that this is part of the firmware, I acknowledge the existence of this feature.
Your explanation has alleviated my concerns regarding captive.apple.com.
If it's agreeable with you, I would like to designate your last response as the solution.
This feature is necessary for the Repeater function.
When the Repeater is connected to a public WiFi, it may be that the WiFi has Captive Portal. It needs to depend on this function to detect whether there is Portal.
For ordinary consumer users, if he does not know the existence of portal, the router has been unable to connect to the Internet, which may cause users to think that GL devices have problems, but actually it has portal but has not been logged in/certified.
I would like to reiterate that function is only used for portal detect and has no other effect. If you have any questions about this, you can capture the package to check the network package of GL router at will.
I must commend your team for the exceptional dedication they demonstrate in addressing your customers' queries within this forum. Your approach is a beacon of excellence and a refreshing change in the industry.
Over the years, I have utilized network equipment from various vendors. Regrettably, not all of them have shown the same level of commitment and empathy that you exhibit in your customer interactions.
Thank you for your kind support and Happy Wednesday
Thank you again for your compliments and encouragement.
Your encouragement will make us more motivated to do whatever any issues users encounter.
This is also the credit of our entire team. I will tell my colleagues to get that their strives have yielded responses and satisfied our users questions. Only these excellent work and professional ability can achieve such satisfying results.
I find great pleasure in perusing this forum, gathering knowledge, and formulating innovative ideas. Consequently, I anticipate having more questions regarding hypothetical scenarios and theories related to your GL.iNet products.
Please expect further friendly inquiries in the future.
