Netdev List
 help / color / mirror / Atom feed
From: "Sérgio Gomes" <sergiomdgomes@gmail.com>
To: netdev@vger.kernel.org
Subject: Routing header reversal in Linux kernel
Date: Mon, 22 May 2006 13:42:40 +0000	[thread overview]
Message-ID: <89fb8be00605220642l3730a60alf7015ee626b8ed69@mail.gmail.com> (raw)

Greetings!

I am a final year student in Instituto Superior Técnico, Lisbon,
Portugal, and part of my final project requires the use of IPv6
routing headers.

In particular, I need the route reversal to work. Now, as it didn't, I
began analysing the source code, and found a comment, stating that it
was a known problem with the IPv6 standard (as I was aware) and that a
way had been built around it via a constant, to avoid the whole AH
mess the RFC imposes.

So I was hoping someone could help me with something. The problem is
that even if I remove that verification, it does not work --
specifically, it looks as though the kernel is prepared to reverse
routing headers on a listening socket (i.e., a passive one), but not
on an active
socket (that is, one making the connection). My terminology is
probably wrong, but I hope you got my point.

However, I have only looked into this now, so I barely understand the
IPv6 implementation in the Linux kernel. I was hoping that you would
be able to shed some light into the subject, namely: is it at all
possible to have a TCP socket initiate a connection, receive a SYN+ACK
from the remote socket that includes a routing header, and reverse
this header for the remaining packets in the TCP connection?

Thanks!

Sérgio Gomes

             reply	other threads:[~2006-05-22 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 13:42 Sérgio Gomes [this message]
2006-05-22 15:43 ` Routing header reversal in Linux kernel Sérgio Gomes

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=89fb8be00605220642l3730a60alf7015ee626b8ed69@mail.gmail.com \
    --to=sergiomdgomes@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox