* 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)
linux-sysmocom_git.bb is used for the BTS, BSC and IDU. Let's
really use 3.10.76 (from 3.10.50 just rebased and not tested
on the device yet). This should fix the Yocto-Master build
tonight.
9610e792ffde7fb2599d19ca6d2a03230f2043c6 can not be found
in the linux-3.10.76 branch. Just avoid this branch game.
ERROR: Fetcher failure: Unable to find revision 9610e792ffde7fb2599d19ca6d2a03230f2043c6 in branch linux-3.10.76 even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://git.sysmocom.de/sysmo-bts/linux.git;protocol=git;branch=linux-3.10.76'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/linux-sysmocom/3.10.76+gitAUTOINC+9610e792ff-r43/temp/log.do_fetch.16350
NOTE: recipe linux-sysmocom-3.10.76+gitAUTOINC+9610e792ff-r43: task do_fetch: Failed
ERROR: Task 126 (/home/builder/jenkins/workspace/Yocto-Master/label/OE/meta-sysmocom-bsp/recipes-bsp/linux/linux-sysmocom_git.bb, do_fetch) failed with exit code '1
It seems like the kernel/package/upgrade/... proceess doesn't deal well
with the fact that some options used to be modules, which are now
built-in. Let's keep it as modules for the time being.
this enables conntrack events, ipset, ebtables, tc
scheduler/classifiers/ematches and much more.
it also disables the ATM code for which I don't think we have any use
case.
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
As pointed out by Harald the PR is lower than the package
that is already on the device. Bump it to 6 then.
Current:
opkg list_installed | grep ntp
ntp - 4.2.8p1-r5.0
ntp-tickadj - 4.2.8p1-r5.0
ntpdate - 4.2.8p1-r5.0
Import ntp 4.2.8 from meta-networking. Our version has some weird
dependency issues that create build breakages and more.
Remove the pps-tools dependency compared to meta-networking and
leave the ntp.conf as doneby Harald (e.g. drift on /etc and not
in /var...). Now I have not verified the upgrade path but I sadly
merged testing to stable when the ntp changes were comitted on
monday. This means I can't easily test the upgrade.
This new version of ntp has quite a number of changes, e.g.
certain utilities requiring perl, and some programs are now in
/usr/sbin rather than /usr/bin.
I edited the config through make menuconfig and then used
savedefconfig but the diff from our config to a minimal
defconfig is too big. So I enabled the temp sensors and i2c
by hand.
Fixes: SYS#1148
For the V-ODU we want to have vlan support as well. This requires
to use the debian ifupdown which means we need a script that creates
/run/network early enough.
On eth1 we should also use a network from the 172.16 block rather than
the 10.23 that we used on the sysmoBSC
Also, we now use 172.16.4.0/23 natively on the bridged onboard network,
this is a temporary measure so existing JBs will still connect and get
an IP address before their software is updated to use VLAN6. After they
(and all APs, BTSs, etc.) have migrated, the 172.16.4.0/23 can be
removed.
Harald Welte
Holger Hans Peter Freyther
Henning Heinold