I meant what does the interface report when you query if with ifconfig. Some cards have a problem with hardware vlan tagging, you can disable it on an interface (em0 here) like so:

If that works you can set it to run at boot using a cron job or with the Shellcmd package.

Steve

You could use Firewall->Traffic Shaper, Limiter and put all your traffic into a limiter. That will slow you down all the time! But it is nice to be able to download at your full speed (8Mbps) so that a file download finishes quickly and you can use it. You just can't do that 24 hours a day on most home plans.
There is nothing in pfSense to count the amount you have downloaded and give you a warning when you reach near your quota.
Note: even if you limit to 1Mbps, that is about 7.5MB/min = 450MB/hour = 10.8GB/day = 324GB/month. If you have something on your network constantly downloading (and/or uploading = bittorrent…) then you will still chew up plenty of quota.

I am not a dansguardian user, so I am not familiar with the settings for that. You might get faster replies by posting in the Packages forum category.

Ok i see pfsense is using the syslogd is that right?

I see there is also the syslog-ng installed but without any use as i see is that right too?
I need to change the hostname in logging to the fqdn because i have more pfsense with the same hostname but different domain names.

Does nobody else has the same problem?

Its solved, thank you so much..

I removed squid3-dev and installed squid3 package and it's working now. I don't know why.

I didn't know there was a package like that. Thanks @Jimp

Hi Steve,
thank you for your answer… unfortunately both solutions didn't work...

mbmon -c1
returns

and
sysctl -a | grep therm
or
sysctl -a | grep temper

return no results… :(

Ok, I got it, I will upgrade my firewall sooner or later... :D

EDIT: and yes, ACPI is enabled in the BIOS setup, and recognized during the boot... (ACPI APIC Table: <compaq broadh2o="">)

Thanks,
Michele</compaq>

Check this: http://forum.pfsense.org/index.php/topic,64790  ;)

Updating the firmware to the latest release appears to have fixed whatever issue it was. I wish I was able to determine what happened, but don't have the knowledge on BSD to do so.

I will put all my settings/packages back in place and see if this happens again. If it does not after a few weeks, then I will wipe the disc and reinstall fresh and chalk it up to some obscure setting or config that developed on the pfSense install. A hardware issue on the machine it was affecting would have been better as I would have found the issue I suppose. I don't like "not knowing" what would cause such a weird situation really. Oh well.

Thank you to all the responses.

Sounds like you have a bit of testing on your hands.  Enjoy.

i found my answer!

https://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-write

I'm sure you have had it explained but:

Port 135 is certainly not a port that needs to be, or should be, exposed to the Internet. Hacker tools such as "epdump" (Endpoint Dump) are able to immediately identify every DCOM-related server/service running on the user's hosting computer and match them up with known exploits against those services.

Any machines placed behind a NAT router (any typical residential or small business broadband IP-sharing router) will be inherently safe. And any good personal software firewall should also be able to easily block port 135 from external exposure. That's what you want.

*******  And this is whats causing your inability to connect probably ********

In addition, many security conscious ISPs are now blocking port 135 along with the notorious "NetBIOS Trio" of ports (137-139). So even without any of your own proactive security, you may find that port 135 has been blocked and stealthed on your behalf by your ISP.

So, it doesn't much matter how awesome your security and filtering is, your ISP is in all likelihood not allowing it.
VPN really is the way to go.

You could probably handle the group issue within pfsense but I'm not sure about DNS by time.  Anyway - Good luck.  :)

/tmp and /var are just memory disks (md0 and md1). On nanoBSD there is nowhere to move them., they live in memory and get created again every boot. The CF card partitions are mounted read-only, and you don't need to mess with that. pfSense mounts them RW when it needs to update the config.
On the CF card there are 2 slices with 2 copies of FreeBSD. When you upgrade, the new version is writtten to the opposite slice. Then the selected slice for boot is swapped, and the system rebooted. It boots from the new slice, and you get the new pfSense+FreeBSD.
The advantage is that, at the console, you can change the boot slice just after the BIOS stuff has run. So you can switch easily between versions if needed. The config is in a partition of its own, accessible from both the other partitions. Take a backup of your config before upgrading, as upgrades usually have some config file conversions, so the config is not always backward portable.
IMHO you should upgrade in-place. It is easy and works. If you have a decent internet connection then use the auto-update from the webGUI. Otherwise, download the upgrade image for your CF card size and use the Manual Update from webGUI to suck it off your local computer and upgrade.