@jchuerta:

I have the same problem any ideas ?

We need your config.xml to track this down.  I believe all the php errors are due to the XML parse error showing in your logs.  Thanks

–Bill

If it helps anyone else out, the card that had these issues was a D-Link DGE-530T.

Thanks again guys :)

Very true - you will see if pfsense is detecting the processor cores but the question was to see if the cores were actually being used - the top command will show it whereas the dmesg will only show they were detected.  :)

gm…

That functionality will be in 1.3.

@onhel:

Status/UPnP

;D

Alright. Alright. There's no way that link was there last night, when i was up too late, and tired, and… Oh i give up.

Thank you.

I wouldn't recommend disabling local logging, unless you have a specific reason for doing so. It's usually desirable to be able to see the logs from the webGUI as well as on your syslog server.

Your config is fine, my first guess is as onhel suggested, a firewall on the machine.

Here is a HOWTO

http://doc.pfsense.org/index.php/HOWTO_setup_vlans_with_pfSense

This has been discussed before, and the response is that you're on your own if you do.  It's completely unsupported.

I would say that I strongly disagree with your final sentence.  The most you should ever install on a firewall would be a proxy server or VPN endpoint.  You should never run FTP/HTTP servers etc.

look at

http://forum.pfsense.org/index.php/topic,6335.msg36526.html#msg36526

Hmm, 0 responses?  Oh well it's no longer relevant (to me).  I was forced by another decision to use a different router.  :'(

Was a bad memory card….  :-\

Thanks for your help,

Have you checked the "Block offenders" option?

I applogize this is slightly off topic.
I was reading this thread trying to figure out if i may have an issue and find that the ntp engine is running however it hasnt updated in two days. the last time it updated was when i installed pfsense
Sep 24 21:37:42 ntpdate[251]: adjust time server 219.117.196.238 offset -0.061082 sec
I searched for a little insite into how offen it updates and possible problems.
I know the clock wasnt that far off but in two days there should be some drift to show in an update.

I ended up using a combination of both. I filled out the remaining rules I hadn't already rebuilt by hand using the "new rules based on this one" button, then did some cut/paste and find/replacing in config backups to fill out opt2-4.

Thanks again to you both.

take a look

http://forum.pfsense.org/index.php/topic,6270.msg36212.html#msg36212

It's a 32 bit counter. It'll be that way until it's changed in FreeBSD.

Danny

You should never remove the SSH-2.0-OpenSSH_4.5p1. Some SSH clients use this to figure out what options your SSHD server supports. In the past I have changed  SSH-2.0-OpenSSH_4.5p1 too SSH-2.0 and never encountered a SSH client that brakes because of that change, but you never know. The clean way to change the SSH-2.0-OpenSSH_4.5p1 is to edit the SHHD source code.

laterz
JamesDean