[OE-core] [PATCH] systemd: cherry-pick patch fixing networkd gateway route handling

[Otavio Salvador]

On Thu, Jan 8, 2015 at 1:46 PM, Maciej Borzecki
<maciej.borzecki at open-rnd.pl> wrote:
> On 01/08 12:14, Otavio Salvador wrote:
>> On Thu, Jan 8, 2015 at 6:43 AM, Maciej Borzecki
>> <maciej.borzecki at open-rnd.pl> wrote:
>> > Cherry-picking a patch that fixes gateway route handling in
>> > systemd-networkd. The patch adds a source IP to the automatically added gateway
>> > static route, this thus allowing for proper communication in case a static or
>> > IPv4 LL address is used alongside a dynamically obtained one.
>> >
>> > (From systemd rev: 46b0c76e2c355c0d0cc4792abb98cde07b28bc5)
>> >
>> > Signed-off-by: Maciej Borzecki <maciej.borzecki at open-rnd.pl>
>> > Signed-off-by: Maciek Borzecki <maciek.borzecki at gmail.com>
>> > ---
>> >  ...d-preferred-source-to-dhcp4-gateway-route.patch | 109 +++++++++++++++++++++
>> >  meta/recipes-core/systemd/systemd_216.bb           |   1 +
>> >  2 files changed, 110 insertions(+)
>> >  create mode 100644 meta/recipes-core/systemd/systemd/0001-networkd-add-preferred-source-to-dhcp4-gateway-route.patch
>> >
>> > diff --git a/meta/recipes-core/systemd/systemd/0001-networkd-add-preferred-source-to-dhcp4-gateway-route.patch b/meta/recipes-core/systemd/systemd/0001-networkd-add-preferred-source-to-dhcp4-gateway-route.patch
>> > new file mode 100644
>> > index 0000000..1a9e8ee
>> > --- /dev/null
>> > +++ b/meta/recipes-core/systemd/systemd/0001-networkd-add-preferred-source-to-dhcp4-gateway-route.patch
>> > @@ -0,0 +1,109 @@
>> > +From 46b0c76e2c355c0d0cc4792abb98cde07b28bc53 Mon Sep 17 00:00:00 2001
>> > +From: Emil Renner Berthing <systemd at esmil.dk>
>> > +Date: Fri, 5 Sep 2014 11:56:02 +0200
>> > +Subject: [PATCH] networkd: add preferred source to dhcp4 gateway route
>> > +
>> > +This makes DHCPv4 and IPv4LL coexist peacefully.
>> > +
>> > +[tomegun: apply to both the dhcp routes, use in_addr_is_null() rather than a
>> > +separate variable to indicate when prefsrc should be applied]
>>
>> Missing Upstream-Status field.
>
> I'm guessing
>
> Upstream-Status: backport
>
> is the correct stanza?

Yes, and [<version>] so we know the referenced version when updating it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750