I have problem with the interface enp7s0

[Michael De Roover]

Hello,

This could happen for any number of reasons. Make sure to check your wires 
with a cable tester or a multimeter from client to DHCP server (which server 
are you running?), and see if you can communicate with anything else on the 
network using a static IP. During testing, use known good wiring, and try to 
eliminate switches and in-wall patch cables in between. You may also want to 
troubleshoot using Wireshark or tcpdump on both ends.

On Monday, September 16, 2024 4:52:14 AM CEST William Torrez Corea wrote:
> RTNETLINK answers: No such process
> Killed old client process
> Internet Systems Consortium DHCP Client 4.4.3-P1
> Copyright 2004-2022 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/enp7s0/e0:db:55:c2:58:45
> Sending on   LPF/enp7s0/e0:db:55:c2:58:45
> Sending on   Socket/fallback
> DHCPRELEASE of 192.168.1.5 on enp7s0 to 192.168.1.1 port 67
> send_packet: Network is unreachable
> send_packet: please consult README file regarding broadcast address.
> dhclient.c:3124: Failed to send 300 byte long packet over fallback
> interface.
> 
> Internet Systems Consortium DHCP Client 4.4.3-P1
> Copyright 2004-2022 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/enp7s0/e0:db:55:c2:58:45
> Sending on   LPF/enp7s0/e0:db:55:c2:58:45
> Sending on   Socket/fallback
> DHCPDISCOVER on enp7s0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on enp7s0 to 255.255.255.255 port 67 interval 9
> DHCPOFFER of 192.168.1.5 from 192.168.1.1
> DHCPREQUEST for 192.168.1.5 on enp7s0 to 255.255.255.255 port 67
> DHCPACK of 192.168.1.5 from 192.168.1.1
> bound to 192.168.1.5 -- renewal in 36477 seconds.


-- 
Met vriendelijke groet,
Michael De Roover