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.
Related
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
I try to see the network trafic of my mobile device in my home wlan network.when I opened wireshark, listening on the WLAN Adapter and entered http.request.method == "GET"` to the wireshark filter.
All I can see is the requests from my laptop and not of my mobile device.
If I enter ip.addre == 10.0.0.30 i can see the protocolls BJNP, ICMP, IGMPv2 and so on.
What is the reason for this behavior?
In my opinion, if I can see a TCP IP Protocol, it should be also possible to see a HTTP request.
There are two things that need to happen in order for you to be able to sniff TCP traffic from another device.
Your device needs to receive the traffic you want to analyze, and
Your device must be configured in "promiscuous mode".
If promiscuous mode is disabled (which is the default), packets not intended for your laptop will never make it to Wireshark. They will instead be filtered out by your network adapter.
There are cases where this is not enough, for example, if you connect to a network with a layer 2 switch.
The first thing you need to ensure is that your network adapter is set to monitor or promiscuous mode, otherwise you just won't be able to see packets not meant for your NIC. Also, set your computer as an access point, and connect your phone to said access point.
If you're going to sniff HTTPS traffic don't forget to add your own certificate to the phone.
I want to use wireshark to check which network users is using Port 59666 for downloads. Is it possible to use wireshark? and how would I begin to do this?
It may be possible to do this with wireshark, but it may require you to adjust your network topology to achieve this.
Firstly you need to decide where to run wireshark.
Wireshark can only tell you about network packets that it can see. To assist, wireshark can put the network card into promiscuous mode, but if the network card is connected to a switch, the switch will not send other network packets to you - so wireshark cannot report on them.
If your users are connected using wifi, then you can run wireshark on a wifi addapter and inspect all wifi network packets from all users on that wifi network. You may also install wireshark on a computer operating as the router / firewall, and inspect all the packets there.
The final option depends on your switch hardware. On managed switches it is usually possible to duplicate all network traffic to an additional port. That would allow you to connect your computer to this port, and then run wireshark on this network connection.
When you are receiving the wireshark trace, set up a filter for the ports you are interested in, and wait for your users to send packets. Inspect the packets, and you will see the source IP address. You now need to translate this IP address to a physical computer (DNS / DHCP servers may help with this).
Depending on your computer environment, tracking it down to a single computer may not identify an individual responsible. Someone could have left a torrent running in the background and someone else could have logged onto and used the machine.
I'm building an application that will run in a museum with a local area wifi network without internet access, for some strange reason I'm not able to fully "join" this network with an iOS device. Enabling internet access on this network solves the problem...
The network should provide only a web server and a DNS server, the access point has a DHCP server, android devices can connect to the network without problems.
When I try to join the network with the device it remains in a "spinning wheel" status, the DHCP server log on the debian server says it has assigned an address to the iOS device, and if I check for the wifi address with an application (like iSys o SBSettings) I see the WIFI DHCP assigned address.
But when my app (or safari) tries to connect to the web server the request is routed through the 3G connection and not completed.
In my app I'm using the standard "Reachability" framework from Apple to check the reachability of a provided host name through the wifi connection and I get 0 on the SCNetworkReachabilityFlags mask....
I'm quite sure the problem is due to the fact iOS (5.1 in my case) tries to check the reachability for some "standard" host in the network, before routing traffic through the WIFI connection.
Anyone knows what an iOS device do to "validate" a WIFI network? I can add hostnames or simple dummy services to the server machine if this can help me connect the device to a LOCAL-only network :)
It seems that iOS doesn't like to join networks without a gateway, also if the network is local you have to setup a correct gateway address.
Setting the gateway as the server itself did the trick and the device started to route TCP/IP over my local area wifi network.
I am trying to create a RAS server in XP Pro. The idea is to log in to this server via a dialup connection. I have set up a new network connection via the New Connect Wizard in XP - according to this tutorial on techrepublic.
I am sure that the modem and the connection is working, I have tested it.
However, I want to monitor incoming network traffic on this connection. So I thought I would use Wireshark. The problem is that Wireshark does not list this incoming connection on the front page. It lists all my other network connections, ( e.g. my ethernet connection ) but not this one.
Whats the best way to monitor traffic on this connection?
Wireshark should be able to capture the traffic on your connection. I would check the protocol you're using for communication and make sure that Wireshark is monitoring those protocols. Also, I would make sure that Wireshark is actually capturing traffic on your dial up device. It sounds like it's currently monitoring your NIC card, not your modem.
I recently found Microsoft Network Monitor and it has ability to sniff on dialup adapter with Vista or Win7 as OS. Works great!
According to this Wireshark wiki page, you must use Winpcp 3.1 to be able to capture traffic on dial up modems.