July-14th-2021, 11:41 AM
(This post was last modified: July-14th-2021, 01:30 PM by Armin@netPI.)
Hi there and welcome.
could you first of all confirm you are using a device NIOT-E-NPI3-EN or NIOT-E-NPI3-EN-RE please.
1.) No this is not normal. netPI runs internally a Linux operating system which is using a standard TCP/IP stack to feature the single eth0 Etnernet port. This eth0 port gets an IP address and gateway address from a DHCP by default. With both settings the netPI can be reached from anywhere with its legal IP address outside the local subnet also. For example in the office we have several netPIs running spread all over the building floors. On is located at ip 10.11.5.61, one is located at 192.168.10.41 ... all these netPIs I can reach from my office notebook with IP 10.11.30.15 without any problems
When you have deployed the raspbian container correctly on netPi as descibed in the containers README here https://hub.docker.com/r/hilschernetpi/netpi-raspbian/ then indeed the raspbian container will ask you for a login name and a password as it is usual for Raspbian OS. On this page you also see that this container has been pulled meanwhile 100.000+ more times. So it is proven in use. For me it seems that the deployment of specifically your Raspbian container was somehow misconfigured in netPI's portainer.io web UI.
2.) netPI relies on a DHCP server only during the first startup. This is the default setting. But in the main control center you can change the eth0 LAN port settings to a static value, you can change the subnet and also the gateway address manually
3.) No this is not correct. Portainer on netPI is installed natively and not as running container. We did this cause we wanted to avoid that users can disable the portainer.io container in the portainter web ui itself ... and would then lose any configuration possibilities. Portainer web-ui is started automaticall along with the Docker deamon at the same time.
4.) No this is not possible. We decided not so offer the SSH/Console feature since the product introduction in year 2016. The only chance you have with netPI is doing anything across portainer concerning the Docker Management.
You said you have difficulties getting started with netPI. I recommend watching youtube videos I made years ago like https://youtu.be/CB6bYfMbFhA or this one here https://youtu.be/A-asfhl7b0c
Thx
Armin
could you first of all confirm you are using a device NIOT-E-NPI3-EN or NIOT-E-NPI3-EN-RE please.
1.) No this is not normal. netPI runs internally a Linux operating system which is using a standard TCP/IP stack to feature the single eth0 Etnernet port. This eth0 port gets an IP address and gateway address from a DHCP by default. With both settings the netPI can be reached from anywhere with its legal IP address outside the local subnet also. For example in the office we have several netPIs running spread all over the building floors. On is located at ip 10.11.5.61, one is located at 192.168.10.41 ... all these netPIs I can reach from my office notebook with IP 10.11.30.15 without any problems
When you have deployed the raspbian container correctly on netPi as descibed in the containers README here https://hub.docker.com/r/hilschernetpi/netpi-raspbian/ then indeed the raspbian container will ask you for a login name and a password as it is usual for Raspbian OS. On this page you also see that this container has been pulled meanwhile 100.000+ more times. So it is proven in use. For me it seems that the deployment of specifically your Raspbian container was somehow misconfigured in netPI's portainer.io web UI.
2.) netPI relies on a DHCP server only during the first startup. This is the default setting. But in the main control center you can change the eth0 LAN port settings to a static value, you can change the subnet and also the gateway address manually
3.) No this is not correct. Portainer on netPI is installed natively and not as running container. We did this cause we wanted to avoid that users can disable the portainer.io container in the portainter web ui itself ... and would then lose any configuration possibilities. Portainer web-ui is started automaticall along with the Docker deamon at the same time.
4.) No this is not possible. We decided not so offer the SSH/Console feature since the product introduction in year 2016. The only chance you have with netPI is doing anything across portainer concerning the Docker Management.
You said you have difficulties getting started with netPI. I recommend watching youtube videos I made years ago like https://youtu.be/CB6bYfMbFhA or this one here https://youtu.be/A-asfhl7b0c
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
