fing?

[ToddAndMargo]

Hi All,

The Fing App

https://apps.apple.com/us/app/fing-network-scanner/id430921107

works really nicely on an iPad.  We got anything like that?

Many thanks,
-T

[Patrick O'Callaghan]

On Sun, 2019-09-01 at 20:13 -0700, ToddAndMargo via users wrote:
> Hi All,
>
> The Fing App
>  https://apps.apple.com/us/app/fing-network-scanner/id430921107
>
> works really nicely on an iPad.  We got anything like that?

I use it on Android, but what specifically do you want? Fing packages a
number of common tools under one interface, but IIRC all those tools
exist in Linux already.

poc

[ToddAndMargo]

On 9/2/19 2:24 AM, Patrick O'Callaghan wrote:
> On Sun, 2019-09-01 at 20:13 -0700, ToddAndMargo via users wrote:
> > Hi All,
> >
> > The Fing App
> >   https://apps.apple.com/us/app/fing-network-scanner/id430921107
> >
> > works really nicely on an iPad.  We got anything like that?
>
> I use it on Android, but what specifically do you want? Fing packages a
> number of common tools under one interface, but IIRC all those tools
> exist in Linux already.
>
> poc

Hi Poc,

Scan an Ethernet and tell me all the devices it
finds including those on different networks, but
on the same cable.

I have customer that often place two routers on the
cable Ethernet and get two different networks.  For
example

10.0.0.0/24
      192.168.1.0/24

And all heck breaks loose.

I use to use AutoScan for this, but it is unsupported
and stopped working as of Fedora 24

-T

[Alexander Dalloz]

Am 2019-09-02 13:14, schrieb ToddAndMargo via users:
> On 9/2/19 2:24 AM, Patrick O'Callaghan wrote:
> > On Sun, 2019-09-01 at 20:13 -0700, ToddAndMargo via users wrote:
> > > Hi All,
> > >
> > > The Fing App
> > >   https://apps.apple.com/us/app/fing-network-scanner/id430921107
> > >
> > > works really nicely on an iPad.  We got anything like that?
> >
> > I use it on Android, but what specifically do you want? Fing packages 
> > a
> > number of common tools under one interface, but IIRC all those tools
> > exist in Linux already.
> >
> > poc
>
> Hi Poc,
>
> Scan an Ethernet and tell me all the devices it
> finds including those on different networks, but
> on the same cable.
>
> I have customer that often place two routers on the
> cable Ethernet and get two different networks.  For
> example
>  10.0.0.0/24
>  192.168.1.0/24
>
> And all heck breaks loose.

Can we assume that you mean more than 1 DHCP server?
> I use to use AutoScan for this, but it is unsupported
> and stopped working as of Fedora 24
>
> -T

arpwatch (IPv4 only)
addrwatch (both IPv4 and IPv6)

[Ed Greshko]

On 9/2/19 7:14 PM, ToddAndMargo via users wrote:
> Scan an Ethernet and tell me all the devices it
> finds including those on different networks, but
> on the same cable.
>
> I have customer that often place two routers on the
> cable Ethernet and get two different networks.  For
> example
>
> 10.0.0.0/24
>      192.168.1.0/24
>
> And all heck breaks loose.
>
> I use to use AutoScan for this, but it is unsupported
> and stopped working as of Fedora 24

nmap -sn 192.168.1.0/24      for example

I don't know, and I leave it up to you, to determine if you can scan a network for which your adapter doesn't have a matching IP address.  You may have to assign a 10.0.0.X address.

Oh, and fire your customer.  :-) :-)

[Earl Ramirez]

> nmap -sn 192.168.1.0/24      for example
>
> I don't know, and I leave it up to you, to determine if you can scan
> a network for which your adapter doesn't have a matching IP address. 
> You may have to assign a 10.0.0.X address.

Netdiscover will scan the entire RFC 1918 regardless of the
configuration of your NIC.

[Ed Greshko]

On 9/2/19 8:23 PM, Earl Ramirez wrote:
> > nmap -sn 192.168.1.0/24      for example
> >
> > I don't know, and I leave it up to you, to determine if you can scan
> > a network for which your adapter doesn't have a matching IP address. 
> > You may have to assign a 10.0.0.X address.
>
> Netdiscover will scan the entire RFC 1918 regardless of the
> configuration of your NIC.

