On Sat, Aug 06, 2005 at 11:13:37AM +0200, Harald Welte wrote:
> On Sat, Aug 06, 2005 at 02:08:15AM +0400, Vladimir B. Savkin wrote:
> > I found that it really is NOTRACK who cause? bogus ICMP errors.
>
> Well, this means that your ICMP errors need to be NAT'ed but they
> cannot, since the original connection causing the ICMP error did not go
> through connection tracking.
How so, when there are no NAT rules that can match either source packets
or ICMP errors?
~
:wq
With best regards,
Vladimir Savkin.
-
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
