I want to create a whitelist on the Central device. Because there is a lot of peripheral devices around and I just want to connect one peripheral device. First I register the address of the central device to the peripheral device. When I work with a single peripheral device and a single central device, connection establishes and I can send commands from the central device to the peripheral device. But when I have more than one peripheral device in the vicinity, I can not send commands to the peripheral device registered from the central device. So I decided to create whitelist on the central device to connect the peripheral device which I registered before. But I don't know how to create a whitelist on the Central device. Do you have any example? (except ble_app_hrs)
Related
I need to setup a secure home network from a Broadband Modem input to a wireless and LAN to support a webserver, email server, Printer, multiple PC's.
I use DRC Shields Up to test my network is stealthy currently but I don't know If my Broadband Modem and router is able to add an email server and webserver so I can look at faster Broadband which doesn't support webspace and emails like my current ISP.
Should the servers be on one PC running in the DMZ or behind the firewall?
DMZ is more secure but there are many pluses/minuses
I have many IoT clients that will soon be in the field. I want some way to have full access to the Device Portal currently on port 8080 without it being publicly exposed.
My thoughts are to develop a management server that accepts connections from multiple clients with keep alive. The connection from the IoT could be net sockets but that is open for feedback.
The management server would show the connection status of each IoT device. It would have the functionality to launch a browser session with the connected IoT device. The IoT device would serve the local Device Portal:8080 through the socket to the management servers browser session. Interaction from the management servers browser session would be transmitted back through the socket and in turn interact with the Device Portal.
I have looked over information for a few days and can’t find examples of website interaction through sockets. I request your feedback on such an approach and also ask is there are any open source projects that may assist in getting to this goal.
Thank you
Have a look at https://openport.io. It does exactly what you ask.
A socket is just a software representation of a TCP connection. Ports would still be required. At least 1 port anyway. If you are accessing all those devices on the same network, you can use a reverse proxy or a VPN for external access into your network and those devices. Always use an SSL cert or IPsec Tunnel for the Proxy or VPN connection. If you open up your firewall on 80 and/or 443 to your Apache web server, apache could redirect to the backed 8080 port. Alternatively, OpenVPN could be used to give you access to the entire network by just opening port 1154 and setting up the configurations. If using OpenVPN, you would still route to the device portal on 8080, as usual, using your internal IP or host name.
If all your devices are on the same network, the nice thing about using VPN to get in is that you can connect to OpenVPN on your cell phone and then connect via SSH with an app like Termius on IOS, or any other SSH capable IOS App to your IoT device, and get things done quickly; like rebooting IoT devices, setting permissions, checking logs on the go.
Lastly, if your planning to pay for Azure, you could do that, I guess ($$$)
https://azure.microsoft.com/en-us/pricing/details/iot-hub/
Setup:
Windows 7 host
Vmware workstation running Oracle Linux guest
I have a static IP assigned to my guest OS (Can be accessed only from office-LAN or with VPN). Using the bridged network , everything works fine. What setup needs to be done when i have to access this VM over wireless network (When my host is connected to wireless internet connection at home) ?
The static IP over wireless can only be accessed once i am connected to VPN.
Go to bridged networking, choose 'Bridged to' adapter to your wireless adapter. Usually Bridged to' adapter will be ethernet adapter.
It is possible to register a domain name with the IP address of the wifi network to use it later in iis.
I've tried the website is only Displayed for computers That Same are connected to the WiFi network does not Appear in the other network.
It's POSSIBLE to do this, but why would you want to? Most WiFi "network" devices are Wireless Access Points and/or hubs that already have an embedded port80/443 web service. You would be pointing a domain to a pre-existing (and non-modifiable) host.
Can you be more specific about what you want to do?
We want to receive signals in Windows Azure Cloud Service and would like some feedback on our strategy.
Our current Project:
Physical GPS unit that runs as a client.
Windows Azure Cloud Service that runs as a server.
1) Physical GPS unit: We are using XT-4000[Xirgo Technologies] physical Gps unit which is a powerful tracking, monitoring and control gateway device. This device requires UDP or TCP port to communicate.
2) Windows Azure Cloud Service: Here we need to open up a TCP listener, which will listen for incoming data which is pushed by the device [XT-4000].
Here's what we are thinking our strategy should be. All advice is appreciated.
Using Worker Role.
Set the TCP listener for receiving incoming signals from device.
[But the question is what should be the IPaddress and port no. of Windows Azure Cloud Service as the device needs to send the data with the help of IPaddress and port no.]
The following command will be SET in the device to push data
Command for the device
“+XT:1001,<Port no>,<IPaddress>,<1>”
1) You can have any port number that you want (UDP or TCP). Just set it in the config file for the service.
2) The IP address will be a little tricky. Once you deploy your service you will be assigned a VIP. This will not change SO LONG AS you do not delete the service. If you do, you will lose the VIP & the devices will stop working. It would be better if the device could accept a URL, which would eliminate the problem entirely. Regardless, once deployed you can still update the service, but you will need to use upgrade vs delete/redeploy or VIP swap.
Pat