From: Patrick McHardy <kaber@trash.net>
To: mail@saschahlusiak.de
Cc: David Miller <davem@davemloft.net>,
contact@saschahlusiak.de, netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] sit: handle ICMPv4 for tunnels with no remote
Date: Mon, 08 Jun 2009 18:46:10 +0200 [thread overview]
Message-ID: <4A2D4052.2010108@trash.net> (raw)
In-Reply-To: <20090608161352.152078nqk5d89e8s@www.domaingo-webmail.de>
mail@saschahlusiak.de wrote:
> If iph.ttl == 0, it means that the ttl of the ipv4 package is inherited
> from the ipv6 package to be sent. In case the ipv4 ttl of the path
> expires, the ipv6 ttl would expire too. While the link does send a
> time_exceeded, I believe that the application should receive an ICMPv6
> time_exceeded as well, even if the package died right on the tunnel
> endpoint.
I have some patches that I wanted to post tommorrow, which will allow
to propagate errno values and queue congestion state of the underlying
device upwards from the hard_start_xmit() functions of virtual network
devices. With these patches, you can simply return -EHOSTUNREACH or
whatever is appropriate and it will be delivered to the application.
Would that help?
prev parent reply other threads:[~2009-06-08 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 14:02 [PATCH 1/3] sit: ipip6_err: ICMP_PORT_UNREACH is a possible event Sascha Hlusiak
2009-06-06 14:02 ` [PATCH 2/3] sit: handle ICMPv4 for tunnels with no remote Sascha Hlusiak
2009-06-06 14:02 ` [PATCH 3/3] sit: Translate ICMPv4 errors to ICMPv6, if possible Sascha Hlusiak
2009-06-08 9:40 ` [PATCH 2/3] sit: handle ICMPv4 for tunnels with no remote David Miller
2009-06-08 14:13 ` mail
2009-06-08 16:46 ` Patrick McHardy [this message]
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=4A2D4052.2010108@trash.net \
--to=kaber@trash.net \
--cc=contact@saschahlusiak.de \
--cc=davem@davemloft.net \
--cc=mail@saschahlusiak.de \
--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;
as well as URLs for NNTP newsgroup(s).