<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On Friday 06 October 2017 07:36 PM,
      Susant Sahani wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAH5UemqQKhv_0nsLuAksnS7x7zQ-7jixbfcT8=9b1SO+CeVW2A@mail.gmail.com">
      <div dir="auto">
        <div dir="ltr">
          <div class="gmail_extra"><br>
            <div class="gmail_quote">On Fri, Oct 6, 2017 at 3:03 PM,
              Amish <span dir="ltr"><<a
                  href="mailto:anon.amish@gmail.com" target="_blank"
                  moz-do-not-send="true">anon.amish@gmail.com</a>></span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">Hello,<br>
                <br>
                Thank you. I am curious to know if this new setting:<br>
                ConfigureWithoutCarrier=1 would resolve my query few
                months back.<br>
                (Although I would not be able to try it out yet for 2-3
                weeks)<br>
                <br>
                Subject: Persistent address on "Lost carrier"<br>
                Link: <a
href="https://lists.freedesktop.org/archives/systemd-devel/2017-June/039041.html"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.freedesktop.org/<wbr>archives/systemd-devel/2017-Ju<wbr>ne/039041.html</a><br>
                <br>
                i.e. systemd-networkd should not remove IP address and
                routes on "Lost carrier".<br>
                <br>
                I looked at the code here:<br>
                <a
href="https://github.com/systemd/systemd/blob/master/src/network/networkd-link.c"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://github.com/systemd/sys<wbr>temd/blob/master/src/network/n<wbr>etworkd-link.c</a><br>
                <br>
                It appears that - it is still not so.<br>
                <br>
                i.e. If carrier is lost (eg. cable removed / network
                issues) then<br>
                link_update() function would go ahead and call
                link_carrier_lost()<br>
                and unconfigure the device.<br>
                <br>
                i.e. it will not obey ConfigureWithoutCarrier=1 which I
                believe it should.<br>
              </blockquote>
              <div><br>
              </div>
              <div>No that is not intended use case for
                 ConfigureWithoutCarrier=. It will only look during
                configuring the the link.</div>
              <div> While configuring a link even if that link has no
                carrier it will go on set it as configured for example
                empty bridges.<br>
              </div>
              <div><a
                  href="https://github.com/systemd/systemd/issues/6645"
                  target="_blank" moz-do-not-send="true">https://github.com/systemd/<wbr>systemd/issues/6645</a>.
                But in your case It is already configured via gained
                carrier not via </div>
              <div>ConfigureWithoutCarrier even if you set it to true.</div>
              <div><br>
              </div>
              <div><br>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    My issue is on similar lines too. May be extension to it.<br>
    <br>
    i.e. if ConfigureWithoutCarrier is set then it should not
    Un-configure when carrier is lost.<br>
    <br>
    The problem I face is that I have some IPs via certain "secure"
    interface. (set via [Route])<br>
    <br>
    But if carrier is lost for a while for any reason then IP address as
    well as routes get deleted.<br>
    <br>
    When routes get deleted then packets to those IPs start going via
    "default" route which becomes security risk.<br>
    <br>
    I can workaround this via firewall.<br>
    <br>
    But it would be great if ConfigureWithoutCarrier is checked for
    carrier_lost case too and IP is not un-configured.<br>
    <br>
    Thanks and regards,<br>
    <br>
    Amish.<br>
  </body>
</html>