Bug 123858 - [stf] [patch] stf not usable behind a NAT
Summary: [stf] [patch] stf not usable behind a NAT
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 6.3-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-21 13:40 UTC by Lapo Luchini
Modified: 2018-01-03 05:16 UTC (History)
1 user (show)

See Also:


Attachments
stf.no_addr4check.diff (4.04 KB, patch)
2008-05-21 13:40 UTC, Lapo Luchini
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Lapo Luchini 2008-05-21 13:40:02 UTC
The stf(4) interface does proper filtering on the incoming 6to4 packets, 
but checking the destination address avoids it to work behind a NAT.

For those of us with a modem/router not capable enough to support IPv6 
but capable to redirect protocol 41 traffic (or maybe just all of it) to 
a NAT-ed FreeBSD box, this patch means easy and working access to IPv6 
world; ok, I'm absent-minded, but I already compiled a kernel forgetting 
to re-apply the patch three times in a row ;-)

Fix: This is ume's patch as in Message-ID: <ygeacqp2y0f.wl%ume@mahoroba.org>, 
applied on latest 6-STABLE.

Has been working perfectly for me in the past year and some more 
(tracking 6-STABLE on both i386 and amd64).
How-To-Repeat: 
ping6(8) some IPv6 website, watch the ping packets go (and correctly 
reach destination) and never see the answer.
Comment 1 Volker Werth freebsd_committer 2008-10-06 22:33:23 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net


Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:36 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