[root@meimei ~]# dnf whatprovides netdiscover
Last metadata expiration check: 1:30:03 ago on Mon 02 Sep 2019 07:03:55 PM CST.
Error: No Matches found

Can we assume you get this from a 3rd party repo?

[Earl Ramirez]

> [root@meimei ~]# dnf whatprovides netdiscover
> Last metadata expiration check: 1:30:03 ago on Mon 02 Sep 2019
> 07:03:55 PM CST.
> Error: No Matches found
>
> Can we assume you get this from a 3rd party repo?

To be honest, I have been using it in Kali, I saw there is a RHEL spec
file. This will be a good weekend project to have it available in copr,
hopefully in Fedora official repos.

[Tom H]

On Mon, Sep 2, 2019 at 2:36 PM Ed Greshko  wrote:
> On 9/2/19 8:23 PM, Earl Ramirez wrote:
> > > nmap -sn 192.168.1.0/24      for example
> > >
> > > I don't know, and I leave it up to you, to determine if you can scan
> > > a network for which your adapter doesn't have a matching IP address.
> > > You may have to assign a 10.0.0.X address.
> >
> > Netdiscover will scan the entire RFC 1918 regardless of the
> > configuration of your NIC.
>
> [root@meimei ~]# dnf whatprovides netdiscover
> Last metadata expiration check: 1:30:03 ago on Mon 02 Sep 2019 07:03:55 PM CST.
> Error: No Matches found
>
> Can we assume you get this from a 3rd party repo?

From some googling:
https://github.com/netdiscover-scanner/netdiscover
https://repology.org/project/netdiscover/versions
https://bugzilla.redhat.com/show_bug.cgi?id=499951
https://copr.fedorainfracloud.org/coprs/lostmemories/Netdiscover/packages/

[Earl Ramirez]

> From some googling:
> https://github.com/netdiscover-scanner/netdiscover
> https://repology.org/project/netdiscover/versions
> https://bugzilla.redhat.com/show_bug.cgi?id=499951
> https://copr.fedorainfracloud.org/coprs/lostmemories/Netdiscover/packages/

Great, I will continue where it was left off.

[ToddAndMargo]

On 9/2/19 4:42 AM, Alexander Dalloz wrote:
> Can we assume that you mean more than 1 DHCP server?

Yes
> arpwatch (IPv4 only)
> addrwatch (both IPv4 and IPv6)

This also occurs when they use a router as a second
access point instead of an Access Point only because
a single function access point is more expensive.

My network rule: one router ONLY.  Don't expect
a router to stay acting as an access point only, regardless
of what you configure it as.  One power hit and/or
one telephone tech support telling the customer
to press the reset button can cause havoc.

[ToddAndMargo]

On 9/2/19 10:10 AM, Earl Ramirez wrote:
> > From some googling:
> > https://github.com/netdiscover-scanner/netdiscover
> > https://repology.org/project/netdiscover/versions
> > https://bugzilla.redhat.com/show_bug.cgi?id=499951
> > https://copr.fedorainfracloud.org/coprs/lostmemories/Netdiscover/packages/
>
> Great, I will continue where it was left off.

Any good new to report?

[Earl Ramirez]

> Any good new to report?

The package was built and tested but need to go thorough the process of
getting it into Fedora official repository.

[ToddAndMargo]

On 9/2/19 9:25 PM, Earl Ramirez wrote:
> > Any good new to report?
>
> The package was built and tested but need to go thorough the process of
> getting it into Fedora official repository.

Any chance of a sneak peek?

[Earl Ramirez]

On Mon, 2019-09-02 at 23:50 -0700, ToddAndMargo via users wrote:
> On 9/2/19 9:25 PM, Earl Ramirez wrote:
> > > Any good new to report?
> >
> > The package was built and tested but need to go thorough the
> > process of
> > getting it into Fedora official repository.
>
> Any chance of a sneak peek?

You can find the packages at https://trinipino.org/fedora_packages/

[ToddAndMargo]

On 9/3/19 5:36 PM, Earl Ramirez wrote:
> On Mon, 2019-09-02 at 23:50 -0700, ToddAndMargo via users wrote:
> > On 9/2/19 9:25 PM, Earl Ramirez wrote:
> > > > Any good new to report?
> > >
> > > The package was built and tested but need to go thorough the
> > > process of
> > > getting it into Fedora official repository.
> >
> > Any chance of a sneak peek?
>
> You can find the packages at https://trinipino.org/fedora_packages/

