On 12/08/2020 18:50, Mike Pumford wrote:
On 12/08/2020 18:29, Roy Marples wrote:
Maybe some other process is listening on the bootpc port?
If you stop dhcpcd and do `netstat -laf inet | grep bootpc` is anything listed?
That command produced no output when dhcpdc was stopped.
When dhcpcd is
On 12/08/2020 18:29, Roy Marples wrote:
Maybe some other process is listening on the bootpc port?
If you stop dhcpcd and do `netstat -laf inet | grep bootpc` is anything
listed?
That command produced no output when dhcpdc was stopped.
When dhcpcd is running I see the following from that
On 12/08/2020 17:27, Mike Pumford wrote:
On 12/08/2020 17:04, Roy Marples wrote:
Interesting. You can post the output of `ps ax | grep dhcpcd` please?
12897 ? Is 0:00.75 dhcpcd: [master] [ip4] [ip6]
During all the IPv4 requests the IPv6 logic worked perfectly. I didn't see any
wm
On 12/08/2020 17:04, Roy Marples wrote:
Interesting. You can post the output of `ps ax | grep dhcpcd` please?
12897 ? Is 0:00.75 dhcpcd: [master] [ip4] [ip6]
During all the IPv4 requests the IPv6 logic worked perfectly. I didn't
see any wm link events in the debug log and I can
On 12/08/2020 13:43, Mike Pumford wrote:
On 11/08/2020 21:14, Mike Pumford wrote:
Aug 11 21:09:55 trigati dhcpcd[12897]: wm0: sending REQUEST (xid 0xc8152c37),
next in 64.3 seconds
Aug 11 21:11:00 trigati dhcpcd[12897]: wm0: sending REQUEST (xid 0xc8152c37),
next in 64.0 seconds
This
On 11/08/2020 21:14, Mike Pumford wrote:
Aug 11 21:09:55 trigati dhcpcd[12897]: wm0: sending REQUEST (xid
0xc8152c37), next in 64.3 seconds
Aug 11 21:11:00 trigati dhcpcd[12897]: wm0: sending REQUEST (xid
0xc8152c37), next in 64.0 seconds
This cycle was finally stopped by this:
Aug 12
On 10/08/2020 12:49, Roy Marples wrote:
On 10/08/2020 12:00, Mike Pumford wrote:
I've also noticed its intermittent. So its clearly being triggered by
some network activity.
dhcpcd will renew if the carrier goes down/up or you issue `dhcpcd -n`
on the command line. Those are the only early
On 10/08/2020 12:00, Mike Pumford wrote:
I've also noticed its intermittent. So its clearly being triggered by some
network activity.
dhcpcd will renew if the carrier goes down/up or you issue `dhcpcd -n` on the
command line. Those are the only early triggers.
Roy
On 10/08/2020 11:19, Roy Marples wrote:
Hi Mike
Anything I need to look at to help with debugging this?
You could start by adding the debug directive to dhcpcd.conf and
restarting dhcpcd.
Then examine syslog and see why it's refreshing so quickly - all the
reasons should be logged.
Hi Mike
On 07/08/2020 17:03, Mike Pumford wrote:
Running 9.0-STABLE buit July 26th.
Machine is refreshing its least approximately once a minute. Despite the DHCP
server being configured with a lease time as follows:
max-lease-time 43200;
default-lease-time 43200;
Server is NetBSD 8.2-STABLE
Running 9.0-STABLE buit July 26th.
Machine is refreshing its least approximately once a minute. Despite the
DHCP server being configured with a lease time as follows:
max-lease-time 43200;
default-lease-time 43200;
Server is NetBSD 8.2-STABLE isc dhcpd and this is the only host of many
on
11 matches
Mail list logo
