For the latest on our response to Coronavirus (COVID-19), click here.
Connecting wireless devices through my 2Wire i3812V router
I'm having major problems connecting wireless devices through my 2Wire i3812V router. I've been unplugging and rebooting the router several times a day for the last several days -- after returning from vacation -- absolutely not the quality of service I expect from AT&T.
The router's console LAN->Status page, in the "Interfaces" section, shows two active and two inactive devices on the wired router, and zero active zero inactive on the wireless. In the "Devices" section, with inactives hidden, it shows three wired and two wireless. The two wireless are the Wii and an older Gateway laptop.
When I show inactive devices, I have an additional nine wireless devices -- a wi-fi printer, several iPhones, and a couple more laptops. None of these devices can connect to the wireless network. I've restarted devices, restarted the router via the web UI, and pulled the power cord on the router... Most of the time, whichever device I'm working on, will eventually work, and I'll go on about my business, only to have someone complain an hour or two later that such-and-such other device isn't working.
My iPhone at the moment is getting a 169.254.x.x address when it tries to connect to wi-fi -- which from what I can tell means that the DHCP server is not supplying an address. Why not? I've rebooted the iPhone, and restarted the 2Wire router... what's the problem?
I just now turned off the wifi on my iPhone and turned it back on -- it again came back with the 169.254 address. I refreshed the event log and system log on the router's webUI -- there are no messages about a DHCP failure.
While I was writing this, my wife turned on her iPhone and her iPad -- both devices seem to be working over the wifi, but only the iPhone shows up as an active device on the router's webUI. The iPad still shows up as "not connected" or "off" depending on which list I look at. I forgot and re-connected the wi-fi on my iPhone; it still claims to connect but fails to receive a DHCP address.
Any suggestions how to troubleshoot this? I'm really scratching my head over this one...