Skip to content
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

dhcp6c: Config not rewritten when interfaces added after the first. #3406

Closed
lrosenman opened this issue Apr 11, 2019 · 15 comments
Closed

dhcp6c: Config not rewritten when interfaces added after the first. #3406

lrosenman opened this issue Apr 11, 2019 · 15 comments
Assignees
Labels
bug Production bug
Milestone

Comments

@lrosenman
Copy link
Contributor

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

[x] I have searched the existing issues and I'm convinced that mine is new.

Describe the bug
Can't add 2nd-nth tracking interface
To Reproduce
Steps to reproduce the behavior:
Have an existing WAN connection with PD
Have an existing LAN connection tracking WAN (prefix id 0)
add another interface (of any flavor)
set to IPv6 Track Wan / Prefix id 1
set it to allow modifying DHCPD/RA

Expected behavior
prefix-interface stanza added to /var/etc/dhcp6c_.conf
restart dhcp6c
Screenshots
If applicable, add screenshots to help explain your problem.

Relevant log files
If applicable, information from log files supporting your claim.

Additional context
Add any other context about the problem here.

Environment
Software version used and hardware type if relevant.
e.g.:

OPNsense 19.1.6 (amd64, OpenSSL).
Intel® i3-7100U Quad Core
Network Intel® 82583V

@lrosenman
Copy link
Contributor Author

Anyone?

@fichtner
Copy link
Member

Nice spot, can you try this patch?

# opnsense-patch 88c5ffa

Cheers,
Franco

fichtner added a commit that referenced this issue Apr 22, 2019
@fichtner fichtner self-assigned this Apr 22, 2019
@fichtner fichtner added the bug Production bug label Apr 22, 2019
@fichtner fichtner added this to the 19.7 milestone Apr 22, 2019
@fichtner
Copy link
Member

Deconfigure now works as expected too. There's still an older bug that I'd like to address before closing: checking wether the same prefix ID is already used.

@fichtner
Copy link
Member

@lrosenman Thanks for the report and sorry for the delay ❤️

@lrosenman
Copy link
Contributor Author

How can I get all the commits on a 19.1.x release/box/etc?

@fichtner
Copy link
Member

@lrosenman let's discuss here about schedule. I can't promise it for 19.1.7 but I can make a single-patch backport for on top of 19.1.6 if you want to test?

@lrosenman
Copy link
Contributor Author

I'd love that and WILL test :)

@fichtner
Copy link
Member

Okay, great! It's 81ca8c9 for both tickets. Apply and subsequently remove by running the same command below:

# opnsense-patch 81ca8c9

@fichtner
Copy link
Member

PS: I don't always have time to respond quickly, but GitHub is indeed the best and quickest way do discuss issues, patches, solutions and release schedules. Closing tickets is just for recording issues as done in the roadmap item "19.7". Ping still works reliably afterwards :)

@lrosenman
Copy link
Contributor Author

Deleting the interface should cause a rewrite as well, and does NOT at the moment with the above patch.

@lrosenman
Copy link
Contributor Author

the rest looks great!

@fichtner
Copy link
Member

@lrosenman nice, thanks a lot. I have an idea about deletion. Will patch tomorrow and follow-up.

@fichtner fichtner reopened this Apr 22, 2019
fichtner added a commit that referenced this issue Apr 23, 2019
Which in the case of track6 disables the new deconfiguration process.
@fichtner
Copy link
Member

7ff838c on top should do the trick:

# opnsense-patch 7ff838cac

I think I can shortcut these to 19.1.7 with the help of your testing. I just have to make sure my office setup likes this as well. Due to the Easter holidays couldn't deploy it there yet but will do it on Thursday.

fichtner added a commit that referenced this issue Apr 23, 2019
@lrosenman
Copy link
Contributor Author

Confirmed it now does the right thing here. Thanks!

@fichtner
Copy link
Member

@lrosenman great, thanks for your help!

fichtner added a commit that referenced this issue Apr 23, 2019
(cherry picked from commit 98e9a3ef34c0719b0767471f9b5f6d071c142030)
fichtner added a commit that referenced this issue Apr 23, 2019
(cherry picked from commit 6d8fb87)
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
Which in the case of track6 disables the new deconfiguration process.
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
Which in the case of track6 disables the new deconfiguration process.
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Production bug
Development

No branches or pull requests

2 participants