Summary: | [pf] [patch] pf rdr incompatible with dummynet | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Alexey Guskov <adg> | ||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Open --- | ||||||
Severity: | Affects Only Me | Keywords: | patch | ||||
Priority: | Normal | ||||||
Version: | 7.2-RELEASE | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Alexey Guskov
2010-06-30 13:20:07 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-pf Over to maintainer(s). How about a more generic solution: Add new mbuf tag PACKET_TAG_PFIL_RESUME_FROM that contains address of a function registered with pfil_add_hook (ipfw_check_hook in this case) and modify pfil_run_hooks() to skip all hooks until that one (if such tag is present). Before reinjecting packet into ip_output by dummynet, prepend this m_tag to mbuf (also strip that tag if it ever comes back?). I don't know if mbuf api allows it but such tag could theoretically have just one instance (created on dummynet module load) to avoid allocation costs. This way you don't have to put ugly workaround in every pfil consumer. For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi> |