Yes I've tried on both ports, I'm also suspicious about the script that exchanges the eth interfaces.

I'll try to build that commit https://github.com/siemens/meta-iot2050/archive/16bc4f221de26386b3c6051e0fc05e1eabb3c68b.zip

I'll get back to you with the result

This one works correctly, I can connect to SSH at 192.168.200.1 on port P1 so the script that exchanges the ports is working fine..

I suspect that the issue cames from kas 2.2, I'll try to build the last commit with kas 2.1.1

https://github.com/siemens/meta-iot2050/archive/56532fec39baf372db219e707830e68f386cba39.zip

I was wrong this commit 6532fec39 already isn't working, I'll try with https://github.com/siemens/meta-iot2050/archive/d152865e677cf72d1d8d321b4036598cb11ecc8f.zip

Hi,

I have face the same issue with IOT2050 basic but now it is resolved. Please find the below steps might be helpful.

IOT2050 CONNECTION:

1. Download Debian image from here
2. Insert SD card into adapter

        - Use SD card formatter to format the card

1. Burn the image on SD card

       - Use Win32DiskImager to write on disk

1. Insert the SD card into IOT box
2. 25V power, on the box
3. Connect ethernet cable to P2
4. Change the network connections Ethernet setting

        - Assign static IPV4 address on the range of 200.

1. Ping on 192.168.200.1 static IP > If there is response ??
2. Try SSH on same IP

Ok I've finally detected after building so many images where the issue begin:

The last working commit is 47044854ef5e79025a3118e6b3da4092550eed98

From commit d152865e677cf72d1d8d321b4036598cb11ecc8f The issue begin to happen.

Hope now you can fix this bahavior! Thank you!