I shutdown ConnMan and ran dhclient and here is the lease file.

It would also be interesting to see what command line parameters dhclient is using. Post the output of the command:
ps ax | grep dhclient

Attached Files

lease.txt (426 Bytes, 15 views)

Unless you have a special use case i.e. you trying to segment out your network for certain use cases like a home lab situation. In most cases, it is recommended that someone who doesn't know what they're doing not try to alter the setting that your router manufacturer ships the device, and if you do just make sure that you use the firmware backup function of your device I'd also recommend that the OP start doing their research most every router manufacturer may even have user to user support communities.

I specifically used that to install in two computers.
https://cdimage.debian.org/debian-cd...64/iso-hybrid/
and then chose this:
[ISO] debian-live-12.4.0-amd64-lxqt.iso



(these setups/logs are AFTER i have made changes to dhclient.conf)
ps ax | grep dhclient

936 ? Ss 0:00 dhclient -4 -v -i -pf /run/dhclient.enp3s0.pid -lf /var/lib/dhcp/dhclient.enp3s0.leases -I -df /var/lib/dhcp/dhclient6.enp3s0.leases enp3s0
803999 pts/1 S+ 0:00 grep dhclient




cat /var/lib/dhcp/dhclient.enp3s0.leases
default-duid "\000\001\000\001,\004^\355tV<?\007\037";
lease {
interface "enp3s0";
fixed-address 192........;
option subnet-mask 255.255.255.0;
option routers 192........;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192........;
option dhcp-server-identifier 192........;
option host-name "elme";
option domain-name "station";
renew 3 2024/01/03 20:54:32;
rebind 3 2024/01/03 20:54:32;
expire 3 2024/01/03 20:54:32;
}
lease {
interface "enp3s0";
fixed-address 192........;
option subnet-mask 255.255.255.0;
option routers 192.........;;
option dhcp-lease-time 864000;
option dhcp-message-type 5;
option domain-name-servers 192.........;;
option dhcp-server-identifier 192.........;;
option dhcp-renewal-time 432000;
option ntp-servers 192........;
option broadcast-address 192.........;
option dhcp-rebinding-time 756000;
option host-name "elme";
option domain-name "station";
renew 1 2024/01/08 22:58:06;
rebind 6 2024/01/13 09:36:09;
expire 0 2024/01/14 15:36:09;
}

in my processes, i found both

`connmand -n` and `device -4 -v -i -pf ....dhclient.enp3s0.pid -lf ...dhclient.enp3s0.leases -I -df .....dhclient.enp3s0.leases`

In my surprise, somehow, .xauthority got the central machine name given by router, again ("easy")!

cat .Xauthority
elme1MIT-MAGIC-COOKIE-1h���C_�W�,L�b��easy0MIT-MAGIC-COOKIE-1"y�"�X9���&�_��easy0MIT-MAGIC-COOKIE-1"y�"�X9���&�_��elme0MIT-MAGIC-COOKIE-1y����F8��߷����(base)"


I make it clear: I have not make any special adjustment to router or config files of debian live installation before this problem occur.rooter came preconfigured by the company (50mbs line)

I used the same ISO but I forgot to mention that I selected the full desktop install (I forgot the exact words) at first boot. In the files I posted the host name was not changed from what I had entered during the install nor did my DHCP server send a random host name to the client with either connman or dhclient. I did not use a specific dhclient.conf file.

Yes, i did full desktop install too. So, I dont know what to say. It may be user-specific case for me triggered from something? Whatever, i think i cant add any useful additional information. we may close this thread.

Try 'xauth list'.

There is something about the setting in the image you posted that has the value easy.box. I don't know it what it exactly means except for maybe a local domain name. You might want to ask your ISP.

Otherwise, yes the thread can be marked as solved using the thread tools pull down menu at the top.