Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-03-03 Thread Christoph Brinkhaus
Am Fri, Mar 03, 2023 at 10:09:42PM +0700 schrieb Max Nikulin: > On 02/03/2023 22:27, Christoph Brinkhaus wrote: > > Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin: > > > On 28/02/2023 17:25, Christoph Brinkhaus wrote: > > > > I will just inform about the status. Everything is fine

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-03-03 Thread Max Nikulin
On 02/03/2023 22:27, Christoph Brinkhaus wrote: Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin: On 28/02/2023 17:25, Christoph Brinkhaus wrote: I will just inform about the status. Everything is fine now. A word about systemd-networkd-wait-online: With this service running there

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-03-02 Thread Christoph Brinkhaus
Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin: > On 28/02/2023 17:25, Christoph Brinkhaus wrote: > > I will just inform about the status. Everything is fine now. A word > > about systemd-networkd-wait-online: With this service running there > > has been even a delay of 1-2 seconds

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-03-02 Thread Max Nikulin
On 28/02/2023 17:25, Christoph Brinkhaus wrote: I will just inform about the status. Everything is fine now. A word about systemd-networkd-wait-online: With this service running there has been even a delay of 1-2 seconds when switching from one console to a different one (the consoles when X is

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-02-28 Thread Christoph Brinkhaus
Am Sun, Feb 26, 2023 at 01:21:07PM -0600 schrieb David Wright: Hello David and Max, > On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote: > > Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > > > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > > > Now there are

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-02-26 Thread David Wright
On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote: > Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > > Now there are no messages reported by journald as above. > > > > I am curious if fixing unbound and so

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-02-26 Thread Christoph Brinkhaus
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > Now there are no messages reported by journald as above. > > I am curious if fixing unbound and so network-online.target helped to avoid > 169.254.x.y address in your case. Can

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-02-26 Thread Christoph Brinkhaus
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin: > On 25/02/2023 19:49, Christoph Brinkhaus wrote: > > Now there are no messages reported by journald as above. > > I am curious if fixing unbound and so network-online.target helped to avoid > 169.254.x.y address in your case. I am

unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

2023-02-26 Thread Max Nikulin
On 25/02/2023 19:49, Christoph Brinkhaus wrote: Now there are no messages reported by journald as above. I am curious if fixing unbound and so network-online.target helped to avoid 169.254.x.y address in your case. Can fetchmail work without a kludge you added to achieve some delay? My