Re: Fing Network Tools 8.7.0 APK [Pro] [Mod] [SAP] [Full]
Edelira Longinotti
Fing - Network Tools is an app that can inform you of all the devices connected to a certain WiFi network. This is incredibly useful if you want to keep a close eye on your connection status, while also checking to make sure no one is accessing your network without your permission.
One great thing about Fing - Network Tools is that its interface is simple, so you can easily discover all the possibilities it has to offer. In fact, it gives you all the tools you need to help you analyze the speed of your WiFi connection and identify the server you're connecting from.
Fing - Network Tools also shows you the IP address and data related to the connection made by each device. These parameters are important if you want to keep track of all the devices connected to your network.
If you use Fing - Network Tools, it'll be easy to detect any hackers or intruders who may be accessing your device. All you need to do is complete a network analysis, and you'll easily detect each device connected to the internet through your router.
Yes, Fing - Network Tools needs some special permissions to gain the necessary information concerning your device and the Wi-Fi network it is connected to. These basic permissions enable it to function normally.
Fing - Network Tools does not require any previous configuration. All you have to do is download the APK and install the app on your phone. When you open it, it will automatically start scanning all the devices connected to your network.
version 2.15 works better for my android and is easy, the last version present some layout problems and tools are more hidden. Ok my english is not good. I updated from version 2.15 to 6.5 and it has ...
Hi I use the fing app on android and was wondering how accurate the port scan tool is on apps like this. Is it as good as websites like yougetsignal.com when checking your ip for open ports? Thanks.
The main goal of this tool is to browse for everything connected on the same WiFi network, and display some informations such as MAC addresses, IP addresses, names of devices, brand/model/manufacturer (if available). It is really powerful even in its free version and I would really like to know how it works.
So I have continued my investigations, and I got the idea of sniffing what is coming from this application.I have set up a TCPDump listener on the Mac, and launch the app again. So I have sniffed everything going from the app to my laptop. And here is what I obtained :
Fing Desktop is a program for Windows that makes it possible to track many aspects related to the devices connected to your wifi network. Through a relatively simple interface, at all times, you can use features similar to those of the smartphone version of the app.
All of these features can be found on a menu on the left side of the screen. Specifically, with Fing Desktop, you can track any issue in your network. All the connected devices will appear in real-time, as well as their brand, IP address, or last time they were connected.
On top of all that, Fing Desktop also includes a forum where you can post questions and check for internet outages on a world map. Take control of your WiFi network with this great program for Windows.
Fing seems like a pretty cool tool - finding devices on the network and their associated MAC address. One could easily implement any of the solutions that provides detection and alerting, but I would like to know how these tools are implemented? Is this a combination of low level linux utilities, or is there some custom programming going on?
I just ran Fing against my wireless network. Using tcpdump, it appears that Fing generates Address Resolution Protocol (ARP) request packets. ARP is a pretty simple protocol that runs at the Ethernet Protocol level (Data Link, OSI level 2). An ARP request packet has the broadcast address (ff:ff:ff:ff:ff:ff) as the "to" address, the Android phone's MAC and IP address as the "from" information, and an IP address that Fing wants to know about. It appears that Fing just marches through whatever subnet it's on, in my case 172.31.0.0/24, so 255 IP addresses, from 172.31.0.1 to 172.31.0.254. After the march, it appears to try IP addresses that haven't responded a second time. This looks to me like Fing tries IP addresses in batches, and relies on the underlying Linux kernel to buffer ARP replies, for a Fing thread to deal with as fast as it can. If Fing decides that there's a timeout, it resends. It's not clear to me how Fing (a Java program) gets the phone's Linux kernel to generate ARP packets.
Fing is a special tool that allows users to see at a glance all of the devices that are connected to their network. Not only is this tool available free of charge it works very quickly and users are not plagued with adverts which is rare for a tool of this kind.
Fing scans the local area to provide information on all of the devices in the area that are connected. This could be extremely useful for anyone who has been finding that their connection is running more slowly than usual. The app can be started and shut down in seconds making it very fast and effective to use at any time. Although most people are able to get the same type of information from their router in theory in practice the information can be rather tricky to find whereas Fing is designed to provide the information at a single glance. However the app is rather limited in its scope and many useful tools that could accompany it are absent.
I was running Fing on my iPhone. My Macbook Pro is on the same wireless network and I noticed that Fing not only detected my laptop's name (this is understandable, it is broadcasted, I can see it on the router too), but it also detected the model generation (say Macbook Pro 13 in, 2017-2018) and the MacOS version (MacOS 10.15 Catalina). How is it able to determine the exact model and the exact OS version and is it possible to prevent broadcasting this info?
How does fing or nmap fingerprint a machine? Usually a database of known claimed hardware manufacturers, looking at open ports and even issuing handshakes to the machine in question to pick apart minute differences in timing and implementation of TCP/IP transactions. It's a lot of reverse engineering and collaboration that lets these tools "identify" gear as the manufacturers generally don't want advertise "I'm a Mac" now that security and cracking are legitimate threats on home networks since routers and software have so many holes in them and it's hard for people to choose strong unique passwords and secure their "smart" devices. Once one is compromised, your whole network is open to "fing scans".
There's lots of tools (mostly professional) that will do a "network inventory" of not only what's connected to your network (type of device), but name, OS, installed software, etc. Network Inventory Advisor is an example of such software (this one is Windows based, but it's product info pages give good examples of what info can be obtained).
The OUI alone can give you a clue as to what computer's identity - there are many free tools on the internet like Wireshark's OUI Lookup Tool. Try it for yourself, paste your MAC address (obtained from ifconfig and see what vendor is identified. You can obtain all of the MAC addresses on your network segment by pinging your broadcast address.
These are just some of the services on your client machines that advertise what resources are available. All Fing is doing is utilizing one or more of these (which one they use specifically, I don't know) to do an inventory of the network.
When you attempt to prevent this, you are going to find it difficult to strike a balance between user convenience and perceived security. These identifiers are shared so that the end user doesn't have to go back to the 1970s and 80s and manually configure services (i.e. printing or network file sharing). For example, turn off a zero-conf service and you have to manually configure your printer on your client. You also have to manually configure your printer to not use DHCP because if that IP changes for whatever reason, you have to reconfigure that service again.
In the book The Art of Deception, the author, Kevin Mitnik (convicted hacker) describes many ways systems are compromised. There are many tools and steps you can take technologically and yes, you should implement them. But knowing what OS you're using is irrelevant when the weakest link can be found between the keyboard the chair. You can turn all of this off tomorrow and with very little effort, can get all this information via social engineering; in other words, just talking to the user.
aa06259810