Looks like it scans everything on 192.168.x.x., 172.16.x.x,
172.26.x.x and so on.

This is useful, but misses a lot of mistakes and takes forever. 
Autoscan can find everything is less than 15 seconds.  Rats!

I have just been using arp-scan

[ToddAndMargo]

On 9/3/19 6:53 PM, ToddAndMargo via users wrote:
> On 9/3/19 5:36 PM, Earl Ramirez wrote:
> > On Mon, 2019-09-02 at 23:50 -0700, ToddAndMargo via users wrote:
> > > On 9/2/19 9:25 PM, Earl Ramirez wrote:
> > > > > Any good new to report?
> > > >
> > > > The package was built and tested but need to go thorough the
> > > > process of
> > > > getting it into Fedora official repository.
> > >
> > > Any chance of a sneak peek?
> >
> > You can find the packages at https://trinipino.org/fedora_packages/
>
> Looks like it scans everything on 192.168.x.x., 172.16.x.x,
> 172.26.x.x and so on.
>
> This is useful, but misses a lot of mistakes and takes forever. Autoscan 
> can find everything is less than 15 seconds.  Rats!
>
> I have just been using arp-scan

And how many hours later, it is still going.  That
pretty much means it is useless unless you want to
let it run over the weekend.  Rats!!!!

Sure we don't have a fing out there?

I suppose when I have time, I really need to fire up
AutoScan on Fedora 23 and watch what it is doing on
Wireshark.

Any way to get AutoScan to work on Fedora 30?

[ToddAndMargo]

On 9/1/19 8:13 PM, ToddAndMargo via users wrote:
> Hi All,
>
> The Fing App
>
> https://apps.apple.com/us/app/fing-network-scanner/id430921107
>
> works really nicely on an iPad.  We got anything like that?
>
> Many thanks,
> -T

Follow up.

Could not find fing for Fedora.  Netmanager is excruciatingly slow,
so as to be unusable

B-U-T !!!! On a lark, I retried AutoScan AND IT IS WORKING AGAIN!
YIPPEE !!!!!!

Quick AutoScan Installation

$ wget 
http://jaist.dl.sourceforge.net/sourceforge/autoscan/AutoScan-Network-Linux-...
     $ tar -zxvf AutoScan-Network-Linux-1.12.bin.tar.gz
     # ./AutoScan-Network-1.12.bin

to run:
    # /opt/AutoScan/bin/autoscan-network

Make sure you run it as root. It doesn't gripe but can
find anything as a user.

[Earl Ramirez]

> > > You can find the packages at 
> > > https://trinipino.org/fedora_packages/
> >
> > Looks like it scans everything on 192.168.x.x., 172.16.x.x,
> > 172.26.x.x and so on.

Yes, it scan all networks in RFC 1918
> > This is useful, but misses a lot of mistakes and takes forever.

Can you give a few examples, I have been using this for years and
haven't seen any 'mistakes' I primarily used it when I am at a customer
and there is zero documentation. I also use bettercap.
> And how many hours later, it is still going.  That
> pretty much means it is useless unless you want to
> let it run over the weekend.  Rats!!!!

I haven't experience this delays neither, did you use any options or
just run netdiscover?
> Sure we don't have a fing out there?

My Google Fu did point me to any source code, if you know of any let us
know.
> I suppose when I have time, I really need to fire up
> AutoScan on Fedora 23 and watch what it is doing on
> Wireshark.
>
> Any way to get AutoScan to work on Fedora 30?

If it was on Fedora 23, I don't see why it will be a problem to have it
available on Fedora 30.

[ToddAndMargo]

On 9/5/19 6:41 PM, Earl Ramirez wrote:
> > > > You can find the packages at
> > > > https://trinipino.org/fedora_packages/
> > >
> > > Looks like it scans everything on 192.168.x.x., 172.16.x.x,
> > > 172.26.x.x and so on.
>
> Yes, it scan all networks in RFC 1918

Indeed!

