SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have a Slackware box configured as a home server on a wireless link to my DSL / router which talks to my main workstation (Suse 10.2 currently) via an ethernet cable and to other devices around the house by wireless links. I have configured FTP, NFS and Samba services on the server.
When the server is doing low volume work (browsing on the DSL, small file transfers to and from other PCs) there is no problem. But if I do a sustained transfer of a big directory of MP3s, for example, then the server - router link will simply give up at some point (today once after 170MB transferred, then again after 280MB). Restarting the wireless access point on the router or restarting the server always cures the problem.
My question is : can anyone tell me what logs are available to help me to understand what is failing and why. All protools (ftp, samba, nfs) seem to suffer the same problem so I assume the problem is deeper in the wireless connectivity. Only HTTP does not seem to suffer but I guess this traffic is never as high in volume.
I have a Slackware box configured as a home server on a wireless link to my DSL / router which talks to my main workstation (Suse 10.2 currently) via an ethernet cable and to other devices around the house by wireless links. I have configured FTP, NFS and Samba services on the server.
When the server is doing low volume work (browsing on the DSL, small file transfers to and from other PCs) there is no problem. But if I do a sustained transfer of a big directory of MP3s, for example, then the server - router link will simply give up at some point (today once after 170MB transferred, then again after 280MB). Restarting the wireless access point on the router or restarting the server always cures the problem.
My question is : can anyone tell me what logs are available to help me to understand what is failing and why. All protools (ftp, samba, nfs) seem to suffer the same problem so I assume the problem is deeper in the wireless connectivity. Only HTTP does not seem to suffer but I guess this traffic is never as high in volume.
You should be looking at the '/var/log/syslog', 'var/log/debug' (if you have debug on) or '/var/log/dmesg'. I can't be specific since I don't know how you have your system configured.
You should see any relative errors in the 'dmesg' or 'syslog'.
If you show a listing of the '/var/log' then we could wag (wild ass guess' it. Then request the post of a particular log.
EDIT: PS; You should make sure the lease time is sufficient for the AP. Also possible limits on the AP for the IP.
You should be looking at the '/var/log/syslog', 'var/log/debug' (if you have debug on) or '/var/log/dmesg'. I can't be specific since I don't know how you have your system configured.
You should see any relative errors in the 'dmesg' or 'syslog'.
If you show a listing of the '/var/log' then we could wag (wild ass guess' it. Then request the post of a particular log.
EDIT: PS; You should make sure the lease time is sufficient for the AP. Also possible limits on the AP for the IP.
Thanks for these helpful hints. My /var/log looks like this:
I have had a look in dmesg and syslog and there seems nothing very obvious regarding the wifi interface going down. syslog has messages regarding booting up the wifi interface. I have upgraded to the latest madwifi drivers from source and this seems to have improved matters a little, but the wifi link still seems to go down at random times and expecially if used intensively. I have checked the lease time and increased it form one hour to six hours. Was not sure what you meant by limits on the "AP for the IP"? If I cannot get any clues from the logs then I was going to try to install kernel 2.6 rather than 2.4, which I opted for when I first installed Slackware 11. I was somewhere that 2.6 was better for wifi connectivity - is thie correct?
....I was somewhere that 2.6 was better for wifi connectivity - is thie correct?
Thanks
My experience is I couldn't even get my wireless adapter to run under 2.4 kernel. Once I compiled my own 2.6 kernel, not only did my wireless network begin to operate, so did my USB mouse, and my flash player became able to play sound as well as video when I went to Youtube.
I recommend compiling a custom kernel of your own, not using one of the pre-compiled ones that come with Slackware. You will need to compile file system support directly into the kernel. The generic 2.6 kernels that come with the Slackware distribution rely on modules to load the file system. Can you say kernel panic?
Sometimes it's a hardware problem with wireless device - it's not so uncommon behaviour at lower-end models when wifi device is 'choked' by high loads or too much open connections.
I would first try to exchange with other AP model if you have the possibility.
Another possible problem would be channel conflict. Other wireless devices in proximity of your AP causing conflicts. You could do a scan to see if a neighbor is using the same channel. Some wireless phones have caused problems with certain APs' with overlap.
Another possible problem would be channel conflict. Other wireless devices in proximity of your AP causing conflicts. You could do a scan to see if a neighbor is using the same channel. Some wireless phones have caused problems with certain APs' with overlap.
Cell phones and microwave ovens also use the same band as APs and wireless cards.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.