I don't know if this is possible, but I'd like to get a count of how many "connected devices" there are on a virtual network in Azure. You can see a list of all connected devices in the Portal (Settings -> Connected devices), but I can't figure out how to get a count using Kusto QL in the Azure Resource Graph Explorer. When I run a query to pull all the info from a virtual network, I can't find anything related to connected devices in the "properties" output, so maybe this just doesn't exist in this format. Any ideas?
My end goal is a list of all our vnets, sorted by a count of connected devices.
Related
Is there a way to get a full record of all the times a specific device with a Host module agent installed was online (ie. turned on) using the Teamviewer API? Which API call should I use for this?
I've created a device template for my IoT Edge in Iot Central.
I'm able to see the modules running on my device through (Devices-> Group of my device-> My Device -> Modules) and confirm it connecting to my IoT Edge and running sudo iotedge list.
I can also manage it and change the module twin desired properties through (Devices-> Group of my device-> My Device -> Manage) but I cannot see my telemetry data showing up.
In Analysis tab it is also possible to count the ocurrence of those specified fields in telemetry message, capabilities in device template.
Do you guys know what could be happening and what should I do to troubleshoot it?
Thanks in advance!
Device dashboard view
Analysis dashboard view
It was a mispelling in the code.
Aparently in Analysis tab it was counting the message quantities but not it's intent.
I'd like to know that a specific device (phone/tablet) has joined my WiFi network created by ESP8266 microcontroller. It shouldn't require any installed apps on that phone/tablet, if possible, to simplify the whole setup.
So I think I need to somehow identify connected clients, and MAC is not an option because it is subject to change randomly on, say, Apple devices.
Maybe it's possible to collect host names of connected clients?
I know that Windows and Ubuntu clients send their host names when getting IP from DHCP server (see here). Also, it's possible to find such information on, say, home Wi-Fi router admin web page (i.e. host names, their IPs and MACs).
I'm running DHCP server on ESP8266, but I haven't found any API that allows to get peer host name (i.e. reverse DNS). Does ESP8266 support getting such information?
I have a scenario of two P2P groups ,each with one AP-client pair.They are independent P2P groups.I am curious to know what will happen if the two P2P groups come close to each other?
TLDR;
The groups will not effect each other.
The WiFi Direct specifications states that devices must be in the FIND phase in order to find more peers to connect to, and even if they were, they wouldn't try to connect unless they were running an app that told them to disconnect from their current group and connect to a new group if they find one.
Two group owner devices can connect to each other if that feature is supported in the particular implementation of Wi-Fi Direct on the devices you are using, and if it supported by the Wi-Fi chip on those devices. According to this paper, it's possible for a device to be a group owner in one group, and a client in another group by time-sharing the Wi-Fi interface:
In order to act both as P2P Client and as P2P GO the laptop will
typically alternate between the two roles by time-sharing the Wi-Fi
interface.
On the other hand, it is impossible to have a group with two group owners. The Wi-Fi direct groups will still be separate from each other, there will simply be a group owner in one that is a client in the other.
According to this article
Some of the capabilities, such as concurrent P2P group and AP
connections, will add complexity to product designs at both the IC and
Wi-Fi subsystem levels. A product will have to maintain multiple MAC
entities to support concurrent operations and most likely will require
concurrent communications on multiple Wi-Fi channels. Clearly the
feature will be valuable, but will it be worth the extra cost required
to implement it? That’s up to the designer to decide. Over time, the
market use, or not, of those features will make that decision easier.
So as far as I understood basic mode is single p2p group per device and since device bound to one group it will not jump in immediately to another group.
Android Classes Reference can be find here
Attempt of implementation can be found here
if device supports more then 1 group it will registered by 2nd group manager as available peer and then any member of group can TRY to connect to device. Device should have some WPS like security or for mobile phone popup dialog.
More on security from Wikipedia:
Wi-Fi Direct essentially embeds a software access point ("Soft AP"),
into any device that must support Direct.[9] The soft AP provides a
version of Wi-Fi Protected Setup with its push-button or PIN-based
setup.
When a device enters the range of the Wi-Fi Direct host, it can
connect to it, and then gather setup information using a Protected
Setup-style transfer.[9] Connection and setup is so simplified that
some suggest it may replace Bluetooth in some situations.[12]
Soft APs can be as simple or as complex as the role requires. A
digital picture frame might provide only the most basic services
needed to allow digital cameras to connect and upload images. A smart
phone that allows data tethering might run a more complex soft AP that
adds the ability to bridge to the Internet. The standard also includes
WPA2 security and features to control access within corporate
networks.[9] Wi-Fi Direct-certified devices can connect one-to-one or
one-to-many and not all connected products need to be Wi-Fi
Direct-certified. One Wi-Fi Direct enabled device can connect to
legacy Wi-Fi certified devices.
The Wi-Fi Direct certification program is developed and administered
by the Wi-Fi Alliance, the industry group that owns the "Wi-Fi"
trademark. The specification is available for purchase from the Wi-Fi
Alliance.[13]
I was exploring regarding Wi-Fi Direct and came accross with conclusion that WiFi -certified devices can connect one-to-one or one-to-many and not all connected products need to be Wi-Fi Direct-certified. One Wi-Fi Direct enabled device can connect to legacy Wi-Fi certified devices.So by this we can conclude like if one device is having WiFi direct and other device is having Wifi one can easily connect to it.
I have following queries please help me to resolve.
1.This Wifi Direct is there in Android ICS onwards.So i am trying to connect WiFi Direct of my Samsung Note 2 having Jelly Bean with another Samsung Mobile Galaxy Y duos having Ginger Bread that only has WiFi but i am unable to detect? Can anyone help me in finding reason for this?
2.Another thing i studied is Wifi Direct device will become as access point means it will create an Ad-hoc network ? So why another Wifi devices are not detecting it?
To find a wifi direct device in access point list of a normal wifi u need to create a wifi direct group. For this you need to first connect two wifi direct devices out of which one will act as a group owner and other as client. Once a group is created group owner act as a normal access point for legacy devices(Wifi devices).
Thus you need to create a Wifi Direct group first