March-22nd-2018, 06:12 PM
Hello Iotuser,
this is very easy. If you use the option "network=host" then docker starts the container using the same TCP/IP stacks as the Linux Host system. In this case it is not a matter of the physical interfaces eth0 and wifi any more, but just a matter of the ip addresses that you have configured.
So make a simple test:
If you configure the eth0 IP address of netPI to 192.168.30.1 for example then you can reach the node-red under 192.168.30.1:1880.
If you now configure the wifi address of netPI to 192.168.40.1 for example (in access point mode) and you connect your mobile phone to this wifi network getting then you can reach node-red under 192.168.40.1:1880 also.
this is very easy. If you use the option "network=host" then docker starts the container using the same TCP/IP stacks as the Linux Host system. In this case it is not a matter of the physical interfaces eth0 and wifi any more, but just a matter of the ip addresses that you have configured.
So make a simple test:
If you configure the eth0 IP address of netPI to 192.168.30.1 for example then you can reach the node-red under 192.168.30.1:1880.
If you now configure the wifi address of netPI to 192.168.40.1 for example (in access point mode) and you connect your mobile phone to this wifi network getting then you can reach node-red under 192.168.40.1:1880 also.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
