Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #255354
| From | Christoph Brinkhaus <c.brinkhaus@t-online.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Remove route '169.254.0.0/16 dev ovs-system' |
| Date | 2023-02-24 19:50 +0100 |
| Message-ID | <G2LiN-8dKn-3@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <G1Ffs-7wbB-9@gated-at.bofh.it> <G1FyN-7whV-3@gated-at.bofh.it> <G1Ze9-7IMf-15@gated-at.bofh.it> <G20tz-7Jto-3@gated-at.bofh.it> <G2I1z-8bOW-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin: > On 22/02/2023 23:45, Christoph Brinkhaus wrote: > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin: > > > On 22/02/2023 01:26, Christoph Brinkhaus wrote: > > > > [Unit] > > > > Description=A remote mail retrieval and forwarding utility > > > > After=network-online.target opensmtpd.service unbound.service > > > > Requires=opensmtpd.service unbound.service > ... > > In case of my fetchmail setup the culprit is unbound. At the startup > > of unbound it takes some time to exchange keys and so on. > > I have no experience with unbound and I am not sure at which moment it > notifies systemd that the service is ready. However I have found a recent > bug > https://github.com/NLnetLabs/unbound/issues/773 > "When used with systemd-networkd, unbound does not start until > systemd-networkd-wait-online.service times out" > > Perhaps the package in Debian has an older version of the unbound.service > file and so is not affected. > Hi Max, I have observed lines below in journald: Feb 22 15:41:44 lenovo systemd[1]: Reached target Network is Online. Feb 22 15:41:44 lenovo systemd[1]: Failed to start Wait for Network to be Configured. Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Feb 22 15:41:44 lenovo systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Feb 22 15:41:44 lenovo systemd-networkd-wait-online[362]: Event loop failed: Connection timed out Feb 22 15:41:25 lenovo systemd[1]: anacron.service: Succeeded. Feb 22 15:41:25 lenovo anacron[3261]: Normal exit (0 jobs run) Feb 22 15:41:25 lenovo anacron[3261]: Anacron 2.3 started on 2023-02-22 Feb 22 15:41:25 lenovo systemd[1]: Started Run anacron jobs. This looks related, thank you very much! I will have a look at the link. > ... > > > However avahi-autoipd should be started concurrently > > > with network configuration to assign link-local address in the case of > > > failure. > > > > In a different thread - it was about IPv6 which has mutated > > slightly - several users claimed that the avahi-autoip is useful for > > their business. > > I mean IPv4 link local addresses 169.254.x.y. My impression is that > avahi-autoipd was created for the cases when there is no point to setup > centralized DHCP server. On the other hand I agree that a router (and so > DHCP out of the box) is more wide spread configuration than connecting a > couple of devices directly or through a switch. I think so, too. Kind regards, Christoph -- Ist die Katze gesund schmeckt sie dem Hund.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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