Bug #4537
closedCrash and reboot when accessing the web UI from the IPsec mobile client or over the tunnel on 32 bit
100%
Description
Accessing the WebUI while over the IPSec mobile connection will crash the box.
The issue was fist discovered on 2.2.
Forum thread https://forum.pfsense.org/index.php?topic=87946.0
Files
Updated by Chris Buechler over 9 years ago
- Subject changed from Crash and reboot when accessing the web UI from the IPsec mobile client or over the tunnel. to Crash and reboot when accessing the web UI from the IPsec mobile client or over the tunnel on 32 bit
- Category set to Operating System
- Affected Version set to 2.2
- Affected Architecture i386 added
- Affected Architecture deleted (
)
This is specific to 32 bit versions only, and something beyond that which hasn't been narrowed down yet, as it's not universal to all 32 bit systems. Nor is it hardware-specific.
Updated by Chris Buechler over 9 years ago
- Status changed from New to Confirmed
- Priority changed from Normal to High
Appears setting sysctl net.inet.ipsec.directdispatch to 0 (can be done under System>Advanced, System Tunables) fixes this issue.
Updated by Chris Buechler over 9 years ago
- Category changed from Operating System to IPsec
Updated by Chris Buechler over 9 years ago
- File pf-crash (1).txt pf-crash (1).txt added
crash provided in duplicate #4610 attached.
Updated by Chris Buechler over 9 years ago
- Target version set to 2.2.3
For 2.2.3, let's set net.inet.ipsec.directdispatch=0 where IPsec is enabled and running on 32 bit.
Updated by Ermal Luçi over 9 years ago
- Status changed from Confirmed to Feedback
Done for non amd64.
Updated by Ermal Luçi over 9 years ago
- % Done changed from 0 to 100
Applied in changeset 0559161320438f942e48c50263043d975be6fc21.
Updated by Ermal Luçi over 9 years ago
Applied in changeset 8b8a4630542156b160e22cf3921f0be5a4563179.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Resolved
- Affected Version changed from 2.2 to 2.2.x
that works around the issue. For tracking purposes we'll mark this resolved. I opened #4754 to investigate the root cause.