I have installed control room and client successfully and also able to work on it. But, whenever I connect VPN, the control room disconnects automatically with the message "The requested address could not be resolved".
It seems that the control room binds with the system IP, and when connected over VPN system IP changes. As per my understanding, this could be the reason for the disconnection of Control Room over VPN.
Do you have any idea how to resolve this?
Please let me know if you have a solution for this or let me know where can I get help with this issue
yes, this is correct. and this is not an error.
Once the machine is connected to the VPN, then it is effectively on the remote network... so all local resources (including the control room) will not be reachable. most likely you are connecting to the control room using its FQDN.
so you can do one of these things:
while connecting the AA client to the control room, use its IP address instead of hostname
use split DNS on ur VPN or split tunneling
Related
I'm wring a small packet tunnel using NETunnelPacketProvider. Before starting VPN, I need to use setTunnelNetworkSettings in order to provide connected VPN settings. In this settings, I need to provide tunnelRemoteAddress for NEPacketTunnelNetworkSettings. I have noticed that this address is shown when VPN is in connected status. But I wonder if there is any other effect too or not?
Since I want ability to change my connected VPN server(e.g. changing to another server when disconnecting from one) and I were not able to change this value by using setTunnelNetworkSettings again while VPN is connected, I was wondering if this tunnelRemoteAddress is just some string for representing in UI and I can set it to just a dummy address like 127.0.0.1 or not.
Any idea?
I've bought a Wireless IBeacon Receiver BLE 4.0 WI-FI Sniffer here installed Node Red on my Synology DS414j. I've been able to configure the sniffer to use my local WLAN and I can access the webpages on the sniffer. So far so good.
Now I'm trying to connect MQTT node from Node Red to the device. Maybe I'm not understanding thing correctly but I would have expected this to work.
There is a Wiki here but that does not contain a lot of information. I tried signing on the forum but the confirmation mails never arrives.
Configuration of the sniffer:
I've added my SSID, security token for my WLAN. That works.
Device mode is configured to 'Station'
MQTT is configured to the IP of the NAS port 1883. With credentials. Topic is set to '/beacons'.
Node Red node is configured to IP of device port 1883, with credentials.
Questions:
Does it work the way I think this should work. Is it possible to have the MQTT Node Red node to connect to the device or do I need something else?
The sniffer can be put into 3 modes. Station, P2P and Access Point. I've now configured it at Station. Does anyone know what this setting means?
Node Red says 'connecting' but never connects. I've also installed a MQTT Dashboard on my Samsung Phone. It says 'connection failed'. What am I doing wrong? Do I need SSL/TLS? to be activated?
By the sound of things you have not installed a MQTT broker.
MQTT is not Point to Point you need a broker that the clients all connect to.
Node-RED does NOT contain a MQTT broker (there is node to add one, but it's not really the best approach), it is just another MQTT client.
iam trying to test my application to public network so i will use my own ip as server , i already did port forward in my router settings, " my goal is reach this application to computers out side my network " but i only can receive data i cannot send from my main ip to other computer ,, i have disabled my firewall also the other pc firewall is this problem of my router ? or my network ?
i tried to disable router firewall but still same problem is there other things i have to check ? also i set my indtCP server binding to 0.0.0.0 to reach all network.
You should be able to send, but only after the client connects to your server.
When a client connects you should handle OnConnect event of your TIdTCPServer component. AThread parameter represent your client. You can respond to it by, for example:
AThread.Connection.Write ('Hi!');
You can disconnect the client by:
AThread.Connection.Disconnect;
Of course, many clients can be connected at the same time. In this case, you should keep track on all (dis)connected clients.
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
I want to be able to have multiple iPads on a single LAN running the same app each with the ability for peer to peers broadcast.
This needs to be peer to peer broadcast (serverless) or if I have to, then I can designate one app as the local server to receive and resend events. But the information should never leave the LAN (so no cloud server).
A simple example would be an app that has a single button. Each instance of this app would be configured with a unique ID (say 1-10). When any user touches that button anywhere on the LAN all the other iPads running this app would display the number of the app instance elsewhere on the LAN where the button has been pushed.
This seems like it should be a basic capability but I am having a hard time finding if it is even possible in IOS. Can anyone confirm that it is and how to do it?
You could set it to broadcast on the broadcast ip of the lan. and use it like a multicast address.
ex. 192.168.1.0/24
broadcast/listen on 192.168.1.255
the only downfall is that it will be sent to every device on the lan.
[edit] vv
or if you designate one as the server you could advertise the servers ip address as a broadcast.