Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #255250

Re: Remove route '169.254.0.0/16 dev ovs-system'

From Jeffrey Walton <noloader@gmail.com>
Newsgroups linux.debian.user
Subject Re: Remove route '169.254.0.0/16 dev ovs-system'
Date 2023-02-21 19:10 +0100
Message-ID <G1Ffs-7wbB-9@gated-at.bofh.it> (permalink)
References (1 earlier) <G0UTf-72PX-3@gated-at.bofh.it> <G14zf-78J5-5@gated-at.bofh.it> <G1fEl-7gkd-15@gated-at.bofh.it> <G1Dnj-7v4O-3@gated-at.bofh.it> <G1EW5-7vPC-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus
<c.brinkhaus@t-online.de> wrote:
> Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin:
> > On 20/02/2023 21:44, Christoph Brinkhaus wrote:
> > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max > > > > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly
> > > > configure network interface, either to ensure that DHCP server is available
> > > > or to assign a static address. After that you may forget about existence of
> > > > avahi-autoipd.
> > >
> > > On my system it did not help. One "issue" might be, that systemd
> > > starts services in some sequence. But it does not wait for a service
> > > to complete. At least in case of stuff I have observed on my system.
> >
> > Out of curiosity, is link-local IP address assigned during boot or later
> > when e.g. WiFi connection is temporary lost? How long does it take to get
> > response from DHCP server? Which way network is configured (ifupdown,
> > NetworkManager, systemd-networkd) in your case?
>
> The 169.254.x.y has been assigned during boot. I have not used DHCP.
> The configuration has been static. The ping to the router takes about
> 4ms. I have no idea if it is possible to estimate a DHCP response
> time. The network has been configured via systemd-networking.

You have to supply a static ip address or a DHCP server.

Since you supplied a static ip address, then the fact that you are
getting an APIPA is a bug. You should file a bug report with the
package (Avahi? Systemd?) that is providing the APIPA.

But backing up... I suspect there's something wrong with your static
ip address assignment. The address is already taken, the netmask is
wrong, or the gateway is wrong.

Looking back through this thread, I did not see where you showed your
static ip configuration. Maybe you should start with that. If it is
bad, then the APIPA is just a symptom of the [static ip address]
problem.

Jeff

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Remove route  '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-19 17:30 +0100
  Re: Remove route  '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-19 17:40 +0100
    Re: Remove route  '169.254.0.0/16 dev ovs-system' Stefan Monnier <monnier@iro.umontreal.ca> - 2023-02-19 18:30 +0100
      Re: Remove route  '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-19 20:00 +0100
        Re: Remove route  '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-19 20:20 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-20 05:40 +0100
    Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-20 04:00 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-20 05:20 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-20 15:50 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-21 17:10 +0100
          Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-21 18:50 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-21 19:10 +0100
              Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-21 19:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-21 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' <tomas@tuxteam.de> - 2023-02-21 20:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-22 20:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Greg Wooledge <greg@wooledge.org> - 2023-02-22 20:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Darac Marjal <mailinglist@darac.org.uk> - 2023-02-22 21:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-22 16:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-22 17:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-24 16:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-24 19:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-24 20:30 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-24 22:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-25 03:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-26 12:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-26 14:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-26 15:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-26 15:50 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Geert Stappers <stappers@stappers.nl> - 2023-02-27 23:00 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-28 07:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Max Nikulin <manikulin@gmail.com> - 2023-02-26 16:20 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-26 18:10 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' David Wright <deblis@lionunicorn.co.uk> - 2023-02-25 04:00 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-25 04:40 +0100
                Re: Remove route '169.254.0.0/16 dev ovs-system' Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-25 13:50 +0100
                unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-02-26 16:40 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-26 17:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-26 19:10 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') David Wright <deblis@lionunicorn.co.uk> - 2023-02-26 20:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-28 11:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-03-02 15:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-02 16:30 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Max Nikulin <manikulin@gmail.com> - 2023-03-03 16:20 +0100
                Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev  ovs-system') Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-03-03 16:30 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Reco <recoverym4n@enotuniq.net> - 2023-02-21 19:30 +0100
  Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 07:00 +0100
    Re: Remove route '169.254.0.0/16 dev ovs-system' <tomas@tuxteam.de> - 2023-02-20 08:30 +0100
      Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 08:50 +0100
        Re: Remove route '169.254.0.0/16 dev ovs-system' tomas@tuxteam.de - 2023-02-20 10:10 +0100
          Re: Remove route '169.254.0.0/16 dev ovs-system' rhkramer@gmail.com - 2023-02-20 15:30 +0100
            Re: Remove route '169.254.0.0/16 dev ovs-system' Jeffrey Walton <noloader@gmail.com> - 2023-02-20 16:10 +0100
  Re: Remove route  '169.254.0.0/16 dev ovs-system' The Wanderer <wanderer@fastmail.fm> - 2023-02-20 16:20 +0100

csiph-web