4

I borrowed the RPI 3B from a friend's friend. hence I don't know the hostname so that I can ping the RPI to know its IP address. Raspberry Pi is a board without any internal storage hence it doesn't matter where you got this. You installed your own operating system (a downloaded image file) on the SD-Card and because of that, you have formated (remove any ...


2

As you mentioned, it's easy to do it on Windows OS, however, it's a bit different on Raspberry Pi and Linux. I have looked up guides but they all seem to mention using the pi as a DHCP server, not too sure what I want/need this. In your situation, the phone is a device that has an internet connection. Obviously, the devices/clients must connect to ...


2

Assuming you're using the hardware mentioned in the "raspi.tv" article, the problem is that you're using an Ethernet straight-through cable when you need a crossover cable. Gigabit Ethernet ports have "auto-crossover"/"auto-uplink" functionality built in, so you can connect any two ports using any type of cable, but older hardware, like the 10Base-T ...


1

It is possible to forward traffic from the wired interface (eth0?) to the usb0 interface. Because you do not have provided any details about your network configuration I can only guess. You have to enable ip forwarding. There are several ways to do it: within /etc/sysctl.conf or by systemd-networkd or with /proc/sys/net/ipv4/ip_forward. Because you have ...


1

How simultaneously do you need it to be? If "within a couple of seconds" is fine, then just call your scripts sequentially via SSH: sshpass -p 'raspberry' ssh pi@192.168.0.2 python take_photo.py & sshpass -p 'raspberry' ssh pi@192.168.0.3 python take_photo.py & You may want to setup a passwordless login to make the commands simpler. If you need to ...


1

Try swapping the two Raspberries around: I would expect that the one you connect via the Ethernet will still be the one that cannot be pinged. The problem then lies in the router (or whatever device you have which provides the Internet access to the rest of your network). ping sends data via Internet Control Message Protocol (ICMP), so that's what you ...


1

I would say ifplugd is the right daemon to solve your problem. But the Debian package for it uses old style ifupdown managed with /etc/network/interfaces. Since Raspbian Stretch dhcpcd is used for networking instead of ifupdown so support for ifplugd is also "deprecated". I think to use a complete outdated Raspbian version Jessie only for this issue is not a ...


1

It's been a week, and only now did i realize what i had done wrong. Apparently i accidentally forgot to save the config for SSH preferences, and when I re-enabled them on the rpi's UI for it's config it worked, no human error this time. IP was fine, port was clear.


1

You have two default routes: Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 The default route is used for all ip packages that destination address does not belong to ...


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