Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Maciej Borzecki <maciej.borzecki@open-rnd.pl>,
	 openembedded-core@lists.openembedded.org,
	Chen Qi <Qi.Chen@windriver.com>,
	Otavio Salvador <otavio@ossystems.com.br>,
	 Ross Burton <ross.burton@intel.com>,
	"Peter A. Bigot" <pab@pabigot.com>
Cc: Maciek Borzecki <maciek.borzecki@gmail.com>
Subject: Re: [PATCH] systemd-networkd: cherry picking route handling patch
Date: Thu, 08 Jan 2015 14:35:54 -0800	[thread overview]
Message-ID: <54AF064A.4070608@gmail.com> (raw)
In-Reply-To: <1420706622-31273-1-git-send-email-maciej.borzecki@open-rnd.pl>

Does this affect Dizzy?

- armin

On 01/08/2015 12:43 AM, Maciej Borzecki wrote:
> There is a problem in systemd-networkd version used in OE-core (216 as
> of now) that prevents a successful communication in a configuration
> that uses a static or IPv4 LL address alongside a dynamically obtained
> one. The setup is rather not uncommon as is makes sense to always have
> a static well known address that a technician or a support engineer
> can access while in the field.
>
> The current code in systed-networkd uses a clever trick to add a
> static route to the gateway, to workaround a misconfigured DHCP server
> that would assign an address from network pool that the gateway is not
> a part of. The trick was missing a source IP address specification in
> the static route, thus normally the first assigned IP address would be
> used for outgoing IP packets. In this particular case the address
> would the static one, hence the packet would most probably be dropped
> by the router. Also, it is quite common in smaller networks that the
> DHCP server, gateway router and even a DNS server are colocated. In
> these setups the current code will effectively render any
> communication to or past the router impossible.
>
>
> Maciej Borzecki (1):
>    systemd: cherry-pick patch fixing networkd gateway route handling
>
>   ...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
>


  parent reply	other threads:[~2015-01-08 22:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  8:43 [PATCH] systemd-networkd: cherry picking route handling patch Maciej Borzecki
2015-01-08  8:43 ` [PATCH] systemd: cherry-pick patch fixing networkd gateway route handling Maciej Borzecki
2015-01-08 14:14   ` Otavio Salvador
2015-01-08 15:46     ` Maciej Borzecki
2015-01-08 16:04       ` Otavio Salvador
2015-01-08 19:59   ` Maciej Borzecki
2015-01-08 20:36     ` Otavio Salvador
2015-02-02  7:36       ` Maciej Borzecki
2015-02-02  7:52         ` Maciej Borzecki
2015-01-08 14:13 ` [PATCH] systemd-networkd: cherry picking route handling patch Otavio Salvador
2015-01-08 19:44   ` Maciej Borzecki
2015-01-08 19:54     ` Peter A. Bigot
2015-01-08 22:35 ` akuster808 [this message]
2015-01-09  8:12   ` Maciej Borzecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AF064A.4070608@gmail.com \
    --to=akuster808@gmail.com \
    --cc=Qi.Chen@windriver.com \
    --cc=maciej.borzecki@open-rnd.pl \
    --cc=maciek.borzecki@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=pab@pabigot.com \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox