Probably yes. I'm calling the mount_rw feature but I did not tested this package on nanobsd yet.

Apparently that is the problem. I checked the "Keep media mounted read/write at all times" box under Diagnostics > NanoBSD, and all the read-only errors went away. There were still three errors showing up during boot however:

Code:

Warning: closedir() expects parameter 1 to be resource, null given in /usr/local/pkg/dansguardian on line 69

Warning: file(/usr/local/share/certs/ca-root-nss.crt): failed to open stream: No such file or directory in /usr/local/pkg/dansguardian.inc on line 74

Warning: Invalid argument supplied for foreach() in /usr/local/pkg/dansguardian.inc on line 76

I ran "pkg_add -r ca-root-nss" and rebooted, and now there are no errors at all. So apparently all the problems have been solved.


Now a different question. How does the process of adding banned sites, urls, etc work exactly? I added a second list to the Site Lists under ACLs with a couple in the "Blocked" section to test if it was working. After saving, it's still not blocking them. I did make sure the "Enable" box for banned was checked. Am I doing something wrong, or is there still a problem that's just not showing up during boot?

Yes, I am. You think that might be the issue?

Here are the errors that appear during booting.

Code:

Starting package squid...

Warning: chown() Read-only file system in /usr/local/pkg/squid.inc on line 77

Warning: chgrp() Read-only file system in /usr/local/pkg/squid.inc on line 78
9

Those errors are repeated many times (probably over 100)

Code:

Warning: file_put_contents(/usr/pbi/squid-i386/etc/squid/squid.conf): failed to
open stream: Read only file system in /usr/local/pkg/squid.inc on line 1159
done.
Starting package Dansguardian...
Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/exc
eptionfilesitelist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 409

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/ban
nedsitelist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 417

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/gre
ysitelist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 424

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/log
sitelist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 431

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/ban
nedurllist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 467

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/exc
eptionfileurllist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 474

Warning: file_put_contents(/usr/pbi/dansguardian-i386/etc/dansguardian/lists/exc
eptionregexpurllist.Default): failed to open stream: Read-only file system in /us
r/local/pkg/dansguardian.inc on line 481

And so on and so forth down to line 919. Then there are some different errors:

Code:

Warning: closedir()expects parameter 1 to be resource, null given in /usr/local
/pkg/dansguardian.inc on line 69

Warning: file(/usr/local/share/certs/ca-root-nss.crt): failed to open stream: No
 such file or directory in /usr/local/pkg/dansguardian.inc on line 74
 
Warning: Invalid argument supplied for foreach() in /usr/local/pkg/dansguardian.
inc on line 76
done.

It almost all appears to be related to the supposedly read only files. I've checked to make sure they are writable.
The permissions on squid.inc are -rwxr-xr-x and the permissions on dansguardian.inc (I changed them the first time I got the errors) are -rwxrwxrwx.

I rebooted just now and discovered that all of the read-only errors in my previous post are back, plus some errors from squid and I think more that I hadn't seen before from dansguardian. Is there a log I can find that shows these errors? I've been trying to take pictures of the screen as they flash by, but obviously that doesn't work very well.

I'm trying to install dansguardian on the latest 2.1 build, and I'm not getting it to work. I installed the squid and dansguardian packages and set them up, but when I test to see if its blocking anything, it doesn't block.

When I reboot pfSense, it spits out a bunch of errors when it tries to start dansguardian. I tried to capture them all, but I may have missed some.

Code:

Warning: file_put_contents(/usr/pbi/dansguardian-i386/dansguardian/
contentscanners/<variouslists>): failed to open stream: Read-only
file system in /usr/local/pkg/dansguardian.inc on line <various lines see list below>

I'm not sure I got all the lines, but the ones I got were:
647
662
669
676
683
702
--- a gap where I might have missed some ---
909
911
915
919

Then there's another series of errors

Code:

Warning: closedir() expects parameter 1 to be resource, null given in
/usr/local/pkg/dansguardian.inc on line 69

