Hi everybody,
this email is for discussing MACAddressPolicy=persistent in
/data/src/systemd/network/99-default.link
there is a Fedora CoreOS issue about this:
[1] https://github.com/coreos/fedora-coreos-tracker/issues/919
Since systemd 242 (Apr 2019), this policy applies to more device types
Hi Peter,
is there a reason why do you want resolved to serve whole LAN? It has
its problems and I think its authors meant it as localhost cache. I
don't think resolved considers it common to have more than one DNS
server on the localhost.
Is there a reason why you wouldn't use dnsmasq, unbound
> use DNSStubListenerExtra=
It's indeed this directive I'm using on the downstream interface. Maybe
I should have mentioned that.
Configuration / results (MACs etc. obfuscated, but all correct on the
running system):
# head -n-0 /etc/systemd/network/linux-dummy_local0.{netdev,network}
==>
On So, 08.05.22 15:00, Peter Mattern (pmatt...@arcor.de) wrote:
> Hello.
>
> Apparently resolved is ignoring DNS servers which are listening on Linux
> dummy interfaces.
It should not do that. Are you sure you configured the interfaces
properly, and they are up?
Provide "networkctl status"
Hi, Petr.
> Do you need any systemd-resolved specific features?
Primarily, it's about the way directive Domains allows for directing
queries to particular DNS servers based on the queries' domains.
I'm using it to restrict the ISP's DNS server to the ISP's domain, use a
local DNS server for
On Mo, 09.05.22 15:32, Lennart Poettering (lenn...@poettering.net) wrote:
> On So, 08.05.22 15:00, Peter Mattern (pmatt...@arcor.de) wrote:
>
> > Hello.
> >
> > Apparently resolved is ignoring DNS servers which are listening on Linux
> > dummy interfaces.
>
> It should not do that. Are you sure
Lennart Poettering writes:
> On So, 08.05.22 19:19, Kamil Jońca (kjo...@op.pl) wrote:
>
>> I have question about custom options in network interface definitions
>> and passing it via command line.
>> In currend Debian tools
>>
>> (https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html)
On Mon, May 9, 2022 at 10:30 AM Lennart Poettering
wrote:
>
> On Fr, 06.05.22 10:12, Wols Lists (antli...@youngman.org.uk) wrote:
>
> > On 27/04/2022 14:53, Lennart Poettering wrote:
> > > I think we systematically disagree on one point here: I am pretty sure
> > > picking a boot loader is
On Mon, May 9, 2022, 16:35 Peter Mattern wrote:
> Hi, Petr.
>
> > Do you need any systemd-resolved specific features?
> Primarily, it's about the way directive Domains allows for directing
> queries to particular DNS servers based on the queries' domains.
> I'm using it to restrict the ISP's
On So, 08.05.22 19:19, Kamil Jońca (kjo...@op.pl) wrote:
> I have question about custom options in network interface definitions
> and passing it via command line.
> In currend Debian tools
>
> (https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html)
> there is a possibility to define
On Mo, 09.05.22 11:23, Thomas Haller (thal...@redhat.com) wrote:
> Hi everybody,
>
> this email is for discussing MACAddressPolicy=persistent in
> /data/src/systemd/network/99-default.link
I think this would be better discussed on a new github issue, as
suggested here:
On Fr, 06.05.22 10:12, Wols Lists (antli...@youngman.org.uk) wrote:
> On 27/04/2022 14:53, Lennart Poettering wrote:
> > I think we systematically disagree on one point here: I am pretty sure
> > picking a boot loader is genuinely someting a distro should be doing,
> > and not the admin really. I
On Mo, 09.05.22 10:35, Neal Gompa (ngomp...@gmail.com) wrote:
> > I am pretty sure the answer to this is not to make choice of boot
> > loaders configurable, but making them adhere to a common definition
> > how boot menu entries are defined, so that it doesn't matter which
> > boot loader you
On Mo, 09.05.22 16:13, Kamil Jońca (kjo...@op.pl) wrote:
> >> (https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html)
> >> there is a possibility to define custom option and passing it to up/down
> >> script (see ENVIRONMENT VARIABLES section)
> >> Is it possible in *.network files?
>
Lennart Poettering writes:
[...]
>>
>> I am afraid you will not cover all cases with networking.
>
> Well, I am not sure. I am pretty sure there are almost always better
> ways to fix the issues that people address with network callout stuff.
I cannot discuss with your conviction.
For now I do
Kamil Jońca writes:
> Let's see.
> from SYSTEMD.NETWORK(5)
> ...
> IPMasquerade=
>Configures IP masquerading for the network interface. If
>enabled, packets forwarded from the network interface will be
>appear as coming from the local host.
>
>
>
> I
On Mon, May 09, 2022 at 03:57:21PM +0200, Lennart Poettering wrote:
> On Mo, 09.05.22 11:23, Thomas Haller (thal...@redhat.com) wrote:
>
> > Hi everybody,
> >
> > this email is for discussing MACAddressPolicy=persistent in
> > /data/src/systemd/network/99-default.link
>
> I think this would be
On Mo, 09.05.22 18:12, Kamil Jońca (kjo...@op.pl) wrote:
> For now I do not know how handle multiple interface where:
> 1. set routing according to classles routes from dhcp on some
> interfaces.
We don't do that anyway?
> 2. set NAT (ie call nftables sctipts) with multitple egress interfaces
Hi Andrei,
Thanks for the suggestion. It becomes more verbose, but it still seems
like `systemd` fails to notice that `gnome-keyring` exited:
May 09 17:52:47 cb6d1c84f84e systemd[106]: gnome-keyring.service:
Passing 0 fds to service
May 09 17:52:47 cb6d1c84f84e systemd[106]:
(sent previously from different address)
Lennart Poettering writes:
> On Mo, 09.05.22 18:12, Kamil Jońca (kjo...@op.pl) wrote:
>
>> For now I do not know how handle multiple interface where:
>> 1. set routing according to classles routes from dhcp on some
>> interfaces.
>
> We don't do that
On 09.05.2022 23:43, Yuri Kanivetsky wrote:
> Hi Andrei,
>
> Thanks for the suggestion. It becomes more verbose, but it still seems
> like `systemd` fails to notice that `gnome-keyring` exited:
>
Probably
...
>
> The child exits:
>
> May 09 17:52:47 cb6d1c84f84e
The one that produces the messages is 249.11 (that is running in a
docker container):
https://packages.ubuntu.com/jammy/systemd
The one running on the host is 215-17 (Debian 8).
> But it sounds like systemd issue in one specific version you are using.
On hosts with newer Debians the issue
On 5/9/22 13:27, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, May 09, 2022 at 03:57:21PM +0200, Lennart Poettering wrote:
>> On Mo, 09.05.22 11:23, Thomas Haller (thal...@redhat.com) wrote:
>>
>>> Hi everybody,
>>>
>>> this email is for discussing MACAddressPolicy=persistent in
>>>
23 matches
Mail list logo
