From: Sourav <sourav.chakraborty@netcommwireless.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Clients can't connect even though hostapd is running
Date: Mon, 13 Oct 2014 14:00:35 +1100 [thread overview]
Message-ID: <543B4053.5060708@netcommwireless.com> (raw)
Even though hostapd process is running on our router still clients can't
connect to it via WiFi....error logs are as follows --
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: associated (aid 1)
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Oct 13 13:49:31 ntc_140wx daemon.info hostapd: wlan0: STA
20:64:32:57:76:e7 IEEE 802.11: authenticated
Please suggest a solution to overcome this.
--
Warm Regards,
Sourav
______________________________________________________________________
This communication contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this communication in error, please notify me by telephone immediately.
______________________________________________________________________
reply other threads:[~2014-10-13 3:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543B4053.5060708@netcommwireless.com \
--to=sourav.chakraborty@netcommwireless.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).