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@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
