Control: forwarded -1 https://github.com/systemd/systemd/issues/20358
Am 01.08.21 um 11:13 schrieb Dirk Heinrichs:
Sorry for the delay, I always forgot to do it. It's finally there now:
https://github.com/systemd/systemd/issues/20358
Thanks, marking it accordingly.
OpenPGP_signature
Descri
Michael Biebl:
> On Wed, 25 Nov 2020 03:27:20 +0100 Michael Biebl
> wrote:
>> If it's still reproducible, can you raise this upstream please at
>> https://github.com/systemd/systemd/issues
> Any updates here?
Sorry for the delay, I always forgot to do it. It's finally there now:
https://github.
On Wed, 25 Nov 2020 03:27:20 +0100 Michael Biebl wrote:
> If it's still reproducible, can you raise this upstream please at
> https://github.com/systemd/systemd/issues
>
Any updates here?
signature.asc
Description: This is a digitally signed message part
If it's still reproducible, can you raise this upstream please at
https://github.com/systemd/systemd/issues
Regards,
Michael
Am 01.02.20 um 07:28 schrieb Michael Biebl:
> Did you find time to reproduce the issue with v244?
Yes, finally. Sorry for the long delay.
> does it work for you? It seems to work for me at least using 244.1
Unfortunately not. I still see the same behavior in Python.
socket.getfqdn() still returns
Am 01.02.20 um 07:28 schrieb Michael Biebl:
Did you find time to reproduce the issue with v244?
No, sorry. And I won't for at least another week.
Bye...
Dirk
--
Dirk Heinrichs
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.
Is this happening for arbitrary hosts or only the hostname?
Taking my simple setup as an example, where my DNS server is a FRITZ.Box
pluto is my hostname
michael@pluto:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.con
On Tue, 31 Dec 2019 08:41:04 +0100 Dirk Heinrichs
wrote:
> Michael Biebl:
>
> > I've uploaded v244 to buster-backports so you should be able to test if
> > you can still reproduce the problem there.
>
> Great, thanks a lot, will do. I've also meanwhile tested this in an Arch
> Linux Container a
Michael Biebl:
I've uploaded v244 to buster-backports so you should be able to test if
you can still reproduce the problem there.
Great, thanks a lot, will do. I've also meanwhile tested this in an Arch
Linux Container and it shows the same behaviour. However, it seems I was
somehow wrong re
Am 29.12.19 um 16:00 schrieb Dirk Heinrichs:
>> It probably makes sense to involve upstream at this point and file a
>> corresponding bug report at
>> https://github.com/systemd/systemd/issues
>
> Wanted to do that first, but it stated: "Bother your distribution if
> your systemd version is more
Oh, btw: I've meanwhile also tried with libnss-resolve, but that didn't
help either. It's also not used on the working system (with
Network-Manager).
Bye...
Dirk
--
Dirk Heinrichs
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retros
Michael Biebl:
How would I create that (the former)?
https://www.cyberciti.biz/faq/linux-unix-dhcpdump-monitor-dhcp-traffic/
Ah, OK. That's nice and clean. I guess it needs to be done on the
client, right? So here we go (attached).
It probably makes sense to involve upstream at this point
Am 29.12.19 um 14:56 schrieb Dirk Heinrichs:
> Michael Biebl:
>
>> Are you aware of the "UseDomain=" option (see man systemd.network)?
>
> Yes, tried it already.
>
>> Does it help if you set that option?
>
> No, unfortunately not.
>
>> If not, we probably need a dump of the DHCP requests and a
Michael Biebl:
Are you aware of the "UseDomain=" option (see man systemd.network)?
Yes, tried it already.
Does it help if you set that option?
No, unfortunately not.
If not, we probably need a dump of the DHCP requests and a verbose debug
log of systemd-networkd.
How would I create tha
Am 29.12.19 um 14:12 schrieb Dirk Heinrichs:
> Michael Biebl:
>
>> not quite sure what you mean by "domain" entry.
>
> "domain example.com"
>
>> Can you post a (full copy of a) working/non-working /etc/resolv.conf?
>
> Working:
>
> nameserver
> search
> domain
>
> Non-Worki
Michael Biebl:
not quite sure what you mean by "domain" entry.
"domain example.com"
Can you post a (full copy of a) working/non-working /etc/resolv.conf?
Working:
nameserver
search
domain
Non-Working (as created automatically by systemd-resolved):
Control: tags -1 + moreinfo
Am 29.12.19 um 11:41 schrieb Dirk Heinrichs:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: normal
> Tags: upstream
>
> Hi,
>
> first, a short description of the overall setup: A private (aka home) network
> using Samba AD with ISC DHCP for network management
Processing control commands:
> tags -1 + moreinfo
Bug #947688 [systemd] systemd-networkd: Python socket.getfqdn() not working
properly when resolv.conf lacks "domain" key
Added tag(s) moreinfo.
--
947688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947688
Debian Bug Tracking System
Contac
This might be related/similar to #859092, but I'm not sure, so I opened
this one.
Bye...
Dirk
--
Dirk Heinrichs
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de
Package: systemd
Version: 241-7~deb10u2
Severity: normal
Tags: upstream
Hi,
first, a short description of the overall setup: A private (aka home) network
using Samba AD with ISC DHCP for network management and setup. All machines run
up-to-date Debian 10 (buster). I mainly run two types of machin
20 matches
Mail list logo