* add interface for connection to Inmarsat
* remove 'br0' and work directly with 'eth2' instead, to avoid bridges
in vlans of bridges
* bridge the video LAN also into the backbone (for later break-out)
Create the /run/network directory for all of our systems. The
proper way with tmpfiles.d ends with a depedency mess that has
no point in being debugged.
My local build hasn't completed yet but we need to rush. Let the
CI test this change and we will see.
Related: SYS#1514
It looks like on my tests with the sysmobts I was saved by
busybox-ifplogd executing ifup again. I couldn't figure out
the dependencies between the LSB networking service and the
tmpfiles.d interaction. So instead of winning a beauty contest
we will need to create the directory by hand.
Cause: SYS#1514
Revert "ifupdown: Package the new file as well"
This reverts commit 15dc869cda.
Revert "ifupdown: Try the workdir for the files we copied"
This reverts commit 1ef790672e.
Revert "ifupdown: Create /run/network through a tmpfiles.d"
This reverts commit e0c7f3c621.
This way the ifupdown application will not only work
for the IDU/ODU but the BTS, BSC and any other machine
we want to build.
(untested OE modification)
To be able to talk to the equipment we need to set a route
after the link is up. Assume that no other (e.g. 3G) equipment
is using the same IPv4 address range.
Message-ID: 55279904.9020802@sysmocom.de
Harald Welte
Holger Hans Peter Freyther
Henning Heinold