-
Notifications
You must be signed in to change notification settings - Fork 726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DHCP renew drops connection - OPNsense Version 24.1_1 #7191
Comments
Hi @Dperrigo18, The log is not complete. I'm specifically missing things from dhclient/dhclient-script here to make sense of it. Cheers, |
Sorry about that.
|
Working with my ISP this is the information they provided and the issue has stopped since they implemented a fix.
|
This issue has been automatically timed-out (after 180 days of inactivity). For more information about the policies for this repository, If someone wants to step up and work on this issue, |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
#6869
The issues are the same as in issue 6869.
Suddenly whenever the WAN IP is supposed to renew the connection drops because the default gateway disappears.
It was advised to open a new bug for version 24.1_1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected lease to renew and not drop packages.
Describe alternatives you considered
A clear and concise description of any alternative solutions or workaround you considered.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
Here are the logs from when the renewal starts to when it finishes.
The new and old addresses are the same but it still drops the route for a second.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1_1-amd64
FreeBSD 13.2-RELEASE-p9
OpenSSL 3.0.12
Intel(R) Celeron(R) J4125 CPU @ 2.00GHz (4 cores, 4 threads)
Intel Corporation Ethernet Controller I225-V (rev 03)
The text was updated successfully, but these errors were encountered: