By the way, I love IPF!  ut here are the details of my system I am having
problems with:

Solaris 8 - uname -a is: SunOS bass 5.8 Generic_108529-14 i86pc i386 i86pc
Processors:  Dual PIII 650MHz on Supermicro Mobo, 768MB RAM
IPF 3.4.27  (as well as a prior version, 3.4.16)
Compiled with gcc 2.95.3 from sunfreeware.com
Dual Intel NICs: iprb0 and iprb1, iprb0 is internal, iprb1 is external
internet
Special cards: none
Internet Connection: Cable modem
Problem: When ipsec tunneling is enabled, the system panics and reboots
after just a few minutes up time.
Error Logs: See below

Further observations:

 Without ipsec tunneling enabled, with ipsec running on point to point and
with IPF loaded, the system is stable, very stable.  It has been running for
over a year without issues but only recently has ipsec been enabled.  A
friend is also having the same problems but with Solaris 8 on a Sparc and I
suspect an earlier version of IPF complied with the Forte compiler.  Both of
us suspect with ipsec tunneling enabled, the IPFilter corrupts the esp
(ipsec security module) and causes the systems to crash.

 If we use ipsec without tunneling, all is fine.  But this prevents virtual
networking.  If we unload the ipf module and run ipsec with tunneling
enabled, it works correctly. Without tunneling, ipsec also runs correctly.

ipsec and ipf seem to be able to be loaded together, it is under initial
connections, and under load where the panic occurs.

 I think the next syslog entry tells alot: (it is the only abnormal ipf log
entry)

May 11 12:22:16 bass ipf: [ID 604323 kern.warning] WARNING: Unknown layer 2
header size for ip.tun0 type 1

Typical Syslog panic output on Solaris 8 intel:

May 11 18:25:36 bass ^Mpanic[cpu0]/thread=efc25e40:
May 11 18:25:36 bass unix: [ID 683369 kern.notice] BAD TRAP: type=8 (Double
Faul
t) rp=fec0d890 addr=efc23ffc
May 11 18:25:36 bass unix: [ID 100000 kern.notice]
May 11 18:25:36 bass unix: [ID 839527 kern.notice] sched:
May 11 18:25:36 bass unix: [ID 702911 kern.notice] Double Fault
May 11 18:25:36 bass unix: [ID 381808 kern.notice] addr=0xefc23ffc
May 11 18:25:36 bass unix: [ID 764221 kern.notice] pid=0, pc=0xfe86b950,
sp=0xef
c24000, eflags=0x10282
May 11 18:25:36 bass unix: [ID 827398 kern.notice]
May 11 18:25:36 bass eip(fe86b950), eflags(10282), ebp(0), uesp(efc24000),
esp(f
ec0d8c0)
May 11 18:25:36 bass unix: [ID 358493 kern.notice] eax(48), ebx(0), ecx(0),
edx(
14), esi(0), edi(0)
May 11 18:25:36 bass unix: [ID 258166 kern.notice] cr0(8005003b),
cr2(efc23ffc),
 cr3(15ee000)
May 11 18:25:36 bass unix: [ID 720544 kern.notice] cs(158) ds(160) ss(160)
es(16
0) fs(1a8) gs(1b0)
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_link:       0x0
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_esp0:
0xefc0fe
8c
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_ss0:
0x160
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_esp1:
0xfec0d8
e0
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_ss1:
0x160
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_esp2:
0xfec0d8
e0
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_ss2:
0x160
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_cr3:
0x15ee00
0
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_eip:
0xfe86b9
50
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_eflags:
0x10282
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_eax:        0x48
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_ecx:
0xe27509
c0
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_edx:        0x14
May 11 18:25:36 bass unix: [ID 455490 kern.notice] tss386.t_ebx:        0x0
May 11 18:25:36 bass unix: [ID 100000 kern.notice]
May 11 18:25:36 bass last message repeated 1 time
May 11 18:25:36 bass genunix: [ID 672855 kern.notice] syncing file
systems...
May 11 18:25:36 bass genunix: [ID 733762 kern.notice]  2
May 11 18:25:37 bass genunix: [ID 904073 kern.notice]  done
May 11 18:25:38 bass genunix: [ID 353387 kern.notice] dumping to
/dev/dsk/c0d0s1
, offset 107479040

---------------------------------
Dave Anderson
[EMAIL PROTECTED]

Reply via email to