Two Ethernet cards.  One for my Lan and one external (Internet
facing).  Both are run through iptables.  Two bridges: one for
my qemu-kvm virtual machines to talk to the Internet and such
and one for Open VPN to interface my VMs with the VPN port.
> > > This is useful, but misses a lot of mistakes and takes forever.
>
> Can you give a few examples, I have been using this for years and
> haven't seen any 'mistakes' I primarily used it when I am at a customer
> and there is zero documentation. I also use bettercap.
> > And how many hours later, it is still going.  That
> > pretty much means it is useless unless you want to
> > let it run over the weekend.  Rats!!!!
>
> I haven't experience this delays neither, did you use any options or
> just run netdiscover?

No options
> > Sure we don't have a fing out there?
>
> My Google Fu did point me to any source code, if you know of any let us
> know.
> > I suppose when I have time, I really need to fire up
> > AutoScan on Fedora 23 and watch what it is doing on
> > Wireshark.
> >
> > Any way to get AutoScan to work on Fedora 30?
>
> If it was on Fedora 23, I don't see why it will be a problem to have it
> available on Fedora 30.

Autoscan died between FC24 to FC29, but it is alive with with FC30.
YIPPEE!!!  I have also noticed that since I downloaded a fresh
copy that some feature are added, but the revision did not change.  Or
perhaps these features would not show for some other reason.

Netdiscover is to without its uses.  It just takes FOREVER.
Netdiscover is running inquires/probes against IP addresses.

I am not sure what Autoscan is doing, but it is not probing
all RFC 1918 IP address, which is probably why it did in 5
minutes what it took Netdiscover over five hours to do
on my little network.

And something else Autoscan does that Netdiscover does not, if
I fire up another VM, Autoscan catches it just at about the time
the VM finishes booting.  This without running a new scan.

And as far as Netdiscover goes, I see it as yet another
tool in my toolbox.  I have learned not to trust these
things to one tool.

And, I typically start out with arpscan, especially since
Windows has one too.

Oh and ESET AntiVirus on Windows 10 got pissed at both
of them.  Chuckle.  But does not complain about arpscan.

Fing has a nice package on iPad, too bad it does to
run under Linux too.

Thank you for all the help and tips!

[Cameron Simpson]

On 03Sep2019 20:47, ToddAndMargo  wrote:
> > > You can find the packages at https://trinipino.org/fedora_packages/
> >
> > Looks like it scans everything on 192.168.x.x., 172.16.x.x,
> > 172.26.x.x and so on.
> >
> > This is useful, but misses a lot of mistakes and takes forever. 
> > Autoscan can find everything is less than 15 seconds.  Rats!
> >
> > I have just been using arp-scan
>
> And how many hours later, it is still going.  That
> pretty much means it is useless unless you want to
> let it run over the weekend.  Rats!!!!

C'mon people. Broadcast ping:

ping -b 255.255.255.255

Watch and enjoy.

Cheers,
Cameron Simpson

[ToddAndMargo]

On 9/6/19 7:52 PM, Cameron Simpson wrote:
> On 03Sep2019 20:47, ToddAndMargo  wrote:
> > > > You can find the packages at https://trinipino.org/fedora_packages/
> > >
> > > Looks like it scans everything on 192.168.x.x., 172.16.x.x,
> > > 172.26.x.x and so on.
> > >
> > > This is useful, but misses a lot of mistakes and takes forever. 
> > > Autoscan can find everything is less than 15 seconds.  Rats!
> > >
> > > I have just been using arp-scan
> >
> > And how many hours later, it is still going.  That
> > pretty much means it is useless unless you want to
> > let it run over the weekend.  Rats!!!!
>
> C'mon people. Broadcast ping:
>
> ping -b 255.255.255.255
>
> Watch and enjoy.
>
> Cheers,
> Cameron Simpson

Ha!  In an idea world.

I use this all the time.  Only Apple devices respond.
I have
     # ping -b 255.255.255.255
going right now and it is being ignored.

The fastest way I have found to get a quick answer is

# arp-scan  --localnet
Interface: eno2, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.9.5 with 256 hosts 
(https://github.com/royhills/arp-scan)

192.168.250.1	xxxxxxxxxxxxxxxx	NETGEAR
192.168.250.127	xxxxxxxxxxxxxxxx	Roku, Inc.
192.168.250.128	xxxxxxxxxxxxxxxx	Roku, Inc.

3 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.5: 256 hosts scanned in 1.886 seconds (135.74 
hosts/sec). 3 responded