Hi,

I come across a similar issue with ntop.

I am running version 2.0-BETA5 on a test system and was looking at what report are available.

After installing ntop and configuring it will not run.
I had to install two additional library files.
pkg_add -r GeoIP and
pkg_add -r rrdtool
and still will not work.

I now get the following error:
/libexec/ld-elf.so.1: /usr/local/lib/librrd_th.so.2: unsupported file layout
when i try to start ntop.

any ideas.

Thanks
George  ;D

You can use port forwards for that. Interface LAN, source and dest as desired, target of the proxy server and its port.

It seems to be working fine here.  Do you have anything else between pfSense and the 'net?  That could affect this.

Something to try:  see if you can use a browser on a machine behind pfSense to browse the update server.  Check from in front of the pfSense box as well if possible.

Windows, AVG, Symantec, Avast and Spywareblaster. So it's actually doing those without a client trigger? This page is interesting: http://www.squid-cache.org/Doc/config/refresh_pattern/

but I don't see anything there about precaching. Looks like I'm going to need the book.

Not sure if this is related so I started a new thread and linking it here in case it is:

http://forum.pfsense.org/index.php/topic,31855.0.html

This one: pfSense-2.0-BETA5-20110103-0042.iso.gz

The new snapshot fixed the issue…awesome! I wasn't able to get back to you on the layout of the dashboard since I was on the road. Irrelevant at this point, I guess.

Thank You!

I found this post which seems to be exactly my problem: http://forum.pfsense.org/index.php?topic=28389.0

Refering to Bug 911 in Redmine, can someone please confirm that when apinger detects a monitor IP as being down, provided there aren't any load balancers set up it won't kill the states? I have a setup where I have 2 Internet connections however they aren't used in a failover/load-balanced fashion.

Thanks

Ah, thank you for that clarification !
I forgot to consider that fact (that since 1.2.3 sits on the same net as the originating host, it sees no need to consult an external router but dispatches the reply traffic itself immediately to the originating host)

EDIT: In this case it might have been smarter to have a DHCP setup since the only point for me in having the 2.0 router involved is that it eliminates the need to configure an extra route on each server on the LAN. With DHCP I could just push the route dynamically from the DHCP-server (assuming pfSense has that capability, to both push routes in the 2.0 version and apply them on the WAN side via DHCP in v1.2.3).
Currently I'm wasting bandwidh funneling data via the 2.0-firewall, something which could be avoided with a static route on each machine.

Just checked with

2.0-BETA5 (i386)
built on Mon Jan 3 13:22:20 EST 2011

Still the same.  Can connect to any PPTP VPN just fine, but if I do not continuously send traffic the link goes half dead - I can send packets but never receive anything.

Please this is very important, any insights?

Bummer… hard to say which sucks less between my ADSL router and my ISP's customer support.

Thanks for your help.  :)

The error still returned…. so.....

....Disabled APIC.

Error gone.    ;)

You know what's funny - when I was first drilling through the BIOS I thought I saw ACPI in two places and thought, 'wtf - stupid BIOS'.  Of course, one is APIC and one is ACPI.

Reading is hard.

Possibly because no connections are made from OPT1?
The database of the logins is shared between the 2 so the connections should be there.

Disabling state killing will not disable notification on logs.
It just means that the states will not get killed and that's it.

@macmacmac:

Ok, i meesed up the things  >:(.

Problem was that Captive Portal was inadvertitely enabled and not working.
Upgrading to the last snapshot resolved the problem.

The strange thing is that until 12/17 snapshot, to make Captive portal work, i was forced to execute:

/sbin/sysctl net.inet.ip.fastforwarding=1

Now in the last snapshot, with VLAN interface, i need to set:

/sbin/sysctl net.inet.ip.fastforwarding=0 (the default value)

Thanks
Happy new Year!

Which is why you shouldn't tinker with such settings :-)

It was broken before, that fix wasn't a real fix, it just pushed the problem elsewhere, then when it was fixed right, it seemed "broken"…

Probably not the two together, but one may not be allowed as a bare character in xml. I'm not sure how that was allowed before, might be changes in the xml parser code that did it.

Have you tried it with just @'s, or just the pound symbols? I'm guessing it's the £ throwing it off.

Since you've posted the PSK for all the world to see you're better off changing it anyhow. :-)

The most likely cause is the older vmware tools loading, leading to a panic.

I had thought we had a ticket open for that situation, but I don't see it. I just opened one:
http://redmine.pfsense.org/issues/1156

There is no general way to do notifications (yet, in 2.0, may happen for 2.1) but for now the only things worthy of a notification are things that cause the scrolling error at the top of the GUI. Usually things that affect the system in some way: Errors loading filter rules, errors syncing to a carp slave, creating ssh keys, etc. Things that are pretty rare but critical to know about.

For 2.1 I hope to be able to have some kind of general use for it, like disk space notifications, etc. We'll see what happens though…

That worked. However, why wasn't that user created when the virtual server was established, if that user ID is required to make the pools work?

Needing to create that user should be part of the documentation on building a load balancing pool, in the version 2.0 documentation, if that's not planned already.

Not having ever created a load balance pool in version 1, was it necessary to create that user there too? I never read that in any of the how-to's.

Thanks,
Timm