CALL FOR TESTING: NanoBSD Packages
-
HAVP may take more work than I thought, but I'll have to look at it again when I'm feeling a little better.
Squid and Squidguard were fairly easy to fix, and have been re-enabled for use on nanobsd, with a couple caveats:
1. Use HDD cache=0 on squid, unless you have some kind of external storage for the cache.
2. Be careful what you enable in squidGuard, as blacklists will likely use a lot of space in /var and there is not much to spare. -
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
Thanks!
-
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
I was finally able to install avahi. It interacted badly with mDNSResponder on the Macs on my network, causing them to think that there were other other hosts with the same name as themselves. This led to an endless loop of automatic self-renaming which stopped only when I uninstalled the package. I don't know enough about avahi to be able to tell why this happened. I was hoping to use the package to work around the lack of OpenVPN bridging support in pfSense. I wanted it to pass mDNS packets between the OpenVPN subnet and the LAN, but there seems to be no way of configuring it to do that.
-
That would be Avahi itself and not NanoBSD specific. Start a new thread for that. (NB - I use it to join two remote LANs via OpenVPN and it works well.)
-
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
Thanks!
I do, if it helps ;)
LCDproc: installs okay, but haven't been able to get output on the (picolcd) display, keep getting the standard output the manufacturer put in.
Log errors:
Nov 17 20:03:50 php: lcdproc: The chosen lcdproc driver is not a valid choice
Nov 17 20:03:57 php: lcdproc: Stopping service: no com port selected
Nov 17 20:04:00 php: lcdproc: The chosen lcdproc driver is not a valid choice
Nov 17 20:04:03 php: lcdproc: Stopping service: no com port selectedAlready posted that in a topic of mine, also in the picolcd topic and I tried contacting ermal since he/she said there would be a working version published soon. He posted that in January, no response from PM.
Tested on pfSense-1.2.3-2g-20091105-2039-nanobsd.
-
That sounds more like it is missing a driver than something nanobsd-specific. I'd wait to hear back from ermal or someone else working on the lcdproc package.
-
If the driver is missing, how can I check if it is that?
(Note, have some basic commandline skills, if necessary.)Already done that, ermal has been online here couple of times since I've send the message, no response, don't even know if it arrived.
Don't think there is anyone (else) working on the package… -
I'm not familiar with the lcdproc package, so I can't say for certain.
-
'kay.
Any idea who can help and actually replies to private messages?
Already tried (besides ermal) a (different) admin, to ask who is working on the package, but also no answer back. -
Most people on this forum prefer to keep things in the public forums, and are turned off by PMs.
You might try the support mailing list, or IRC.
-
Not getting any response there either, that's why I tried PM's.
Uhm, support mailing list?
edit: found it -
These 2 not very big packages, but packages nonetheless work fine:
- iperf
- blinkled
Fit123 doesn't work though (seems to expect a RW filesystem):
- installs correctly, but switching any of the features on/off have no effect
- themes work fine
- error when selecting DDNS tab in Fit123: Warning: fopen(/usr/local/pkg/Fit123/ddns/ddns.php): failed to open stream: Read-only file system in /usr/local/pkg/fit123.inc on line 164
Hardware: 2 carped ALIX 2D3's / pfSense 1.2.3 RC3 and 4GB CF cards.
-
Hello all
i use the 1.2. 1G images for testing.
Now i see that the full versions and the 4G versions are still beeing updated, but the 1G version is still from 14 Nov
both the update and the new to install versions.Are the 1 GB version obsolete?
regards,
Johan -
Sylhouette,
That is unrelated to this topic, please start a new thread for a different question.
-
Fit123 doesn't work though (seems to expect a RW filesystem):
- installs correctly, but switching any of the features on/off have no effect
- themes work fine
- error when selecting DDNS tab in Fit123: Warning: fopen(/usr/local/pkg/Fit123/ddns/ddns.php): failed to open stream: Read-only file system in /usr/local/pkg/fit123.inc on line 164
Further to this, it's clear that Fit123 isn't calling /etc/rc.conf_mount_r[w|o] when doing it's thing. I don't use DDNS (and perhaps the error is caused because DDNS is disabled?), and even so by calling /etc/rc.conf_mount_rw before visiting the Fit123 doesn't get rid of the DDNS tab error. However the Fit123 tab works fine - here's a workaround:
1: Open 2 tabs both visiting the pfsense box. This is important.
2: Install the Fit123 package as normal (System -> Packages)
3: Go to Diagnostics -> Command and run /etc/rc.conf_mount_rw and leave it
4: In the 2nd tab, go to Status -> Fit 123, select the settings as required and save
5: Check that it's applied the settings: System -> General should have 4 DNS server fields, Status -> System should have current time. If not, run /etc/rc.conf_mount_rw in one of the tabs again, and save Fit123 settings again (it took 2 goes for it's magic to work for me for some reason)
6: Once settings have been applied to your satisfaction, run /etc/rc.conf_mount_ro in Diagnostics -> CommandFor some reason even with /etc/rc.conf_mount_rw run and the FS as writeable, the DDNS tab in Fit123 still says the fopen() warning, leading me to believe there are actually 2 bugs here:
1. That /etc/rc.conf_mount_r[w|o] needs to be called for it to be properly NanoBSD compatible
2. That the DDNS tab has a further bug, which may be due to the actual DDNS service (Services -> Dynamic DNS) being disabled on my pfSense.
