[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lartc
Subject:    Re: [LARTC] ICMP time exceeded in-transit sent from wrong interface
From:       Simon Kissel <scamp () untergrund ! net>
Date:       2006-02-23 14:18:53
Message-ID: 1858757722.20060223151853 () untergrund ! net
[Download RAW message or body]

Just in case someone else in the future googles for this problem:

SK> My question now is: WHY does that happen, and what could I do against
SK> it? Is there some kernel setting or mechanism that decides which
SK> interface is used when sending ICMP time exceeded in-transit messages?
SK> My goal is that the message gets generated for the correct hop...

This seems to be as designed by the kernel. The ICMP message gets sent
from the target address of the original paket, if that address is
local. If not, the ICMP message gets sent from 0, the default
interface (which in my case is eth0).

IMHO this is totally broken logic in the Kernel. For a router, the target
address of the original paket will never be local. Instead the address
of the interface the paket gets forwarded to should be used as the
source address for the ICMP message.

Simon




_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
[prev in list] [next in list] [prev in thread] [next in thread]