From: Rafa Garrido <rgarrido.l@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: NetBIOS dgm NAT Helper
Date: Sat, 17 Sep 2005 02:53:09 +0200 [thread overview]
Message-ID: <2b8e1997050916175339d88351@mail.gmail.com> (raw)
In-Reply-To: <1126895937.6687.3.camel@localhost>
It can that this patch of the last week help you:
http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=2859
It will be necessary to hope to that stable kernel appears.
Greetings.
On 9/16/05, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
> We have encountered an unusual situation where NetBIOS datagram packets
> (138/udp) are being passed through an IPSec tunnel on an iptables
> firewall but they are also being NATted by the same firewall. It
> appears there is IP information embedded in the NetBIOS header. Thus
> NAT causes this protocol to break because the reply packets are sent to
> the original IP address in the NetBIOS header rather than the NAT IP
> address in the IP header.
>
> I believe Cisco does have a NAT helper for NetBIOS but I have not seen
> anything for iptables. Is there such a helper? Is there anyway for an
> iptables firewall to NAT NetBIOS datagram packets? Thanks - John
> --
> John A. Sullivan III
> Open Source Development Corporation
> +1 207-985-7880
> jsullivan@opensourcedevel.com
>
> If you would like to participate in the development of an open source
> enterprise class network security management system, please visit
> http://iscs.sourceforge.net
>
>
>
next prev parent reply other threads:[~2005-09-17 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 18:38 NetBIOS dgm NAT Helper John A. Sullivan III
2005-09-17 0:53 ` Rafa Garrido [this message]
2005-09-17 2:21 ` John A. Sullivan III
2005-09-17 12:01 ` Rafa Garrido
2005-09-17 16:21 ` John A. Sullivan III
2005-09-17 20:15 ` Rafa Garrido
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b8e1997050916175339d88351@mail.gmail.com \
--to=rgarrido.l@gmail.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox