You appear to want a DHCP server (although it is unclear why) but appear to have configured dhcpcd to use an external server.
You can only have ONE server on a network segment.
If you are attempting to create an access point you can use interfaces but disable dhcpcd, or tell dhcpcd not to configure an interface.
If you connect them with a simple CAT5 cable (568A to 568A or 568B to 568B, no crossover needed) then assign an IP address on each end of the link it will "just work".
The system will assign an IP address from 169.254.xxx.xxx automatically by default, but that's a pain as you have to find the new IP address each time you reboot either system. ...
You should also check that the wifi devices are not blocked by rfkill - you can do so like this:
rfkill list wifi
If any are listed as blocked you can unblock all wifi devices using this command:
sudo rfkill unblock wifi
Or just enable/unblock a specific one by adding its index (from the rfkill list) e.g:
sudo rfkill unblock wifi 0
Yes with the correct software on your Pi 4
Not sure what you mean by this
Have a look at MotionEyeOS for your Pi4, this works well with both Pi zero W and other network cameras. I have a Pi4 8gb running MotionEyeOS and currently hosting a Pi zero camera, a Pi 3 camera, 2 network cameras and an ESP32 Cam. I assume you have internet and WiFi etc at ...
It seems you want to run a DHCP server on your Pi and give IP addresses to your other devices connecting to your Pi's wlan0 and eth0. You don't need NAT since the Pi will act like a switch.
The most simple solution is to run another instance of your DHCP server (in your case, dnsmasq) on your eth0, since it seems you already have one running on your wlan0.
I would just delete connman - from similar posts the dhcpcd plugin (I would have to search to find its name) appears to be installed.
Its normal operation depends on the dhcpcd service (which appears to be running) but dhcpcd disables itself and its wpa supplicant plug-in if another DHCP client is active.
I will investigate later if this doesn't resolve ...
Check the documentation of your web server. In Apache, this is done with mod_authz_core:
Require ip <list of addresses>
Before proceeding, check that all your friends actually have static public IP addresses which you could list. Most people have dynamic IPs which change a couple of times a day, making your approach incredibly hard to maintain.
Not to ...
Sorry to say this, but it looks like a quirk of your "modem". If it is managed remotely by your provider (I assume you didn't create a guest network, did you?) there may be little you can do.
Perhaps the connection times out if it's inactive. Check the settings of your box if you have access to them. Alternatively, try setting up a program which ...
gksudo is deprecated now. Having said that, if you're issuing commands manually, you can just use sudo instead.
Set the following options in your ssh_config:
The first option alone will work, but keep in mind that untrusted X sessions expire after 20 minutes or so, making you wonder why your GUI apps suddenly stop ...
The solution that worked for me was setting up the wireless access point manually by following steps in https://www.raspberrypi.com/documentation/computers/configuration.html#setting-up-a-routed-wireless-access-point, than replacing the routing rule to direct traffic to wlan1 instead of eth0 as the original article directs:
sudo iptables -t nat -D ...