Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Does anyone have experience with a disappearing wifi access point (AP)?
Is there anything that a cable modem might do to provoke this event?
All is working fine. Workstation wifi activity stops at random intervals. It will return at random intervals. I can power-off restart the AP/router to restart net activities, but it will eventually disappear at a later time.
I've used a wifi analyzer app looking for the AP. It is completely gone and not simply -200 dB or similar.
I've tried to treat it as an AP whose SSID is hidden, but that did not work either.
If this is a hardware or other AP/router issue, I guess that it means I need a replacement. Any suggestions for something to cover a 2600 sq-ft ranch house?
Before you ask, the failing AP/router is a D-Link DIR-655 that has been working well for quite some time. It is connected to a cable modem for internet service.
The wifi went TU on one of my router's many years ago in a similar fashion and a replacement would be my first suggestion. Since you already created a similar thread with a post will have this one closed.
Dan, what's "quite some time"? Routers do seem to wear out after a time...I get around 7-8 years out of them.
I'm currently running a pair of TP-LINK devices. One is router-WAP at one end of the house, the other is a range extender for the far end of the house. (2000 sq.ft. ranch) I won't bother with model numbers -- they're both obsolete -- but they're working fine (so far).
Dan, what's "quite some time"? Routers do seem to wear out after a time...I get around 7-8 years out of them.
I'm currently running a pair of TP-LINK devices. One is router-WAP at one end of the house, the other is a range extender for the far end of the house. (2000 sq.ft. ranch) I won't bother with model numbers -- they're both obsolete -- but they're working fine (so far).
I've mostly used Linksys® until they went screwy (the company not my boxes), then I started using Netgear® because we used that at work and I had knowledge and experience with them. I have NEVER seen an AP/SSID "disappear" and "return" if it was powered on. After all, it is a radio station broadcasting and identification.
In this case, the network (ISP) service entrance is in one corner of the house. The master suite is opposite. Other bedrooms and the kitchen occupy the other corners with the family space in the center. There is no in-wall network wire and no cheap/easy way to add them. I think net-over-powerline (NOPL) might work, but I've never tried to run an AP downline on a NOPL.
The family desktop box is near the service entrance and could connect to the cable modem directly. NOPL to somewhere else to move the AP near the center of the living spaces. A direct connect to the cable box would leave the desktop out of the wifi lan segment so I'd likely need to add wifi parts to it (ugh! winXX). I could also add a second NOPL port. These folks are very light users so they won't require giga-anything.
I've mostly used Linksys® until they went screwy (the company not my boxes), then I started using Netgear® because we used that at work and I had knowledge and experience with them. I have NEVER seen an AP/SSID "disappear" and "return" if it was powered on. After all, it is a radio station broadcasting and identification.
In this case, the network (ISP) service entrance is in one corner of the house. The master suite is opposite. Other bedrooms and the kitchen occupy the other corners with the family space in the center. There is no in-wall network wire and no cheap/easy way to add them. I think net-over-powerline (NOPL) might work, but I've never tried to run an AP downline on a NOPL.
The family desktop box is near the service entrance and could connect to the cable modem directly. NOPL to somewhere else to move the AP near the center of the living spaces. A direct connect to the cable box would leave the desktop out of the wifi lan segment so I'd likely need to add wifi parts to it (ugh! winXX). I could also add a second NOPL port. These folks are very light users so they won't require giga-anything.
Thanks in advance,
~~~ 0;-Dan
The first failures I had were with a Linksys router...replaced with Netgear. Then my Linksys AP went south. Again, these were over 7 to 8 year intervals...I've been running an in-home network here forever
I have had good experiences, as I've said, with a router/WAP near the IPS modem and an "wireless range extender" to get to the other end of the house. I'm not sure brand matters that much. I got a good deal on the TP-LINK devices on Amazon, is all.
As I type, there are two wired clients and 13 wireless clients reported by the main router which is also supplying dhcp service.
michaelk: I'll follow in the other thread from now on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.