Like many, I use 1:1 NAT to give one of my public IP address to an internal
host. This works great for certain applicatons where the host (such as
Asterisk) is 'smart' and can be made aware of the fact that the IP address
bound to its own network interface differs from the one the outside
I use pfsense 1.2.3-RELEASE and I installed ntop v.3.3.8. but Ntop working 5
minutes and then stop logs is below kernel: pid 49342 (ntop), uid 0: exited on
signal 11 (core dumped) How can I resolve my problem ?
Thank you for your help
Pretty much my experience as well across several platforms,
On 12/31/2009 2:12 AM, Koray AGAYA wrote:
Hi,
I use pfsense *1.2.3-RELEASE* and I installed ntop v.3.3.8. but Ntop
working 5 minutes and then stop logs is below kernel: pid 49342 (ntop),
uid 0: exited on signal 11 (core dumped) How can I resolve my problem ?
[snip]
Dec 31 09:00:27
Generally, the best way to handle something like this is to actually give the
host the public IP, and avoid NAT altogether.
However, sometimes, that's not an option, and so you can use the following to
trick the host into working as expected.
(Note that 192.0.2.x documentation IPs are used -
On Thu, Dec 31, 2009 at 9:52 AM, Karl Fife karlf...@gmail.com wrote:
Like many, I use 1:1 NAT to give one of my public IP address to an internal
host. This works great for certain applicatons where the host (such as
Asterisk) is 'smart' and can be made aware of the fact that the IP address
