February-24th-2021, 01:17 PM
Hello Armin,
after a morning of try and error I have new conclusions.
The TOSIBOX container can not be avtivated when within it's own, bridged network, 10.10.10.0/24, GW 10.10.10.1
If I move the TOSIBOX container to the build-in bridged network 172.17.0.0/16, GW 172.17.0.1, I can activate the TOSIBOX.
In the TOSIBOX container a static route is added to the network at the cifx0 port 192.168.1.0.
With the gateway 10.10.10.1 or 172.17.0.1 as needed
But I'm only able to access 192.168.1.1 which is the host address of the cifx0 port. The device connected to the port is unreachable.
I have cross checked it with my other NIOT-E-TPI51-EN-RE with same Firmware-Version. Here I'm able to connect to the device 192.168.1.180 via TOSIBOX.
Looking forward to your next ideas,
Carsten
after a morning of try and error I have new conclusions.
The TOSIBOX container can not be avtivated when within it's own, bridged network, 10.10.10.0/24, GW 10.10.10.1
If I move the TOSIBOX container to the build-in bridged network 172.17.0.0/16, GW 172.17.0.1, I can activate the TOSIBOX.
In the TOSIBOX container a static route is added to the network at the cifx0 port 192.168.1.0.
With the gateway 10.10.10.1 or 172.17.0.1 as needed
But I'm only able to access 192.168.1.1 which is the host address of the cifx0 port. The device connected to the port is unreachable.
I have cross checked it with my other NIOT-E-TPI51-EN-RE with same Firmware-Version. Here I'm able to connect to the device 192.168.1.180 via TOSIBOX.
Looking forward to your next ideas,
Carsten
