All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Greg Osinaike" <gregory.osinaike@elec.qmw.ac.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] routing locally created marked packets
Date: Sat, 24 Mar 2001 11:54:56 +0000	[thread overview]
Message-ID: <marc-lartc-98543483718242@msgid-missing> (raw)

Hello,

I have a simple question regarding routing of locally created packets.

I have set up netfilter 'mark' rules for all locally created IP packets with
destination port number 25 with the following:

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

I wish to set up specific routing entries for each locally created marked
packet. I have tried this using iproute2, with no success.

My question is do locally created packets initiate routing table lookups, if
not how can I achieve routing for locally created packets.

I've been trying for a week to do IP port forwarding on locally created
packets in this way.


 any help would be great.

ThanKs!
Greg.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

                 reply	other threads:[~2001-03-24 11:54 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=marc-lartc-98543483718242@msgid-missing \
    --to=gregory.osinaike@elec.qmw.ac.uk \
    --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.