From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: NetBIOS datagram nat helper proposal
Date: Mon, 19 Sep 2005 21:52:04 -0400 [thread overview]
Message-ID: <1127181124.29021.34.camel@localhost> (raw)
In-Reply-To: <432F58A7.4030907@trash.net>
On Tue, 2005-09-20 at 02:32 +0200, Patrick McHardy wrote:
> John A. Sullivan III wrote:
> > It appears that we may need a netbios datagram NAT helper. Unless we
> > can find a workaround, it we have encountered a couple of environments
> > where we need to NAT netbios datagram packets. Since they have embedded
> > IP address information in the netbios header, this protocol breaks with
> > NAT. We see the packets enter the server with the NAT address but the
> > replies are addressed to the original address as per the netbios header.
> >
> > We have not seen such a helper within netfilter. There appears to be a
> > simple helper for this at
> > http://suif.stanford.edu/~csapuntz/ip_nat_netbios.c
>
> The helper does stateless NAT without issuing any expectations
> or even adjusting the conntrack entry. I'm not sure this is
> enough, but I'm not familiar with the netbios stuff. What is
> running on port 138? Do you have any pointers to a description
> of the protocol?
Yes, this is what I mean by finishing and polishing.
>
> > We are seeing if we have the resources to finish and polish this patch
> > and submit it. It seems that we then simply post it to this list to
> > submit it. Is that the correct procedure?
>
> Yes, if the patch is OK conceptually. If you send me some pointers,
> I'll have a look.
>
I believe it is defined by RFC1002. You can find it here:
http://ubiqx.org/cifs/rfc-draft/rfc1002.html#s4.4
I would think it is pretty straightforward but it is so easy to
dreadfully underestimate these things. Thanks - John
--
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com
Financially sustainable open source development
http://www.opensourcedevel.com
next prev parent reply other threads:[~2005-09-20 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 21:10 NetBIOS datagram nat helper proposal John A. Sullivan III
2005-09-19 21:27 ` Phil Oester
2005-09-19 21:30 ` Krzysztof Oledzki
2005-09-19 21:39 ` John A. Sullivan III
2005-09-20 0:32 ` Patrick McHardy
2005-09-20 1:52 ` John A. Sullivan III [this message]
2005-09-20 8:56 ` IPT_RETURN is not worked in the kernel 2.6.10 Vincent
2005-09-20 22:51 ` NetBIOS datagram nat helper proposal Patrick McHardy
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=1127181124.29021.34.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.