home network unstable and arpscan kills connection

asked 2024-06-01 10:53:16 +0000

pioupus gravatar image

updated 2024-06-01 11:12:44 +0000

Hi, I am helping a friend setting up an ip cam for searching for meteors. Unfortunately it seems something is wrong in the network.

There is a raspberrypi(192.168.2.115) which captures constantly the ip cam's(192.168.2.139) video stream at night. We observed the first problems because its framerate is not constant. Now I try to log into the raspberrypi via anydesk and even this seems to be problematic. Often the connection is sufficiently quick but it happens as well that it gets barely unusable due lagging.

And even more interesting: If I perform from the raspberry:

sudo arp-scan --destaddr=aa:42:a1:0e:08:1c --localnet

sudo: unable to resolve host gmnraspi: Name or service not known
Interface: eth0, type: EN10MB, MAC: d8:3a:dd:8b:2e:21, IPv4: 192.168.2.115
Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan)
192.168.2.1 aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.100   ac:15:a2:e1:3b:8b   (Unknown)
192.168.2.113   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.115   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.100   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.101   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.114   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.115   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.110   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.115   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 3)
192.168.2.117   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.139   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.254   aa:42:a1:0e:08:1c   (Unknown: locally administered)
192.168.2.101   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.110   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.114   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.117   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.139   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)
192.168.2.139   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 3)
192.168.2.254   aa:42:a1:0e:08:1c   (Unknown: locally administered) (DUP: 2)

24 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.7: 256 hosts scanned in 2.212 seconds (115.73 hosts/sec). 20 responded

The anydesk connection breaks and I have to wait a couple of minutes/hours to have access again. The prompt is still open so the raspberrypi did not reboot in the meantime. It was just invisible to the network.

I have ... (more)

edit retag flag offensive close merge delete

Comments

You have some hosts that do not seem to behave very nicely with arp - it indicates you have duplicate IP:

Frame 721: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on interface any, id 0
Linux cooked capture v1
Address Resolution Protocol (request/gratuitous ARP)
[Duplicate IP address detected for 192.168.2.115 (aa:42:a1:0e:08:1c) - also in use by d8:3a:dd:8b:2e:21 (frame 720)]

Don't know why 08:1c is is issuing a grat arp for for your rpi device. Proxy arp? Really no idea, but this is probably why you lose connectivity for a while after running the arp-scan tool - you have to wait until arp cache timeout occurs for the network to stabilize.

Bob Jones gravatar imageBob Jones ( 2024-06-02 14:28:54 +0000 )edit
add a comment