All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Cempura <kcem@tlen.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Little problem with ifb. How to catch server traffic on
Date: Mon, 12 Feb 2007 21:17:57 +0000	[thread overview]
Message-ID: <45D0D985.2040006@tlen.pl> (raw)

I've network with NATed hosts.

I want to catch only all traffic going from my server, but I don't want
catch NATed traffic from LAN.

I need only traffic going from/to my server (traffic from INPUT, OUTPUT
chain in iptables) (like SSH, postfix, WWW or proxy).

This is throw all traffic from my LAN to IFB:

$TC qdisc add dev $iface_lan handle ffff: ingress
$TC qdisc add dev $iface_lan root handle 1:0 htb
#Incoming traffic...
$TC filter add dev $iface_lan parent 1:0 protocol ip prio 1 u32 match ip
dst 192.168.0.0/16 flowid 1:1 action mirred egress redirect dev ifb0
#Outgoing traffic...
$TC filter add dev $iface_lan parent ffff: protocol ip prio 1 u32 match
ip src 192.168.0.0/16 flowid 1:1 action mirred egress redirect dev ifb1

I need some rules to throw all traffic from my server to ifb.
This rules throw all traffic from my router, all with NATed LAN
traffic... And there is no way to filter this traffic:/

$TC qdisc add dev $iface_wan handle ffff: ingress
$TC qdisc add dev $iface_wan root handle 1:0 htb
#Incoming traffic...
$TC filter add dev $iface_wan parent ffff: protocol ip prio 1 u32 match
ip dst $server_external_IP flowid 1:1 action mirred egress redirect dev ifb0
#Outgoing traffic...
$TC filter add dev $iface_wan parent 1:0 protocol ip prio 1 u32 match ip
src $server_external_IP flowid 1:1 action mirred egress redirect dev ifb1

I need some help... Is any possibility to do this? How to catch packets
which is not from/to LAN - on WAN interface?

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2007-02-12 21:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45D0D985.2040006@tlen.pl \
    --to=kcem@tlen.pl \
    --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.