All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John H. Spicer" <jhs@edg.com>
To: Daniel Chemko <dchemko@smgtec.com>, netfilter@lists.netfilter.org
Subject: Re: Problem using fwmark -- how to mark packets from local host?
Date: Wed, 03 Mar 2004 17:43:00 -0500	[thread overview]
Message-ID: <40465F74.8070609@edg.com> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF56791BB@alderaan.smgtec.com>

Daniel Chemko wrote:
> Use the OUTPUT chain instead of the PREROUTING chain for packets
> originating from the local system.
> 
> 
>>Is there a way to mark packets originating on the local system?
> 
> 
> 

Thanks.  I tried that, but it did not seem to have any effect.  The command I 
used was:

iptables -t mangle -A OUTPUT -j MARK --set-mark 0x0a -p tcp --dport 25

Now, when connecting from the localhost, I get:

telnet: connect to address 66.33.196.49: No route to host

I can still connect via the NAT'd systems okay.

Thanks for the assistance!

John.


  reply	other threads:[~2004-03-03 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 22:17 Problem using fwmark -- how to mark packets from local host? Daniel Chemko
2004-03-03 22:43 ` John H. Spicer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-03 22:09 John H. Spicer

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=40465F74.8070609@edg.com \
    --to=jhs@edg.com \
    --cc=dchemko@smgtec.com \
    --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 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.