Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: Destination Host Unreachable (Greg Sloop <gr...@sloop.net>)
2. Re: Script execution failed with return value 2
(glenn.satch...@uniq.com.au)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Sep 2024 21:20:24 -0700
From: "Greg Sloop <gr...@sloop.net>" <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Destination Host Unreachable
Message-ID:
<CAAjorqWa6wQzX4fFmvqcZSeGcd5k8mA5LzNjJbS2M=yaoxp...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Your log shows that no DHCP server responded to the machine the logs came
from and you got an IPIPA 169.x.x.x address. (The 169.x.x.x address is the
address your machine will pick for itself, if no DHCP server responds and
the DHCP request times out.)
Meaning that something is wrong.
1) Either the machine the logs are from is NOT on the network, somehow -
like a patch cable is not plugged in (or damaged), wifi is not joined, or
something similar. Fix your connection to the network and DHCP should work.
or
2) The DHCP server isn't working properly to hand out addresses. This is a
more complicated problem - we'd need a description of how your
network/router/dhcp-server are all connected physically/logically.
But if *other* machines can get on the network and get DHCP addresses (not
a 169.x.x.x address), it's likely #1. (That's my guess - but it's only a
guess.)
On Mon, Sep 2, 2024 at 9:03?PM William Torrez Corea <willitc9...@gmail.com>
wrote:
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> From 169.254.10.244 icmp_seq=1 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=2 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=3 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=4 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=5 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=6 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=7 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=9 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=10 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=11 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=12 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=13 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=14 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=15 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=16 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=17 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=18 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=19 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=20 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=21 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=22 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=23 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=24 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=25 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=26 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=27 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=28 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=29 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=30 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=31 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=32 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=33 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=34 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=35 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=36 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=38 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=39 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=40 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=41 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=42 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=43 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=44 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=45 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=46 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=47 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=48 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=51 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=52 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=53 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=54 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=55 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=56 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=57 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=58 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=59 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=60 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=61 Destination Host Unreachable
> From 169.254.10.244 icmp_seq=62 Destination Host Unreachable
> ^C
> --- 192.168.1.1 ping statistics ---
> 65 packets transmitted, 0 received, +58 errors, 100% packet loss, time
> 65311ms
> pipe 4
>
>
> --
>
> With kindest regards, William.
>
> *Larry Wall invented a messy programming language -- and changed the face
> of the Web*
>
> --
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20240902/94c229c2/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 03 Sep 2024 19:50:31 +1000
From: glenn.satch...@uniq.com.au
To: William Torrez Corea <willitc9...@gmail.com>
Cc: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Script execution failed with return value 2
Message-ID: <9a94b86afad1cae55beeefd0c6023...@uniq.com.au>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 2024-09-03 13:27, William Torrez Corea wrote:
> On Sun, Sep 1, 2024 at 11:39?PM <glenn.satch...@uniq.com.au> wrote:
>
> With _systemctl status whatever.service_ you can also do _journalctl
> -xeu whatever.service_ and get the full status and error messages.
> Otherwise you just get the last 10 or so lines which isn't always the
> interesting or useful part.
>
> regards,
>
> Glenn
>
> On 2024-09-02 15:04, William Torrez Corea wrote:
>
> networking.service - Raise network interfaces
> --
>
> With kindest regards, William.
>
> _Larry Wall invented a messy programming language -- and changed the
> face of the Web_
>
> --
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
Sep 02 20:52:55 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on
enp7s0 to 255.255.255.255 port 67 interval 2
Sep 02 20:52:55 lulu-inspiron5437 ifup[4434]: DHCPDISCOVER on enp7s0 to
255.255.255.255 port 67 interval 2
Sep 02 20:52:57 lulu-inspiron5437 dhclient[4434]: No DHCPOFFERS
received.
Sep 02 20:52:57 lulu-inspiron5437 ifup[4434]: No DHCPOFFERS received.
Sep 02 20:52:57 lulu-inspiron5437 ifup[4434]: No working leases in
persistent database - sleeping.
Sep 02 20:52:57 lulu-inspiron5437 dhclient[4434]: No working leases in
persistent database - sleeping.
Sep 02 20:52:57 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]: Found
user 'avahi-autoipd' (UID 107) and group 'avahi-autoipd' (GID 11>
Sep 02 20:52:57 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]:
Successfully called chroot().
Sep 02 20:52:57 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]:
Successfully dropped root privileges.
Sep 02 20:52:57 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]: Starting
with address 169.254.10.244
Sep 02 20:53:03 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]: Callout
BIND, address 169.254.10.244 on interface enp7s0
Sep 02 20:53:07 lulu-inspiron5437 avahi-autoipd(enp7s0)[4889]:
Successfully claimed IP address 169.254.10.244
Sep 02 20:53:07 lulu-inspiron5437 systemd[1]: Finished
networking.service - Raise network interfaces.
?? Subject: A start job for unit networking.service has finished
successfully
?? Defined-By: systemd
?? Support: https://www.debian.org/support
??
?? A start job for unit networking.service has finished successfully.
??
?? The job identifier is 1878.
Sep 02 21:00:04 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on enp7s0
to 255.255.255.255 port 67 interval 4
Sep 02 21:00:08 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on enp7s0
to 255.255.255.255 port 67 interval 10
Sep 02 21:00:18 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on enp7s0
to 255.255.255.255 port 67 interval 19
Sep 02 21:00:37 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on enp7s0
to 255.255.255.255 port 67 interval 20
Sep 02 21:00:57 lulu-inspiron5437 dhclient[4434]: DHCPDISCOVER on enp7s0
to 255.255.255.255 port 67 interval 8
Sep 02 21:01:05 lulu-inspiron5437 dhclient[4434]: No DHCPOFFERS
received.
Sep 02 21:01:05 lulu-inspiron5437 dhclient[4434]: No working leases in
persistent database - sleeping.
--
With kindest regards, William.
_Larry Wall invented a messy programming language -- and changed the
face of the Web_
Hi WIlliam,
Looks like there isn't a DHCP server on that network, or it's not
plugged in to the switch properly? Do you have a server or wifi router
or something that should be serving up DHCP? Anything in the log files
fon the server? Are there other systems on that network segment that are
working?
regards,
Glenn
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20240903/b2fb7343/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 189, Issue 4
******************************************
