This is something that has probably been done numerous times, but I have not found an instant recipe for.
With a RPi4 (maybe a 5 later) and a to-be-installed raspian version (or other OS, if better for my purpose), I need the following:
The RPi Ethernet might be connected to an existing network (V4/V6) with DHCP, usually a 192.168.x/24. This is for setup and config via SSH, but not for regular work.
The RPI Wifi should span a separate network, no NAT or other routing to the Ethernet side necessary or even desirable. The Wifi should be a 10/8 V4 only network with the RPi having the 10.0.0.1, and should supply its own DHCP service for the range of 10.0.0.2 onwards. DNS is not necessary, as all devices in the wifi (RPI Pico W) "know" to talk to the 10.0.0.1 host only - their MQTT broker (mosquitto).
Is there any tutorial/recipe for this available somewhere? I know my way around ifconfig and route, but have no real experience with those fancy config file manglers that seem to be the current fad in network setup.
With a RPi4 (maybe a 5 later) and a to-be-installed raspian version (or other OS, if better for my purpose), I need the following:
The RPi Ethernet might be connected to an existing network (V4/V6) with DHCP, usually a 192.168.x/24. This is for setup and config via SSH, but not for regular work.
The RPI Wifi should span a separate network, no NAT or other routing to the Ethernet side necessary or even desirable. The Wifi should be a 10/8 V4 only network with the RPi having the 10.0.0.1, and should supply its own DHCP service for the range of 10.0.0.2 onwards. DNS is not necessary, as all devices in the wifi (RPI Pico W) "know" to talk to the 10.0.0.1 host only - their MQTT broker (mosquitto).
Is there any tutorial/recipe for this available somewhere? I know my way around ifconfig and route, but have no real experience with those fancy config file manglers that seem to be the current fad in network setup.
Statistics: Posted by ChTreczoks — Mon Jun 10, 2024 9:26 am
