From: "John Jones" <jjones@merlintechnologies.com>
To: netfilter@lists.samba.org
Subject: NetBIOS browsing across subnets
Date: Thu, 4 Jul 2002 13:44:57 -0700 [thread overview]
Message-ID: <007201c2239b$a885a8b0$6301a8c0@JJONES1> (raw)
I have a need to allow NetBIOS/Network Neighborhood browsing across a
firewall between one internal LAN segment (192.168.0.0/23) to another
(192.168.10.0/24). The two networks are on interfaces eth2 and eth3,
respectively, off of the corporate firewall.
The two segments of the LAN were seperated due to broadcast flooding
during video streaming development work by a dev team.
I have the majority of the instructions down, I *think*:
iptables -t nat -I PREROUTING 1 -i eth2 -p tcp -d 192.168.0.1 --dport
139 -j DNAT --to 192.168.10.1:139
iptables -I FORWARD 6 -i eth2 -o eth3 -p tcp -d 192.168.10.1 --dport
139 -j ACCEPT
iptables -t nat -I PREROUTING 1 -i eth3 -p tcp -d 192.168.10.1
--dport 139 -j DNAT --to 192.168.0.1:139
iptables -I FORWARD 6 -i eth2 -o eth2 -p tcp -d 192.168.0.1 --dport
139 -j ACCEPT
Not sure if this should be Destination NAT or Source NAT. I would like
advice and/or corrections from anyone out there that has a better
knowledge of this, first.
Thanks in advance.
next reply other threads:[~2002-07-04 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 20:44 John Jones [this message]
2002-07-04 20:46 ` NetBIOS browsing across subnets Antony Stone
2002-07-04 21:52 ` Stewart Thompson
2002-07-05 0:37 ` Ron Gedye
2002-07-05 18:34 ` Nathan Cassano
2002-07-05 18:40 ` Adam D. Barratt
2002-07-05 19:15 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 22:51 George Vieira
2002-07-05 0:48 George Vieira
2002-07-05 2:42 ` Michael
2002-07-05 1:49 George Vieira
2002-07-05 3:21 ` Michael
2002-07-05 2:30 George Vieira
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='007201c2239b$a885a8b0$6301a8c0@JJONES1' \
--to=jjones@merlintechnologies.com \
--cc=netfilter@lists.samba.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