FreeBSD Port: p3scan-1.0

[horio shoichi]

On Fri, 14 May 2004 19:55:26 +0200
Thomas M$B|l(Bler <thomas.muh at gmx.de> wrote:
> Hello,
> 
> I have a problem running p3scan on my FreeBSD 5.2.1 BOX.
> I think you have done the patches for a box running ipfw
> but i$B4m(B using the OpenBSD pf as a kernel module.
> 
> The problem:
> 
> 
> May 15 19:09:30 router p3scan[694]: Connection from 192.168.1.100:3790 
> May 15 19:09:30 router p3scan[694]: Real-server adress is 127.0.0.1:8110 
> May 15 19:09:30 router p3scan[694]: Oops, that would loop! <--
> May 15 19:09:30 router kernel: pid 694 (p3scan), uid 1002: exited on signal
> 11
> May 15 19:09:30 router p3scan[694]: Session done (Critial abort). Mails: 0
> Bytes: 0 
> May 15 19:09:30 router p3scan[590]: Attention: child with pid 694 died with
> abnormal termsignal (11)! This is probably a bug. Please report to the
> author. numprocs is now 1 
> 
> 
> After my pf does some nat the "real-server-adress" would not be corectly
> fetched from
> the kernel. T think because of the pf is only a kernel module.
> 
> I have watch out the patch-p3scan.c but i$B4m(B not good in programming c.
> 
> Any ideas?
> 
> Thanks a lot and sorry because of the bad english
> 
> Tom
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 


Ipfilter mailing list discussed p3scan problem about a month ago.

A short answer: use rdr rule on the host.



horio shoichi