Martti Kuparinen wrote:

> I'm not sure this is true, I've had the same problem. I "solved" it by 
> not using IPv6 :-(

Well, this happened again so I guess I need to upgrade our firewall to the 
latest and greatest netbsd-4 code...

# uname -srm
NetBSD 3.1.1 i386

# dmesg -M netbsd.1.core
trap() at netbsd:trap+0x149
--- trap (number 6) ---
fr_checkicmp6matchingstate(c0894960,0,28,c0894960,8) at 
netbsd:fr_checkicmp6matchingstate+0x95
fr_stlookup(c0894960,c2745ff8,c0894928,0,c0894960) at netbsd:fr_stlookup+0x2c4
fr_checkstate(c0894960,c089495c,c0894960,1,6) at netbsd:fr_checkstate+0x21f
fr_check(c2745fd0,28,c1cfc400,1,c0894a68) at netbsd:fr_check+0x4bd
fr_check_wrapper6(0,c0894a68,c1cfc400,2,c1cfc400) at netbsd:fr_check_wrapper6+0x23
pfil_run_hooks(c07ce180,c0894af4,c1cfc400,2,60) at netbsd:pfil_run_hooks+0x6e
ip6_output(c2745f00,0,c0894bb0,4,0) at netbsd:ip6_output+0x891
icmp6_reflect(c2745f00,28,1,8000000,cb5b202a) at netbsd:icmp6_reflect+0x287
icmp6_error(c274ad00,2,0,500,c1df3320) at netbsd:icmp6_error+0x1b8
ip6_forward(c193b700,0,c1cfc400,1,c193b700) at netbsd:ip6_forward+0x47d
ip6_input(c193b700,0,0,246,0) at netbsd:ip6_input+0x499
ip6intr(55390010,30030,a67a0010,10,c0891000) at netbsd:ip6intr+0x76
DDB lost frame for netbsd:Xsoftnet+0x4e, trying 0xc0894e60
Xsoftnet() at netbsd:Xsoftnet+0x4e