On 07/05/2019 19:36, John D. Baker wrote:
On Sat, 4 May 2019, Roy Marples wrote:
I've imported dhcpcd-7.2.2 which fixes this issue.
After the pullup to netbsd-8 I ran a CVS update, built releases and
updated my systems. The NAT router has been working fine and the sparc
box booting from
On Sat, 4 May 2019, Roy Marples wrote:
> I've imported dhcpcd-7.2.2 which fixes this issue.
After the pullup to netbsd-8 I ran a CVS update, built releases and
updated my systems. The NAT router has been working fine and the sparc
box booting from local disk configures "le0" without needing any
On 01/05/2019 13:55, John D. Baker wrote:
On Wed, 1 May 2019, Roy Marples wrote:
On 01/05/2019 03:44, John D. Baker wrote:
I've now tried it and it works as expected.
OK, this might be tricky to solve.
Can I get the output of route montior captured during early boot please?
To be clear,
On 01/05/2019 13:55, John D. Baker wrote:
On Wed, 1 May 2019, Roy Marples wrote:
On 01/05/2019 03:44, John D. Baker wrote:
I've now tried it and it works as expected.
OK, this might be tricky to solve.
Can I get the output of route montior captured during early boot please?
To be clear,
On 01/05/2019 13:55, John D. Baker wrote:
On Wed, 1 May 2019, Roy Marples wrote:
On 01/05/2019 03:44, John D. Baker wrote:
I've now tried it and it works as expected.
OK, this might be tricky to solve.
Can I get the output of route montior captured during early boot please?
To be clear,
On Wed, 1 May 2019, Roy Marples wrote:
> On 01/05/2019 03:44, John D. Baker wrote:
>
> > I've now tried it and it works as expected.
>
> OK, this might be tricky to solve.
> Can I get the output of route montior captured during early boot please?
To be clear, your asking about a 'dhcpcd' binary
On 01/05/2019 03:44, John D. Baker wrote:
On Tue, 30 Apr 2019, John D. Baker wrote:
On Tue, 30 Apr 2019, Roy Marples wrote:
As to the need to bring the interface up, can you try reverting this
commit please?
On Tue, 30 Apr 2019, John D. Baker wrote:
> On Tue, 30 Apr 2019, Roy Marples wrote:
>
> > As to the need to bring the interface up, can you try reverting this
> > commit please?
> > https://roy.marples.name/git/dhcpcd.git/commit/?h=dhcpcd-7=4f903d6ad4adf2de7712d36a921051b4dfd7210a
> I've
On Tue, 30 Apr 2019, Roy Marples wrote:
> As to the need to bring the interface up, can you try reverting this
> commit please?
> https://roy.marples.name/git/dhcpcd.git/commit/?h=dhcpcd-7=4f903d6ad4adf2de7712d36a921051b4dfd7210a
>
> I've had a similar report from an OpenBSD user that reverting
On Mon, 29 Apr 2019, Roy Marples wrote:
> This patch should help.
> Let me know!
After rebuilding with this patch and updating the router, it's remained
up for the last 4 hours which is much longer than before. Looks
promising.
--
|/"\ John D. Baker, KN5UKS NetBSD
Hi John.
It seems I didn't test this thoroughly enough as I was pressed with an
urgent matter with getting a new release in and I do appologise for that :(
This patch should help.
Let me know!
Roy
diff --git a/src/dhcp.c b/src/dhcp.c
index f24d14f6..8291dd23 100644
--- a/src/dhcp.c
+++
Also, a behavior change on "sparc", although possibly on other ports.
When booting from disk, 'dhcpcd' reports "timed out" configuring "le0".
When net-booting with NFS root, it doesn't have a problem.
For local-disk boot I need to explicitly mark the interface "UP" before
calling 'dhcpcd'. My
On Mon, 29 Apr 2019, John D. Baker wrote:
> Analysing it may be tricky as I'll have to use the cross-gdb on the
> build host and point to the corresponding debug symbols in the
> build DESTDIR.
The timestamp on the core file seems to be just before it was next due
to renew the lease. Loading a
On Mon, 29 Apr 2019, John D. Baker wrote:
> It appears that after a few hours 'dhcpcd' stops RENEWing the lease so
> it expires, leaving the IP address and default route in place. This
It appears that 'dhcpcd' is crashing. I finally remembered to look and
there is a "dhcpcd.core" file in the
Following the recent pull-up of the latest 'dhcpcd' to netbsd-8, I updated,
build a release, and updated my NAT router.
Since then, I lose network connectivity after a few hours.
'dhcpcd' seems to log very little but I have "/etc/dhcpcd.exit-hook" log
the "REASON" every time it is called.
It
15 matches
Mail list logo
