RTE3 Use real time ethernet as "normal" ethernet interface

[Armin@netPI]

Hello Andi,

I see the same effect like you do. I tried to understand the root cause of the error "RTNETLINK answers: Network is down" and I have learned that using an "ip route" command on any interface needs to have it in "up" state before the command can be used. This is not how it is realized today. I never saw this problem cause my interface was "up" always and hence all "ip route" commands worked right away.

Meanwhile I am getting this in my container when I am using your IP setup

Code:

root@b8e92e0e5baf:/# ip route
default via 172.17.0.1 dev eth0
10.7.1.0/24 via 10.7.1.1 dev cifx0
10.7.1.1 dev cifx0 scope link
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2

Is it how it shall look like?