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

Bootloop and Kernel Exception with Trace while Configuring Wireguard #46

Closed
skl283 opened this issue Sep 3, 2019 · 7 comments
Closed
Labels
support Community support

Comments

@skl283
Copy link

skl283 commented Sep 3, 2019

Hi guys,

i think i've found a serious Bug. I've added 2 Devices like this to get Wireguard to Work and to configure policy based routing (Copy & Paste out of the backup.xml)

    <opt3>
      <if>wg0</if>
      <descr>WGVPN</descr>
     <enable>1</enable>
      <lock>1</lock>
      <spoofmac/>
    </opt3>
    <opt4>
      <if>wg1</if>
      <descr>WGAZIRE</descr>
      <enable>1</enable>
      <lock>1</lock>
      <spoofmac/>
    </opt4>

and i've configured wireguard to use these Interfaces. While activating these Interfaces the System reboot.

You can look at the Stack-Trace which i've already sent by Mail through the webinterface. I've uploaded it here: https://pastebin.com/dsApfGcz

Are you having any hints or suggestions or could fix my issue? I've posted already a Thread in the OPNSense Forum, but did not get an answer. Link: https://forum.opnsense.org/index.php?topic=14044.msg64586#msg64586

I need both Interfaces. One for VPN Incoming Connections, and the other for my VPN Provider. Is it possible to fix the crash? Could i change something to get rid of the bootloop?

@fichtner
Copy link
Member

fichtner commented Sep 4, 2019

As with previous kernel crashes this should be reported to FreeBSD. Also, you don't have the issue template filled out so we don't know which versions you use.

See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233955

@skl283
Copy link
Author

skl283 commented Sep 6, 2019

Thank you @fichtner for your Reply. Sorry, if i didn't filled out every relevant things, but i've postet a pastebin Link with Version.

The Link you have posted (ID 233955) is marked as fixed. I don't understand why this is relevant in my case? Perhaps you could help me to bring this bug in the right form to post it at the freebsd bugzilla?

@fichtner
Copy link
Member

fichtner commented Sep 6, 2019

The link is for reference that this happened in the past. There may be more crashes yet to be reported like yours. I want to show you where and how you will need to report it.

@skl283
Copy link
Author

skl283 commented Sep 6, 2019

OK. I understand but i don't feel to be able to post all relevant information to freebsd bugzilla that they can fix "my" issue.

Could you help me to extract the relevant Inmformation so hat i can create the Post?
I don't know what they ned out of Stacktrace from my post...

sorry.
sash

@skl283
Copy link
Author

skl283 commented Oct 14, 2019

Exactly this Issue was posted at opnsense Forum - https://forum.opnsense.org/index.php?topic=14403
@fichtner @mimugmail perhaps one of you could help to get this issue fixed?

@fichtner fichtner transferred this issue from opnsense/core Dec 3, 2019
@fichtner fichtner added the help wanted Contributor missing / timeout label Dec 3, 2019
@skl283
Copy link
Author

skl283 commented Feb 6, 2020

Since October last year nothing happened. Are there any chances to get this issue fixed? Or do i need to test v20.1?

@AdSchellevis
Copy link
Member

@skl283 policy based routing? it might be #52, depending on configuration you might consider disabling "shared forwarding" in firewall advanced if it's the same issue

@fichtner fichtner added support Community support and removed help wanted Contributor missing / timeout labels May 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

3 participants