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 now
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
h
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 wh
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 n
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 no
Hi.
On Mon, Feb 27, 2023 at 10:53:24PM +0100, Geert Stappers wrote:
> (Meanwhile solved with denyinterface in /etc/dhcpcd.conf)
>
>
> > Long story short, consider running "systemctl mask dhcpcd" unless you
> > need dhcpcd to work in a way described above.
>
> The laptop does need to ha
Hi.
On Sun, Feb 26, 2023 at 05:25:09PM +0300, Reco wrote:
> On Sun, Feb 26, 2023 at 03:14:22PM +0100, Geert Stappers wrote:
> > On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> > > On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
} } } } } Have you tried `journalctl --boot`?
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 networ
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 fetch
On Sun 26 Feb 2023 at 22:11:30 (+0700), Max Nikulin wrote:
> On 26/02/2023 18:18, Geert Stappers wrote:
> > AIUI is systemd-networkd the main player, dhcpcd some helper
> > and NetworkManager for contact with user.
>
> First of all, I would not touch dhcpcd.conf for a while.
>
> Is it assumed tha
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 no
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 expect
On 26/02/2023 18:18, Geert Stappers wrote:
AIUI is systemd-networkd the main player, dhcpcd some helper
and NetworkManager for contact with user.
First of all, I would not touch dhcpcd.conf for a while.
Is it assumed that ovs-system should get its IP address from DHCP?
If I understand it corr
Hi.
On Sun, Feb 26, 2023 at 03:14:22PM +0100, Geert Stappers wrote:
> Hi.
>
> On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> > On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> > > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> > > Feb 24 22
Hi.
On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: IAID cb:93:09:25
> > Feb 24 22:24:15 trancilo d
Hi.
On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: IAID cb:93:09:25
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: adding address
> fe80::56b2:
On Sat, Feb 25, 2023 at 09:42:49AM +0700, Max Nikulin wrote:
> On 25/02/2023 04:43, Geert Stappers wrote:
> > Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
> >
> > Ideas how to avoid it are welcome.
>
> Have you checked "journalctl --boot" for logs which component assigns
>
Am Fri, Feb 24, 2023 at 07:41:26PM +0100 schrieb Christoph Brinkhaus:
I reply to myself thanking Max.
> 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
On Fri, Feb 24, 2023 at 9:51 PM David Wright wrote:
>
> On Fri 24 Feb 2023 at 22:43:49 (+0100), Geert Stappers wrote:
> > [...]
> I see you rebooted, and you get the same address. It's ambiguous as
> to why: it could have been stored, which makes things more efficient
> when a number of machines
On Fri 24 Feb 2023 at 22:43:49 (+0100), Geert Stappers wrote:
> On Fri, Feb 24, 2023 at 01:25:55PM -0600, David Wright wrote:
> > On Fri 24 Feb 2023 at 19:41:26 (+0100), Christoph Brinkhaus wrote:
> > > Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin:
>
>
>
> > > >
> > > > I
On 25/02/2023 04:43, Geert Stappers wrote:
Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
Ideas how to avoid it are welcome.
Have you checked "journalctl --boot" for logs which component assigns
169.254.x.y address and for various errors related to network?
I am not fam
On Fri, Feb 24, 2023 at 01:25:55PM -0600, David Wright wrote:
> On Fri 24 Feb 2023 at 19:41:26 (+0100), Christoph Brinkhaus wrote:
> > Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin:
> > >
> > > I mean IPv4 link local addresses 169.254.x.y. My impression is that
> > > avahi-
On Fri 24 Feb 2023 at 19:41:26 (+0100), Christoph Brinkhaus wrote:
> 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
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 forw
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=
On 22/02/2023 19:40, Greg Wooledge wrote:
On Wed, Feb 22, 2023 at 02:04:58PM -0500, Jeffrey Walton wrote:
Maybe the 'w' is not matching anything.
I thought eth0 and wlan0 went the way of the dinosaurs. I thought with
Consistent Network Device Names and biosdevname, the name will begin
with a
On Wed, Feb 22, 2023 at 02:04:58PM -0500, Jeffrey Walton wrote:
> Maybe the 'w' is not matching anything.
>
> I thought eth0 and wlan0 went the way of the dinosaurs. I thought with
> Consistent Network Device Names and biosdevname, the name will begin
> with a 'p' or 'em', not a 'w', and based on
On Wed, Feb 22, 2023 at 1:43 PM David Wright wrote:
>
> On Tue 21 Feb 2023 at 13:48:58 (-0500), Jeffrey Walton wrote:
> > On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> > wrote:
> > > [...]
> > > > But backing up... I suspect there's something wrong with your static
> > > > ip address assi
On Wed 22 Feb 2023 at 17:45:40 (+0100), 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:
> > > > > I have no idea if it is possible to estimate a DHCP response
> > > > > time.
> >
> > Since static IP addr
On Tue 21 Feb 2023 at 13:48:58 (-0500), Jeffrey Walton wrote:
> On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> wrote:
> > [...]
> > > But backing up... I suspect there's something wrong with your static
> > > ip address assignment. The address is already taken, the netmask is
> > > wrong, o
Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> On 22/02/2023 01:26, Christoph Brinkhaus wrote:
> > > > I have no idea if it is possible to estimate a DHCP response
> > > > time.
>
> Since static IP address is assigned, it does not matter. I expected DHCP
> configuration and that d
On 22/02/2023 01:26, Christoph Brinkhaus wrote:
I have no idea if it is possible to estimate a DHCP response
time.
Since static IP address is assigned, it does not matter. I expected DHCP
configuration and that delay may be noticed in `journalctl -b 0` logs.
[Unit]
Description=A remote mail
On Tue, Feb 21, 2023 at 01:48:58PM -0500, Jeffrey Walton wrote:
> On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> wrote:
> > [...]
> > > But backing up... I suspect there's something wrong with your static
> > > ip address assignment. The address is already taken, the netmask is
> > > wrong,
On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
wrote:
> [...]
> > 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 no
Am Tue, Feb 21, 2023 at 01:06:01PM -0500 schrieb Jeffrey Walton:
> On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus
> 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
Hi.
On Tue, Feb 21, 2023 at 06:44:38PM +0100, Christoph Brinkhaus wrote:
> I have no idea if it is possible to estimate a DHCP response time.
sudo nmap --script broadcast-dhcp-discover
Reco
On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus
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
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 Nikulin:
Hello Max,
> > > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly
> > > configure network interfac
On 20/02/2023 21:44, Christoph Brinkhaus wrote:
Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin:
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 tha
On 2023-02-19 at 11:21, Geert Stappers wrote:
> Hi,
>
> Having installed package openvswitch-switch and doing `ip route` I do get
>
> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>
>
> What can be done to prevent that "zeroconf"
> configures interface `ovs-system`?
On Mon, Feb 20, 2023 at 9:28 AM wrote:
>[...]
> --
> rhk
>
> (sig revised 20221206)
>
> If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
> avoid top posting; and keep it "on list". (Oxford comma (and semi-colon)
> included at no charge.) If you revise the topic, change t
Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin:
Hi Max,
> On 19/02/2023 23:35, Christoph Brinkhaus wrote:
> > Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >169.254.0.0/16 dev
On Monday, February 20, 2023 04:05:19 AM to...@tuxteam.de wrote:
> On Mon, Feb 20, 2023 at 02:42:59AM -0500, Jeffrey Walton wrote:
> > On Mon, Feb 20, 2023 at 2:27 AM wrote:
> [...]
>
> > > That's what Microsoft calls them. I prefer the RFC's IP4LL.
> >
> > And Wireshark (https://wiki.wireshark.
On Mon, Feb 20, 2023 at 02:42:59AM -0500, Jeffrey Walton wrote:
> On Mon, Feb 20, 2023 at 2:27 AM wrote:
[...]
> > That's what Microsoft calls them. I prefer the RFC's IP4LL.
>
> And Wireshark (https://wiki.wireshark.org/APIPA.md) and Cisco
> (https://study-ccna.com/apipa-automatic-private-ip-a
On Mon, Feb 20, 2023 at 2:27 AM wrote:
>
> On Mon, Feb 20, 2023 at 12:53:25AM -0500, Jeffrey Walton wrote:
> > On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers
> > wrote:
> > >
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >
> > > 169.254.0.0/16 dev ovs-sys
On Mon, Feb 20, 2023 at 12:53:25AM -0500, Jeffrey Walton wrote:
> On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers wrote:
> >
> > Having installed package openvswitch-switch and doing `ip route` I do get
> >
> > 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>
> Those are
On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers wrote:
>
> Having installed package openvswitch-switch and doing `ip route` I do get
>
> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
Those are called "APIPA's". Automatic Private IP Addressing (APIPA).
The host parts are
On 20/02/2023 01:57, Geert Stappers wrote:
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed
to update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed
to update link state, ignoring: No s
On Mon 20 Feb 2023 at 09:59:20 (+0700), Max Nikulin wrote:
> On 19/02/2023 23:35, Christoph Brinkhaus wrote:
> > Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >169.254.0.0/16 dev ovs-system sc
On 19/02/2023 23:35, Christoph Brinkhaus wrote:
Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
Having installed package openvswitch-switch and doing `ip route` I do get
169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
Please have a look at https://wik
Am Sun, Feb 19, 2023 at 07:57:56PM +0100 schrieb Geert Stappers:
Hi Geert,
> On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote:
> > >> Having installed package openvswitch-switch and doing `ip route` I do get
> > >> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric
On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote:
> >> Having installed package openvswitch-switch and doing `ip route` I do get
> >> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
> >>
> >> What can be done to prevent that "zeroconf"
> >> configures interfa
>> Having installed package openvswitch-switch and doing `ip route` I do get
>> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>>
>> What can be done to prevent that "zeroconf"
>> configures interface `ovs-system`?
>
> Please have a look at https://wiki.debian.org/Avahi.
Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
Hello Geert,
> Having installed package openvswitch-switch and doing `ip route` I do get
> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>
> What can be done to prevent that "zeroconf"
> configures inter
Hi,
Having installed package openvswitch-switch and doing `ip route` I do get
169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
What can be done to prevent that "zeroconf"
configures interface `ovs-system`?
Groeten
Geert Stappers
--
Silence is hard to parse
55 matches
Mail list logo
