On Mon, Jan 16, 2006 at 08:08:19AM +0100, Patrick McHardy wrote: > > I can't figure out how this can happen. If a local outgoing multicast > packet would have been SNATed to a non-local IP, ip_route_input would > have been used by ip_route_me_harder. In that case we should see > ip_output instead of ip_mc_output in the backtrace. But it definitely > looks related to the rerouting changes in the NAT code.
The reason it stays in ip_mc_output is because the SNAT is performed by the POST_ROUTING hook in ip_mc_output. So it's too late to get out of it. Because at this stage in the stack we no longer look at dst->output the skb is simply passed onto ip_finish_output and then ip_finish_output2. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
