From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: two subnets...
Date: Wed, 01 Aug 2007 20:11:39 -0500 [thread overview]
Message-ID: <46B12F4B.10603@riverviewtech.net> (raw)
In-Reply-To: <46B10CCE.9040507@interia.pl>
On 8/1/2007 5:44 PM, Pawel Zawora wrote:
> Stupid question: Is it possible to filter packet based on src or
> dst IP? or using TCP state (contrack, port, flags)
Yes, you can filter based on port. To do connection state filtering I
think you will need to use IPTables. With the Bridged IP/ARP Netfilter
code you can use all of IPTables features on layer 2 in the bridge and
not have to worry about crossing subnets.
> Yes, It it so complex
Indeed, probably too complex.
> I have one "big" subnet (assume 1.1.1.0/24) now I want remove 3
> machines (1.1.1.98 - 100) to separete "small" subnet "small" subnet:
> It is enough to change subnet size to /29 and define new default gw
> router - I need to create 1 additional routing table that will send
> data to my smal subnet based on dst address "big" subnet - I have to
> told *each* machine: send packet to GW even 1.1.1.98... seems be in
> local network.
Again, I'm a bit confused as to whether or not you want the machines you
are moving to a different network to be able to communicate with the
machines that are staying on the big network or not. Let me ask it a
different way, what is your reasoning / motivation for moving the
machines in question to a different network?
> Similarly thinks are done in DR (in this case I dont need to create
> extra routing rules ) But probably I cannot use DR mechanism in my
> situation...
Again, will you please try to explain more of your situation (if you
can) as to what you have now and what you are wanting to achieve and why
you are going that route. In other words, what is your original problem
/ desire?
> After this I can create any iptables rules on the router..........
Yes. The bridge is as much a real interface as any ppp interface, so
you can do just about any thing you want to with it.
> Thank you for explanation
You are welcome.
> Probably bridging is easiest way to solve my problem....
Probably. Though I can not say for sure with out knowing more about
your situation. I keep asking, because bridging is a very good solution
in a lot of situations, but what you do with it is how you tune the
bridging setup to your environment.
> Does snort work correctly on brigde server?
I see no reason why it would not. I have successfully ran any and all
utilities against a bridge interface with out a problem. TCPDump, DHCP,
any web server / dns server / mail server, just about any thing. The
only draw back that I see with using a bridge for Snort is that you
can't physically cut the transmit line so you have to use the no arp
methods to stop arp replies.
> What is the best way to trace and log tcp connections in that
> scenario?
Probably the same thing that you are doing now. TCPDump, Snort should
work, libpcap, you name it.
> Thank you
You are welcome.
Grant. . . .
P.S. If you would be more comfortable discussing details off of news
group just drop me a line.
next prev parent reply other threads:[~2007-08-02 1:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 10:31 two subnets Pawel
2007-07-31 15:05 ` Grant Taylor
2007-07-31 19:28 ` Pawel Zawora
2007-07-31 20:07 ` Grant Taylor
2007-07-31 22:40 ` Mike Wright
2007-07-31 23:28 ` Grant Taylor
2007-08-01 13:38 ` Maximilian Wilhelm
2007-08-01 14:04 ` Pascal Hambourg
2007-08-01 20:14 ` Pawel Zawora
2007-08-01 21:14 ` Grant Taylor
2007-08-01 22:44 ` Pawel Zawora
2007-08-02 1:11 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 19:15 Pawel Zawora
[not found] <200708020115.l721FOEu011164@mail3.jubileegroup.co.uk>
2007-08-02 5:56 ` G.W. Haywood
2007-08-02 14:14 ` Michael P. Brininstool
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=46B12F4B.10603@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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