From: Don Gould <don@bowenvale.co.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] SMB traffic routing/blocking...
Date: Wed, 04 May 2011 21:30:17 +0000 [thread overview]
Message-ID: <4DC1C569.3040705@bowenvale.co.nz> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
Dear Spammers,
Thanks for waking everyone on the list up last night. ;)
Dear List,
Now that you're all awake, and following the number of requests for some
technical discussion, here's my current challenge on my little research
project...
Yes, I'm wanting to figure out the following for a Mikrotik RB750G
router, but AIUI the mkt runs a Linux core, so my request is on topic ;)
I've got a number of networks on my router....
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24
192.168.4.0/24
192.168.1.2 can ping 192.168.2.2, 192.168.3.2, 192.168.4.2
That's cool.
However I don't want people on 2.0 to be able to see computers in 3.0 or
4.0, etc.
I also don't want them to be able to establish windows networking
connections -- so basically samba/smb connections.
However I do what 192.168.2.0/24, 192.168.3.0/24, 192.168.4.0/24 to be
able to use a NAS in 192.168.1.0/24.
So I need to drop some traffic unless it's heading to my NAS IP
(192.168.1.2 for sake of argument).
I do want users in 192.168.x.0/24 to be able to see each other though.
I'm using a Mikrotik 750G with router OS5 on it, lic 4.
TIA
D
--
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
[-- Attachment #1.2: Type: text/html, Size: 1852 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2011-05-04 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 21:30 Don Gould [this message]
2011-05-04 21:45 ` [LARTC] SMB traffic routing/blocking Grant Taylor
2011-05-04 22:11 ` Don Gould
2011-05-05 15:47 ` Grant Taylor
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=4DC1C569.3040705@bowenvale.co.nz \
--to=don@bowenvale.co.nz \
--cc=lartc@vger.kernel.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.