Pi.Alert icon indicating copy to clipboard operation
Pi.Alert copied to clipboard

arp-scan config not working !

Open ErfanDL opened this issue 4 years ago • 6 comments

Hi. today I update the Pi.Alert to version 3.0 and add the SCAN_SUBNETS = '10.5.50.0/24 10.5.51.0/24' parameter to pialert.conf, but the 10.5.50.0/24 devices doesn't show up in PiAlert web UI. what's wrong ?

thanks.

ErfanDL avatar Apr 22 '21 09:04 ErfanDL

Hi Can you execute this commands?

ifconfig

ip route

sudo arp-scan 10.5.50.0/24 10.5.51.0/24

pucherot avatar Apr 22 '21 20:04 pucherot

Thanks for reply. ip route:

default via 10.5.51.1 dev eth0 src 10.5.51.5 metric 202
10.5.51.0/24 dev eth0 proto dhcp scope link src 10.5.51.5 metric 202

arp-scan:

Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.9.5 with 512 hosts (https://github.com/royhills/arp-scan)
10.5.51.1              Routerboard.com
10.5.51.2              ASUSTek COMPUTER INC.
10.5.51.3              Routerboard.com

4 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.5: 512 hosts scanned in 5.474 seconds (93.53 hosts/sec). 3 responded

ErfanDL avatar Apr 23 '21 07:04 ErfanDL

10.5.50.0 segment is in the same interface eth0?

please, execute the command: ifconfig

pucherot avatar Apr 23 '21 12:04 pucherot

10.5.50.0 segment is in the same interface eth0?

please, execute the command: ifconfig

No it's not in the same interface eth0 it's routed by mikrotik router and I can ping the 10.5.50.0 subnet from 10.5.51.0 network.

here the ifconfig:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.5.51.5  netmask 255.255.255.0  broadcast 10.5.51.255
        inet6 fe80::fc7e:28a4:65ae:26c0  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:86:dc:6c  txqueuelen 1000  (Ethernet)
        RX packets 123109  bytes 26801684 (25.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 144045  bytes 19654929 (18.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 293666  bytes 20864852 (19.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 293666  bytes 20864852 (19.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:d3:89:39  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ErfanDL avatar Apr 23 '21 12:04 ErfanDL

Arp is Layer 2 only so is not routable meaning it will stay within the subnet.

You would need another interface within your 10.5.50.0 network to be able to use arp.

bignick8t3 avatar Apr 27 '21 08:04 bignick8t3

Arp is Layer 2 only so is not routable meaning it will stay within the subnet.

You would need another interface within your 10.5.50.0 network to be able to use arp.

OK thanks.

ErfanDL avatar Apr 27 '21 11:04 ErfanDL