JFYI, the patch Ian recently MFCed does fix the problem here on our
4.7 box.
Thanks Ian :-)
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Langer; Patrick Soltani;
>[EMAIL PROTECTED]
>Subject: Re: panic: icmp_error: bad length
>
>
>
>BTW, if this bug exists in 5.0 for the same reasons (or even different
>ones), we should try to generate a fix ASAP and get it committed.
>
>Robert N M Watson Free
In message <[EMAIL PROTECTED]>, Rober
t Watson writes:
>
>BTW, if this bug exists in 5.0 for the same reasons (or even different
>ones), we should try to generate a fix ASAP and get it committed.
I'll check later today if 5.0 is affected. It is probably easy to
trigger by arranging for a bridged p
BTW, if this bug exists in 5.0 for the same reasons (or even different
ones), we should try to generate a fix ASAP and get it committed.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Thu, 12 Dec 2002, Ian Dowse wrot
On Thu, 12 Dec 2002, Ian Dowse wrote:
> --- ip_fw.c 21 Nov 2002 01:27:30 - 1.131.2.38
> +++ ip_fw.c 12 Dec 2002 00:43:22 -
> @@ -1573,6 +1573,11 @@
> break;
> }
> default:/* Send an ICMP unreachable using code */
> +
Hi again,
>
>the diagnosis looks reasonable, though i do not remember changing
>anything related to this between 4.6 and 4.7 so i wonder why the
>error did not appear in earlier versions of the code.
>
This is happening on 4.6-STABLE and -RELEASE as well as 4.7 all flavors.
Many thanx for identif
In message <[EMAIL PROTECTED]>, Luigi Rizzo writes:
>the diagnosis looks reasonable, though i do not remember changing
>anything related to this between 4.6 and 4.7 so i wonder why the
>error did not appear in earlier versions of the code.
Yes strange - actually, it looks like the "THERE IS NO FUN
the diagnosis looks reasonable, though i do not remember changing
anything related to this between 4.6 and 4.7 so i wonder why the
error did not appear in earlier versions of the code.
icmp_error() consumes the mbuf so i believe it is ok to scramble it
but one should double check.
Note that NTOHS(
In message <[EMAIL PROTECTED]>, Alexander Langer
writes:
>Yeah, same situation here. 4.6 used to work w/o problem, 4.7 doesn't.
Great, thanks for the debugging info. The bug seems to be that
icmp_error() requires that the IP header fields are in host order,
but when it is called on a briged pack
Thus spake Ian Dowse ([EMAIL PROTECTED]):
> >In the last couple of months, upgraded to 4.6 and 4.7 using RELENG_4 =
> >with again no errors, however, now under a light smurf attack, I get:
> >panic: icmp_error: bad length
> >Hardware: Dell PowerEdge 350, 2 built-in Intel n
In message <[EMAIL PROTECTED]>
, Patrick Soltani writes:
>In the last couple of months, upgraded to 4.6 and 4.7 using RELENG_4 =
>with again no errors, however, now under a light smurf attack, I get:
>
>panic: icmp_error: bad length
>Hardware: Dell PowerEdge 350, 2 built-in
raded to 4.6 and 4.7 using RELENG_4 with again no
errors, however, now under a light smurf attack, I get:
panic: icmp_error: bad length
syncing disks... 1
done
Uptime: 1h12m58s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
I have found couple of posting on Fr
12 matches
Mail list logo
