From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Netbios over NAT
Date: Thu, 19 Oct 2006 13:52:12 -0400 [thread overview]
Message-ID: <1161280332.3212.28.camel@localhost> (raw)
In-Reply-To: <4537B28D.4020708@plouf.fr.eu.org>
On Thu, 2006-10-19 at 19:14 +0200, Pascal Hambourg wrote:
> Hello,
>
> John A. Sullivan III a écrit :
> >
> > As far as I know, most NetBIOS functionality works across NAT except for
> > browsing (and perhaps name registration).
>
> Isn't it because these functionnalities use IP broadcasts ?
>
No, they can be configured to use unicast packets and a WINS. However,
even with unicast packets and WINS, it breaks when NAT is applied - 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
prev parent reply other threads:[~2006-10-19 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 14:28 Netbios over NAT Jeremy
2006-10-19 15:38 ` John A. Sullivan III
2006-10-19 17:14 ` Pascal Hambourg
2006-10-19 17:52 ` John A. Sullivan III [this message]
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=1161280332.3212.28.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=netfilter@lists.netfilter.org \
--cc=pascal.mail@plouf.fr.eu.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