3

Since all RPi use b8:27:eb as the first three octets of their MAC address, you can use arp from your Mac/Linux PC, but you'll need to refresh the arp cache first. Here's a bash script that will do the job. You can get more details from my github page on the subject. #!/bin/sh : ${1?"Usage: $0 ip subnet to scan. eg '192.168.1.'"} subnet=$1 for addr in `...


2

First of all: very good explained question. But it is a sophisticated setup. And just to answer your question: yes, it is needed to setup special static routes on several devices. But it is very difficult to give advices remotely. I would need access to the network to try setup and look how it works step by step, the usual way to do the work of a network ...


2

arp -a prints a cached list of hosts/devices that have been talking to this host. Therefore if you see your smart plug and other devices appearing in the output, it's proof they were talking to this host since the last reboot of the Pi or restart of its' networking. In a nutshell: Your nmap is doing OUTWARD scanning of the specified subnet from the Pi ...


1

Ping Failures: Without any granular details about IP addressing & firewalling- you've not given much detail- I'd suspect that ICMP is being blocked somewhere in either a host firewall or the AP FW connecting the Pi & laptop. Interpreting Arp Cache Output: A quick discussion on interpreting arp cache results when investigating connectivity issues ...


1

The problem seems to be a firewall on the server. Your tcpdump shows a response that claims to come from 10.0.155.157, the address of your server. 07:32:25.397201 IP raspberrypi.47684 > 10.0.155.157.mdns: Flags [S], seq 174219133, win 29200, options [mss 1460,sackOK,TS val 1905316196 ecr 0,nop,wscale 7], length 0 07:32:25.397773 IP 10.0.155.157 > ...


1

It is a bit confusing for me why a ssh connection to the same ip address 10.0.155.157 on port 22 works and it also should work on port 5353. Usually the ssh daemon (server) listens only on one port. That is by default port 22. So for my understanding the server is listening on this port and not on port 5353. I haven't seen before a ssh daemon listening on ...


1

Seems there are to many components that have to play together: dhcpcd, ifupdown, hostapd and maybe dnsmasq and bridge-utils. I have a suggestion to reduce complexity with using systemd-networkd. It is available by default on Raspbian and has everything built-in, no need to install any additional helpers. Here is a setup with a bridge that I have tested for ...


1

1) Your service is terminated (all process started by this service are killed) when your last script (python here) execution is finished. Execute the python script into a terminal, your script exit with default value of 0 (process exit success code) after python file execution because you have not a forever loop (while). Service file is principaly for ...


1

After modifying wpa_supplicant.conf you need to make wpa_supplicant re-read the configuration file. wpa_cli -i wlan0 reconfigure (assuming wlan0 is your wifi to reconfigure) reference - wpa_cli man page


1

RFC 1918 ("local") addresses such as 192.168.1.x are non-routable across the Internet, so you'd need to configure a destination NAT ("DNAT") in the router in front of your Pi to forward traffic to it. How this is achieved depends on how your router's web or CLI interface is organized. However, the operation is the same: A) Set your DNS Record to point to ...


1

the ev3dev build is from before the 3B plus was released The Pi3B+ has new networking hardware and requires new firmware, so is unlikely to work with an old OS. If this is based on Raspbian, you could try updating on an older model Pi or you could try downloading firmware from http://archive.raspberrypi.org/debian/pool/main/r/raspberrypi-firmware/ or https:...


1

I am assuming that you are using Raspbian on the PI. If you want to write the files from a Gnu/Linux machine, then it is easy. From other OS you have a few choices. Option 1 Look up how to write to ext file-system from your OS. Option 2 Install Virtual-box (this may work with other virtualisation programs, don't try to run more than one at a time, as ...


1

You wrote in a comment: "I want to share the Pi's internet connection with the PC". At the answer to the question you have linked I find: "5. Now your Pi will obtain an IP address from your PC and can access internet through your PC". This is not what you want, you are using the wrong setup. Because you use a Raspberry Pi 3B I assume you are connected to a ...


1

Default config for a Pi is DHCP addressing. The router (or switch) assigning the IP to your Pi will assign one from a pool of addresses with an express lease time set for the IP address it assigned (mapped) to the mac address of your WLAN0 interface. Think of this IP as "loaned" to you: it's not yours in perpetuity and the address can be chucked back into ...


Only top voted, non community-wiki answers of a minimum length are eligible