Bug 157689 - [ipfw] ipfw nat config does not accept nonexistent interfaces
Summary: [ipfw] ipfw nat config does not accept nonexistent interfaces
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.2-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-07 16:00 UTC by Viktor Štujber
Modified: 2017-12-31 22:32 UTC (History)
0 users

See Also:

Attachments
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 Viktor Štujber 2011-06-07 16:00:21 UTC 
ipfw accepts rules for interfaces that do not (yet) exist, and makes
them work seamlessly as the interfaces come and go. However, the 'ipfw nat'
addon feature is not compatible with ipfw's interface handling philosophy.

Fix: 

A workaround using cloned_interfaces was suggested. This preemptively
creates a dummy interface to satisfy ipfw.
How-To-Repeat: # ipfw add 60000 allow via foobar
60000 allow ip from any to any via foobar
^-- works

# ipfw nat 100 config if foobar
ipfw: unknown interface name foobar
^-- doesn't work
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2011-06-09 22:27:53 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-ipfw

Reclassify and assign.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:11 UTC 
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