Bug 35631 - SKIP and IPSEC together cause kernel panic
Summary: SKIP and IPSEC together cause kernel panic
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Archie Cobbs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-07 13:30 UTC by david
Modified: 2003-11-10 22:32 UTC (History)
0 users

See Also:

Attachments
file.diff (591 bytes, patch)
2002-03-07 13:30 UTC, david 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description david 2002-03-07 13:30:01 UTC 
Running both IPSEC and SKIP packets through the same interface causes a kernel panic.

Fix: Packets decrypted by IPSEC have a NULL receive interface. When an IPSEC-decrypted packet enters SKIP for processing it checks to see if SKIP is enabled on the receive interface. This causes a NULL pointer derefence and a kernel panic

A simple fix to the SKIP port is required:
How-To-Repeat: 
Run both SKIP and IPSEC traffic through the same network interface
Comment 1 Christian Weisgerber freebsd_committer freebsd_triage 2003-02-14 14:50:16 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->freebsd-bugs

Misfiled PR.
Comment 2 Kris Kennaway freebsd_committer freebsd_triage 2003-10-11 09:26:25 UTC 
Responsible Changed
From-To: freebsd-bugs->archie

Assign to skip port maintainer
Comment 3 Archie Cobbs freebsd_committer freebsd_triage 2003-11-10 22:31:59 UTC 
State Changed
From-To: open->closed

Patch applied.. thanks!