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

Fix for static IPv6 when using PPPoE IPv4 on WAN #2736

Merged
merged 1 commit into from
Sep 19, 2018
Merged

Fix for static IPv6 when using PPPoE IPv4 on WAN #2736

merged 1 commit into from
Sep 19, 2018

Conversation

marjohn56
Copy link
Member

When using a static WAN IPv6 address and using PPPoE for v4, if you save and apply the interface - this is when the interface is already up, the IPv6 address does not get applied, an error from ifconfig is generated. It appears as though the interface is not ready to accept the v6 address. This fix adds a slight delay in calling ifconfig if both the IPv6 address is static and the v4 is pppoe.

This is a fix for issue 2726 https://github.com/opnsense/core/issues/2726

@fichtner
Copy link
Member

For static IPv6 on top of a PPPoE this may be more suited for rc.newwanip, see my question on the Use IPv4 toggle state?

@marjohn56
Copy link
Member Author

Use IPv4 connectivity is checked, as it's using the PPPoE link.

@fichtner fichtner self-assigned this Sep 19, 2018
@fichtner
Copy link
Member

Ok, that means the spot you are looking for is here, no sleep required:

https://github.com/opnsense/core/blob/master/src/etc/rc.newwanip#L118

Cheers,
Franco

@marjohn56
Copy link
Member Author

Interesting, as it only happens if you save and and apply when the interface is already up, if you take disable the interface - save & apply then enable - save & apply it's OK.

@marjohn56
Copy link
Member Author

We are talking static IPv6, not SLAAC or dhcp6c, even though it's using the v4 connectivity,

@fichtner
Copy link
Member

@marjohn56
Copy link
Member Author

marjohn56 commented Sep 19, 2018

OK.. done that, I get warnings that the route cannot be applied, but it all seems to work fine. Hold on spaces again!!!

@fichtner
Copy link
Member

looks good, ready for pull? :)

@marjohn56
Copy link
Member Author

Want kev to check his too. We may be the only two who use this strange setting. :)

I've emailed him.

@fichtner
Copy link
Member

ok, let me clean up related fluff in interfaces.inc ... that shouldn't get in the way of the merge now

@marjohn56
Copy link
Member Author

He'll test it and post here, but it could be tomorrow.

@fichtner
Copy link
Member

ok, no problem. just let me know :)

@nivek1612
Copy link

tested works like a charm :-)

@fichtner fichtner merged commit 2392c75 into opnsense:master Sep 19, 2018
@fichtner
Copy link
Member

Thanks, merged! :)

@fichtner
Copy link
Member

fichtner commented Sep 19, 2018

@marjohn56 would you mind testing this on top of master 9d37fe6 in the next few days... I made a reusable function. works for my static v4/v6, but I don't have the PPPoE / Use v4 part.

@marjohn56
Copy link
Member Author

My live system is now development... ooerr!

Works fine.
Reboot OK
Save and apply OK.

@marjohn56 marjohn56 deleted the Fix-for-static-IPv6-when-using-PPPoE-v4-issue branch September 19, 2018 20:02
@fichtner
Copy link
Member

brilliant, many thanks ❤️

@marjohn56
Copy link
Member Author

That bits OK, but the dev version has something amiss in the firewall, it was not allowing any of my rules for my servers, everything was hitting the default deny.

@marjohn56
Copy link
Member Author

@fichtner - Finally had chance to test again regarding my last comment. Dev version definately NOT working. Something is very broken in the Aliases. Firstly, the existing aliases are not imported into the GUI. Re-creating the alias entries creates some real strangeness in the config.xml and still they do not work. Going to email the xml files to you.

@fichtner
Copy link
Member

thanks, looking at it now. we have the new aliases planned for 18.7.4 which is basically ready so worst case we have to pull 18.7.4 last minute. keep you posted.

@marjohn56
Copy link
Member Author

I will switch my test unit to release to check whatever is needed, won't have another chance to mess with the live unit but I can edit the aliases into the test unit config.xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants