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

Fixed bug which caused the some cache files not being created #1524

Closed
wants to merge 1 commit into from
Closed

Fixed bug which caused the some cache files not being created #1524

wants to merge 1 commit into from

Conversation

aponert
Copy link
Contributor

@aponert aponert commented Apr 6, 2017

Hello, since opnSense is a fork of pfSense I found a solution for a problem I had with opnSense in the pfSense bugtracker. See: https://redmine.pfsense.org/issues/3669

They state, that there are 2 bugs which cause the cache files /var/db/wan_cacheip and /var/db/wan_cacheipv6 not being created.

One of the bugs is already fixed in pfSense as well as opnSense.
The other bug concerning IPv6 is fixed by my change and working for me.

For me, the bug caused OpenVPN restart every 15 minutes, when WAN has IPv6 enabled. Now it works.

However, I do not know the whole opnSense and can not say if this fix would have other side-effects.

@fichtner fichtner self-assigned this Apr 6, 2017
@fichtner
Copy link
Member

fichtner commented Apr 6, 2017

Hi @theq86,

Thanks! There is indeed something wrong here, but it looks like we should get rid of the cacheipv6 file trickery and align the code a bit more. IPv4 doesn't use this workaround so IPv6 should be the same.

I'll see what I can do and report back. :)

Cheers,
Franco

fichtner added a commit that referenced this pull request Apr 6, 2017
@fichtner
Copy link
Member

fichtner commented Apr 6, 2017

I've added f729d88 but won't be able to test this before tomorrow.

@aponert
Copy link
Contributor Author

aponert commented Apr 6, 2017

Thanks. I will apply the changes live on my opnSense and test as well.

@fichtner
Copy link
Member

fichtner commented Apr 6, 2017 via email

@aponert
Copy link
Contributor Author

aponert commented Apr 6, 2017

You're right. I reverted to my temporary fix. It works and it will do until your changes find the way into the release.

fichtner added a commit that referenced this pull request Apr 7, 2017
@Woi
Copy link

Woi commented Apr 23, 2017

@fichtner Will this fix make it to the 17.1.5 release?

@fichtner
Copy link
Member

fichtner commented Apr 23, 2017 via email

@Woi
Copy link

Woi commented Apr 23, 2017

If I run pkg install -y opnsense-devel as described in https://docs.opnsense.org/contribute.html#testing do I end up with an pre-release of 17.1.5 or an development version of 17.7?

@fichtner
Copy link
Member

fichtner commented Apr 23, 2017 via email

@Woi
Copy link

Woi commented Apr 23, 2017

I'll try to test the fix, but I don't expect to find time for this during the next two weeks.

@fichtner
Copy link
Member

fichtner commented Apr 25, 2017

The backported patch for 17.1.5:

# opnsense-patch f31964a

(run once to apply, run again to remove)

@aponert
Copy link
Contributor Author

aponert commented Apr 25, 2017

Since this pull request will never make it as it is, should we reject and close it?
Or move it into an issue (if possible)

@fabianfrz
Copy link
Member

@theq86 a pull request cannot be converted to a ticket.

@aponert
Copy link
Contributor Author

aponert commented Apr 25, 2017

Okay, then I close it because the issue presented in this pull request is going to be resolved by other commits.

@aponert aponert closed this Apr 25, 2017
@Woi
Copy link

Woi commented May 3, 2017

I'll give feedback f31964a

@fichtner
Copy link
Member

@theq86 your patch will go into 17.1.7 via 805cac40 -- thanks!

we're reworking and unifying the IP renewal for IPv4 and IPv6 completely for 17.7, so this buys some time. The code hasn't been dusted off in a very long time. :)

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.

4 participants