netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
	netfilter-devel@vger.kernel.org
Subject: Re: Accessing packet marking functions
Date: Wed, 30 Jun 2010 07:32:13 +0100	[thread overview]
Message-ID: <1277879533.1561.39.camel@andybev> (raw)
In-Reply-To: <alpine.LSU.2.01.1006300815280.30439@obet.zrqbmnf.qr>

> >> That retrieves the socket mark, not the packet mark.
> >> The packet mark on outgoing packets gets initialized to the socket mark...
> >
> >Hmmm, I understand. So is there any way to retrieve a packet's mark as
> >opposed to a socket's mark?
> 
> And how would you do that with SOCK_STREAM anyway?

I don't know. I'll admit that I don't fully understand what I'm doing
here, which I apologise for, but I'm trying to learn.

All I want to do is retain a packet's mark from its arrival into Squid,
onto its transmission to the client. Something like this:


ppp0 -> PREROUTING -> Squid -> POSTROUTING -> eth0

            ^^                      ^^
         Set Mark               Read mark


If this isn't possible then please tell me.

Thanks,

Andy



  reply	other threads:[~2010-06-30  6:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 16:42 Accessing packet marking functions Andrew Beverley
2010-06-19 20:01 ` Jan Engelhardt
2010-06-19 20:50   ` Andrew Beverley
2010-06-20 11:16   ` Andrew Beverley
2010-06-20 11:52     ` Jan Engelhardt
2010-06-20 12:31       ` Andrew Beverley
2010-06-22  6:16         ` Patrick McHardy
2010-06-28 21:21           ` Andrew Beverley
2010-06-28 21:45             ` Jan Engelhardt
2010-06-29 21:22   ` Andrew Beverley
2010-06-29 21:35     ` Maciej Żenczykowski
2010-06-30  6:14       ` Andrew Beverley
2010-06-30  6:15         ` Jan Engelhardt
2010-06-30  6:32           ` Andrew Beverley [this message]
2010-06-30  6:47             ` Jan Engelhardt
2010-10-24 17:30               ` Andrew Beverley
2010-10-24 23:55                 ` Jan Engelhardt

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=1277879533.1561.39.camel@andybev \
    --to=andy@andybev.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=zenczykowski@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).