r/Fing_App

Every time I launch the IOS Fing app (current version), I have to clear a banner regarding upgrading to Pro. It is really annoying, especially when I get a "down" alert and open Fing to see what is going on. As a paid Premium subscriber, I would think that I shouldn't have to deal with these kinds of ads. I would be a different matter if I was using the free version, but I'm paying for this. Developers should remove these banners from showing up on paid user accounts.

I've looked all around and cannot find any way to display the version number. Most programs I have seen in the past might have it near the bottom center somewhere. This would be of course most helpful in reporting bugs and asking for help or support. Any way we can get this added?

I was surprised to find that I cannot adjust the page length or number of rows displayed per page.

Ten devices per page is basic. The ability to be able to show 100, 50, 25 or whatever would be a nice addition.

I've used Fing forever. It served me well for a long time. Unfortunately, with the latest release and a support ticket response that... I'll leave it there.

The previous version of the app had effectively and accurately monitored 127 IP devices on my home network. The database contained a rich catalogue of extra data that had been added over several years. All the little fiddly pieces of data like warranty end dates, HA access codes, etc. It didn't need me to troubleshoot it often; when it did, it was quick.

The new version...

1. Fing app upgraded and doesn't recognize the network it has managed forever. Monitoring remains offline.
2. Fing support ticket response was "Delete previous instances and it will allow you to monitor two networks... ticket closed." No consideration for the fact the device data would all be erased, and no warning.
3. The interface requires scrolling within the device list if you have all columns active. This window is fixed, so even with the app maximized, scrolling is required.
4. Data is incorrect in an alarming number of fields.
5. The "Upgrade to Pro" advertisement is annoying.

Effort outweighs reward, so...

/end

The latest update keeps failing and app hangs, chewing up resources. So, I’ve been trying to uninstall it. Going to Settings>Apps, it doesn’t show up in the list. Going to Start menu, and right clicking on Fing, it shows the Uninstall option, but it does nothing. Going to Task Manager, and killing all the Fing entries, some pop right back in. When I reboot, Fing tries to install all over again, hangs, and I have to start all over again.

How do I KILL this thing?!?!?

I wanted one Fing Agent to monitor devices across multiple VLANs/subnets so Fing would treat them as one monitored network.

My main reason was presence detection. I wanted Fing's **Everyone left** trigger to work for people whose devices are on different VLANs, without running multiple Fing Agents or trying to synchronize state in IFTTT.

My phone is one VLAN 1, my wifes is VLAN 14. Fings's IFTTT requires everyone to be on 1 subnet for 'everyone left' trigger.

This is unsupported/experimental, but it's working for me.

## How it works

The Linux host has access to each VLAN:

eth0

eth0.14

eth0.21

eth0.24

eth0.42

eth0.66

eth0.69

A network namespace, macvlan interfaces and nftables make those separate networks appear to Fing as one synthetic `/21`.

My mapping is:

Fing sees Real subnet

192.168.1.x -> 192.168.1.x

192.168.0.x -> 192.168.14.x

192.168.2.x -> 192.168.21.x

192.168.3.x -> 192.168.24.x

192.168.4.x -> 192.168.42.x

192.168.5.x -> 192.168.66.x

192.168.6.x -> 192.168.69.x

For example, a device actually at:

192.168.42.188

appears to Fing as:

192.168.4.188

The device's real MAC address is preserved, so Fing can still identify and use the device for presence detection.

## Files

The scripts/configuration are here:

https://github.com/p1r473/fing/

The repo contains:

fing-combo-netns

fing-combo-netns.service

combo.conf

Edit `fing-combo-netns` for your VLANs/interfaces before installing it.

The important mapping in the script is:

SYN=(0 2 3 4 5 6)

REAL=(14 21 24 42 66 69)

For mine that means synthetic `192.168.4.x`, for example, maps to real `192.168.42.x`.

## Install

Install Fing Agent:

sudo snap install fing-agent

sudo /snap/fing-agent/current/script/connect-fing-agent.sh

Copy the three files from the repo to:

fing-combo-netns -> /usr/local/sbin/fing-combo-netns

fing-combo-netns.service -> /etc/systemd/system/fing-combo-netns.service

combo.conf -> /etc/systemd/system/snap.fing-agent.fingagent.service.d/combo.conf

Then:

sudo chmod +x /usr/local/sbin/fing-combo-netns

sudo systemctl daemon-reload

sudo systemctl enable --now fing-combo-netns.service

sudo systemctl enable snap.fing-agent.fingagent.service

sudo systemctl restart snap.fing-agent.fingagent.service

That's it.

Fing now sees the synthetic network as:

192.168.0.0/21

I confirmed Fing is ARP scanning across the synthetic subnet and receiving translated replies from devices on the real VLANs.

## Why bother?

All of the devices can now exist under **one Fing monitoring unit**.

That means instead of trying to combine presence state from multiple Fing Agents in IFTTT, I can simply use:

Fing -> Everyone left -> automation

## Caveats

Fing displays the **synthetic IP**, not the device's real VLAN IP.

For example:

Fing: 192.168.4.188

Real: 192.168.42.188

The MAC address remains the real device MAC.

The script also uses `.251` for the Fing-side address and `.252` on the translated VLANs, so make sure those addresses aren't already in use.

This isn't an officially supported Fing configuration, but it's working well for me so far.