Warning: file(/usr/local/share/certs/ca-root-mss.crt): failed to open stream:
no such file or directory in /usr/local/pkg/dansguardian.inc on line 74

Warning: Invalid argument supplied for foreach() in /usr/local/pkg/dansguardian.inc on lind 76

So apparently there's something wrong with /usr/local/pkg/dansguardian.inc?
Suggestions are appreciated.

EDIT:
I changed the permissions on the dansguardian.inc file to make sure it wasn't read only, and all of the read only errors went away. The last three errors are still there however, and its not blocking sites.
Also, I don't know if its related, but squid is taking what experience tells me is an exceptionally long time to startup. It doesn't give any errors, just takes awhile to start.

Third, possibly not related, after installing dansguardian and squid and rebooting, I can no longer access my webConfigurator. It just times out. if I reset to factory settings, it will work fine, but after installing and rebooting again, it once again times out. I haven't tried to figure out whether its dansguardian, squid, 2.1 BETA, or some combination thereof thats causing this. The first time I had this problem I assumed it was the beta version of squid3 that I had installed, but now its happening again with the normal squid package.

I recently tried to do this myself. The main reason I stopped working on it was because my USB WiFi Adapter was causing pfSense to reboot at best every few hours. But I also was unable to get pfSense to properly connect to my phone. It would say it was connected (under Status -> Interfaces) but it wouldn't get an IP address and so of course, wouldn't actually work. I don't know if thats the issue you're having, but it might be worthwhile, after setting it up to connect, to see if its not connecting at all, or connecting but not getting an IP address.

Unchecking "Block private networks" on the 2.1 box, did indeed fix it. I am puzzled however, because my ISP is using a private network IP, and my 2.0 box is working fine with "Block private networks" enabled... However, the problem is solved, so I'm happy  .

I'm trying to setup a pfSense box behind an already existing one. The original one is running 2.0, the new one is running 2.1. I've got the new one installed and setup, but it can't access the internet. If I ping out (from Diagnostics -> Ping) from the WAN interface, it works, but if I ping out from the LAN interface it doesn't work. nothing connected to the LAN works either. Is there something I need to configure, either on the 2.0 box or the new 2.1 box, or is there something else wrong? Thanks.

It must not be the CF card then. It started doing this not very long after I built the system, so it's probably not write cycles anyway. I suppose it could be that some hardware was bad out of the box, but it was working fine at first, so I don't know.

if it were the CF you'd be seeing at least some errors in the logs, and usually a ton of them. Write errors, timeouts, something on adX or daX depending on what your CF device is.

I see you have, for a time at least, been running squid on a CF card. It is possible that the card has run out of write cycles on some blocks. Have you seen any warnings in the logs that might point to this?
What hardware are you running now?

Steve

That's possible. I haven't noticed any warnings, but I haven't been monitoring the logs too closely. Though I did check them once right after a reboot, and didn't see anything. What would such a warning look like?

I have a hard time believing it's hardware, but everyone else seems to think that, so maybe I'm wrong. 

I'm having a problem with my pfsense box randomly rebooting. There doesn't seem to be any pattern except that it occurs approximately once a week. Sometimes it'll only go six days, sometimes it will go for 10, but never more than that. There haven't been any problems or errors. It just reboots.

Yes, I thought of that, but it's not. It's right below another blocking rule that is working.

Both.

Yes. And blog.facebook.com and www.facebook.com and facebook.com (all of which return different IPs) Plus a dozen or so other IPs that I found to be associated with Facebook.

I'm trying to block Facebook during a certain time. I have an alias set up for Facebook following the instructions I've found on a number of different threads in this forum, but it's not working. I'm beginning to think it might not be a problem with my alias, but some other problem. I've tried going directly to a supposedly blocked IP from my browser (instead of going to the domain name that is associated with that IP), and it doesn't block it. I have another rule blocking all access to anything from a certain computer (on a schedule), which is working fine.