I am using hostapd_cli(http://www.freebsd.org/cgi/man.cgi?query=hostapd_cli&sektion=8) to interact with my hostapd to change the channel. I am using "chan_switch" command to switch channels.
But this command gets failed with "CSA is not supported" as the error message. Any inputs on how I should go about solving this issue would be greatly appreciated.
CSA is Channel Switch Announcement; which goes inside the beacon to let connected station know that AP is changing the channel. For this things to work device/hw/firmware should able to configure CSA-IE.
In your case, either the device doesn't support CSA or it supports it but have not notified the same in its capabilities.
If you just want to change the channel, which will make stations connected to disconnect first and then reconnect, then you can just change the 'channel' field in hostapd.conf and just reload by 'kill -1'.
As per your question, I have tried chan_switch using hostapd_cli without killing hostapd. All you need to do is update your backports version, in my case, I am using backports-4.2.6-1. Just build it and then you can try chan_switch if channel switch is possible it should give OK message else FAIL. I have tried it with more than 10 interfaces at the same time and I was able to change the channel. Attached a screen shot for reference.
Hope this helps..!!]1
Related
Is it possible to write rules for sending alerts when an app node or an app space starts or stops.If yes, which method from the list can be used for the same?
It's should be simple, use below method of the appnode
AppNodeRuntimeStateInfo
of the Appnode check it's status , if it is running send an alert.
I have an issue regarding Twilio Javascript SDK and stuck in a
situation where the issue directly involve IOS and RTC support. Right
now, i cannot connect the twilio device after device is ready. There
is no error or anything to track/debug.
Constantly, running the connection.status() return back connecting always. I think the signaling system works when there is an incoming call but again, connection.accept() and status remain connecting like forever.
Application Overview
Cordova/Phonegap app
https://media.twiliocdn.com/sdk/js/client/releases/1.6.9/twilio.min.js
shim:https://webrtc.github.io/adapter/adapter-1.0.2.js
https://github.com/BasqueVoIPMafia/cordova-plugin-iosrtc
Possible reasons: Can this be directly CSP issue? or I have you setup configuration using STUN/TURN?
Let me know if you need any information. It's not going to resolve because there is no error just "connecting" status.
I am developing a web application which shows the status of the all available smart devices in my hub. and I can also control the devices from this application.
For example, if I want to turn on the switch I send "on" commands with appropriate contexts to smartthings API.
In order the send commands, the devices should be active (it should respond to commands).
And I got the state of the device through API call (device.status) but this state found with the device object is not accurate.
For example, the Econet valve is actually responding to my commands.but it states shows INACTIVE.
So I can't trust on the values get from "device.status" parameter. is there any other approach?
Update: In order to know the current value of devices and take actions according to the current value, we need to know whether the device is responding or not. Currently, we cannot rely on the device status like ACTIVE, ONLINE because even after disconnecting the devices from networks the states doesn't change.
I'm creating an access point with no Internet access. Users can view content hosted locally on a Raspberry Pi
I want a jump-off point where the user can share something on Facebook. At this point I would need them to be kicked from the WiFi network so they can use their own 3G/4G connection.
How can I force a mac address off the access point instantly without restarting hostapd?
You an use the hostapd_cli command to control the hostapd daemon.
To force a client off the wifi you can use either the "disassociate" or the "deauthenticate" command.
hostapd_cli deauthenticate 00:5e:3d:38:fe:ab
make sure you have the ctrl_interface properly set in your hostapd config!
The default is this:
ctrl_interface=/var/run/hostapd
It depends on the Client if it will reconnect right away though. This could be "remedied" by filtering his packets using iptables so he doesn't get an IP anymore and thus is highly likely to not try and connect again.
NOTE: Doing the latter with iptables might make the client "blacklist" your AP, at least for a certain time!
NOTE2: If you do not provide a default route with your DHCP-Server you should not need to disconnect them from the wifi at all. Though most devices (Smartphones) will avoid the wifi alltogether since it's not what they expect (an internet connection).
Like Badmaster's answer, the Client will try to reconnect to the AP in my case and it got connected. But in my case I want to force the Client disconnected and the AP will not accept it when reconnecting.
So I just add some codes in related function of disassociate, before it call the function hostapd_drv_sta_disassoc() in file ctrl_iface_ap.c in function hostapd_ctrl_iface_disassociate. I add codes of adding the mac address of the Client to the mac deny list in hapd->conf->deny_mac. Before make these codes working you should make sure your settings of mac access control in file hostapd.conf is right.
then then command hostapd_cli deauthenticate 00:5e:3d:38:fe:ab can force the Client disconnect and will not connect again.
At the same time, I create a function to remove the mac address from the mac deny list to allow the Client connecting.
the example of modifying source codes is as follows:
Force disconnect a P2P Client/STA from GO/AP side
hostapd: make it possible to remove addresses from maclists
The prevent your sta rejoin the network automatically, before the 'hostapd_cli deauthenticate ' cmd, you could run cmd below to enable allowed macaddr list
hostapd_cli macaddr_acl 1
Assuming the macaddr has not been added in the allowed list it will be prevented to join.
Later disable it via hostapd_cli macaddr_acl 0 so that the sta can join
During a call, if I am not actively speaking into the microphone, it appears as if there are no audio packets being sent. This is causing problems because I am tring to mix audio at the server level. It appears to be some kind of echo cancellation in the pjsip stack. Does anybody know if there is a way to shut this off?
I have tested with Zoiper and I have isolated the problem to this sdk. Thanks!
This is usually not because of AEC. You should look for something called "VAD" (Voice Activity Detection). If you find it try to change its setting or disable it.