Hi,

if u got serial line access you can call

ifdown <netdev>

ifup <netdev>

This helped me

If you have a serial line connection

ifdown eth0

ifup eth0

works fine.

After udhcpc or ping worked here.

If eth1 is not visible

ifdown eth1

ifup eth1

fix it.

Best regards

On the IoT2020 there is of course only one ethernet port, with the public available image it will not work... Sorry.

With the separate engineering image it will. This same port on the IoT2040 sample also has the same issue but the second Ethernet port eth1. does still work and defaults to DHCP protocol. (eth0 is set to static)

If you have the Engineering image both should work but eth0 will default to IP address 192.168.200.1, you will have to modify your PC IP to be on the same subnet or re-configure the /etc/network/interfaces file to change this.

for the IoT2020 I simply re-configured eth0 to be DHCP

This is my file for the IoT2040

And this is the one for the IoT2020, as you will see I also have a PCIE WIFI adapter up and running, the official PI WIFI will also work well

for more info see my videos

Hii anku0815,

I also had the same problem. But I was able to connect to 192.168.200.1 by changing the IPv4 address of host system to 192.168.200.2 and subnetmask 255.255.255.0.

Once connection is established, change the static IP address to a series coming in the range of our Ethernet connection. Then again change the IPv4 address to the previous one.

 Hi Sir, 

I have followed all the steps shown in your video (but in my case when i have mode the changes to the "eth0" to dhcp via WinSCP while the putty window is still open & running but i am not able to continue with the step "ifdown eth0" & "ifup eth0". The putty connection is aborted the moment when i finish making the changes at WinSCP. I am basically stuck here (i am not sure on how to find the ip address of the IOT2020 now to start the putty connection.

On the IoT2020 there is of course only one ethernet port, with the public available image it will not work... Sorry.

With the separate engineering image it will. This same port on the IoT2040 sample also has the same issue but the second Ethernet port eth1. does still work and defaults to DHCP protocol. (eth0 is set to static)

If you have the Engineering image both should work but eth0 will default to IP address 192.168.200.1, you will have to modify your PC IP to be on the same subnet or re-configure the /etc/network/interfaces file to change this.

for the IoT2020 I simply re-configured eth0 to be DHCP

This is my file for the IoT2040

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface

auto lo

iface lo inet loopback

# Wired interfaces

auto eth0

iface eth0 inet static

address 192.168.200.1

netmask 255.255.255.0

auto eth1

iface eth1 inet dhcp

And this is the one for the IoT2020, as you will see I also have a PCIE WIFI adapter up and running, the official PI WIFI will also work well

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface

auto lo

iface lo inet loopback

# Wired interfaces

auto eth0

iface eth0 inet dhcp

# Wireless interfaces

auto wlan0

iface wlan0 inet dhcp

wireless_mode managed

wireless_essid any

wpa-driver wext

wpa-conf /etc/wpa_supplicant.conf

for more info see my videos

I tried to put the IOT2020 sd image on intel galileo gen 1 board and I have similar problems:

- putty and winscp not connect

- default ip is not enabled

- the static ip is not store after reboot.

After 2 days to find a solution for this I get the problems!!

The old firmware Intel firmware on board (~7xx).

After upgrade of firmware to 1.1.0 the board work very well.

So, maybe the Siemens IOT have a similar problem (sd card image is not compatible with intel firmware) !!!

I have the same problem. I wrote the image from Siemens Support to microSD, then plugged it in IoT2040 and powered on. When I try to ping 192.168.200.1 (via X1P1), it didn't reply. The same happened with X2P1. Please help me to solve this problem :(