Internet Systems Consortium DHCP Client

Forum › Forums › New users › New Users and General Questions › Internet Systems Consortium DHCP Client

Tagged: 

  • This topic has 3 replies, 2 voices, and was last updated Oct 1-9:26 am by Anonymous.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • September 30, 2020 at 6:53 pm #42385
    Member
    rayluo

      Part 1

      Recently I created a new antiX 19.2 64bit LiveUSB flash drive to boot my computers. The boot time was longer than usual, and I notice that there is an extra “Internet Systems Consortium DHCP” step during boot.

      
[ ok ] Setting up resolvconf...done.
[ ok ] Skip starting firewall: ufu (not enabled)...done.
[....] Configuring network interfaces in background...Internet Systems Consortium DHCP Client 4.4.1
Copuright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/f0:de: f1:1e:12:7b
Sending on   LPF/eth0/f0:de: f1:1e:12:7b
Sending on   Socket/fallback
Created duid "\000\001\000\001'\007\3261\360\336\361\036\822(".
DHCPDISCOVER on ethe to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ethe to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ethe to 255,255.255.255 port 67 interval 19

      It won’t discover anything, and eventually it will proceed to the rest of the boot process, and everything will be fine. But it consumes some 20~30 extra seconds during each boot, for nothing.

      Q1: Any idea where this “Internet Systems Consortium DHCP Client” step comes from, and how can I disable it?

      Part 2

      I have another LiveUSB drive that was created months ago. It works just fine, without such new extra “Consortium DHCP Client” thing. The 2 LiveUSB drives were most likely created with SAME iso snapshot, although I am not entirely sure, because it has been months between them. So,

      Q2: How do I know for sure that which version of antiX my LiveUSB was using?

      I tried getting the “full info” from “Control Centre -> Hardware -> PC Information”, and they both output same System information: “Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 … Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020

      September 30, 2020 at 7:22 pm #42387
      Anonymous
        Helpful
        Up
        0
        ::

        I have no guess as to how one (and not the other) wound up behaving differently, but editing the “timeout” value within /etc/dhcp/dhclient.conf may solve the delay.
        https://manpages.debian.org/testing/isc-dhcp-client/dhclient.conf.5.en.html

        How do I know for sure that which version of antiX my LiveUSB was using?

        In the top level directory of the liveUSB, a file named “version” contains details
        (I can’t recall whether that ever gets changed, i.e. if you perform a remaster operation)

        Also, you can mount the rootfs and
        $ cat //path_to///var/log/live/initrd.log | grep Welcome
        $ cat //path_to//etc/lsb-release

        October 1, 2020 at 5:09 am #42412
        Member
        rayluo
          Helpful
          Up
          0
          ::
          Anonymous wrote:

          In the top level directory of the liveUSB, a file named “version” contains details
          (I can’t recall whether that ever gets changed, i.e. if you perform a remaster operation)

          Perhaps the recent LiveUSB has been changed to NOT contain that version file anymore? This is a newly created LiveUSB.

          
demo@antix1:/media/demo/Live-usb$ ls -ltra
total 44
-rw-r--r--  1 root root   894 Oct 10  2019 cdrom.ico
drwx------  2 root root 16384 Oct  1 03:21 lost+found
drwxr-xr-x  6 root root  4096 Oct  1 03:31 boot
drwxr-xr-x  2 root root  4096 Oct  1 03:31 antix19-2-x64-full-gvmcf
drwxr-xr-x  3 root root  4096 Oct  1 03:31 EFI
-rw-r--r--  1 root root   122 Oct  1 03:31 made-by-live-usb-maker
drwxr-xr-x  2 root root  4096 Oct  1 03:31 antiX
drwxr-xr-x  7 root root  4096 Oct  1 03:31 .
drwxr-x---+ 5 root root   100 Oct  1 03:33 ..
          Anonymous wrote:

          Also, you can mount the rootfs and
          $ cat //path_to///var/log/live/initrd.log | grep Welcome
          $ cat //path_to//etc/lsb-release

          I found no rootfs from the newly created LiveUSB. I think that file would only exist when I start to use this LiveUSB (and when/if I also enable root persistence). But, if you just hinted to do “grep Welcome /var/log/live/initrd.log” and “cat /etc/lsb-release”, I can do that when the LiveUSB is booted normally. They are all “antiX 19.2 (Hannie Schaft) 64-bit”. Even the “/Live-usb/antix…(my_iso_file_name)…/package_list” contains exact same content.

          Now the funny part. My newly created LiveUSB (i.e. the 3rd one) does not (currently?) have that “Internet Systems Consortium DHCP Client” thing during the boot process. So, I still don’t know why my 2nd LiveUSB behaves differently, I’ll revisit this if my 3rd LiveUSB develop same symptom again. Thanks for your time!

          October 1, 2020 at 9:26 am #42431
          Anonymous
            Helpful
            Up
            0
            ::

            skidoo wrote:

            Also, you can mount the rootfs linuxfs and
            $ cat //path_to///var/log/live/initrd.log | grep Welcome
            $ cat //path_to//etc/lsb-release

            oops, I should have typed “linuxfs”

            [no “version” file]
            Hmm, timestamp here shows that it was written at the same time as all the other file in the liveboot directory.

            Okay, here’s a file which should certainly be present & accessible just by mounting the drive:
            /dev/sdb1/boot/syslinux/syslinux.cfg

          • Author
            Posts
          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.