@ky41083:

Does it worry anybody else that pfSense dev's accept code commits from this "genius"?

nope.

David, thanks for the insight. I already have my 2.3 VM up and running and will try to patch things for varnish4 in there.

The reason is to confuse the enemy… :D As I understand it, this is only used for package name itself?

No problem, won't delete the thread as it might help someone in the future.

If you want to try it sooner than later…well, check back later today.  :D Snapshots will be announced soon.

@Derelict:

If you upload it to /usr/local/captiveportal or upload it somewhere and link to it from /usr/local/captiveportal it will be available if it includes "captiveportal" in the Nain me.  http://portal_ip:8002/captiveportal-image-asset.png

There is a rewrite in the lighttpd config that disallows the web server from serving any files directly referenced that do not include the string "captiveportal" in its filename (the name of the link in /usr/local/captiveportal)

url.rewrite-once = ( "(.captiveportal.)" => "$1", "(.*)" => "/index.php?zone=guest_zone&redirurl=$1" )

My suggestion is to use one of the many available control panels or CMS to upload assets used in your captive portal page on a separate web server, which is where all but the most basic of portal pages belongs anyway.

Thanks mate this us perfect and 100% relevant.

I ended up doing just this - the /usr/local/www/ folder is public so made a /cportal folder and uploaded everything there and direct link. Works fantastic. Only had to change some code for this to work. Users can now upload from .NET software and set custom values to skin the UI with ease.

This is what the dev forum is about! Whooo

Thanks, new 32 bit builds are there now.

If it's properly declared global before use it may be OK…

Or there's the ever-popular "touch a flag file in /tmp/" style.

Though if debug_backtrace() shows it being called by the package install code that would be pretty obvious, though I'd have to run some tests to find out how deep that goes. If the info is there it would definitely be the most reliable way. It's not really a bad way to go about it, it just needs some experimentation to derive the required tests/info.

Be aware there will be differences due to the different PHP versions on 2.3 vs 2.2.x. It's OK for basic testing but be careful.

whois is in 2.3. We don't strip as much of stock FreeBSD anymore in 2.3.

Just FYI, fixed in Chrome a couple of days ago. (And meanwhile screwed a whole bunch of other JS: https://code.google.com/p/chromium/issues/detail?id=527930)  ::)

This is used in lots of packages without any problem. Yeah, keep those package accounts outside the reserved range.

Problem is, I want to get the data into an iphone-app…
Doing a http-get is piece of cake, doing a SNMP-call, I have no idea how.
Also I tried using some sort of snmp-walk software for windows, and it returned hundred, if not thousands of rows from Pfsense, seems to be quite a steep threshold in learning how SNMP works...

Now onto the good news : I ugly-hacked it!
It was as easy as going into the php-file and uncomment this row:
require_once('guiconfig.inc');

That seems to bypass the whole auth-system.
No idea what other issues this may cause tho :O

Follow-up question:
It doesnt seem that the interface bandwidth speeds are reported in any of these outputs?
Do I need to do consecutive calls to ifstats.php and calclulate the speeds myself?

Thanks :) Perfect sense, now it's explained!

And thus one learns New Things…  ::)

Hmmmm… I submitted a bunch of packages stuff (that wasn't move anywhere) and I wanted some visual hints about the context of some of the changes before doing a PR, so tried to use the GitHub preview for that... The preview didn't work at all, showed the original file all red, the new all green (-> useless). Now it somehow shows like it used to for some smaller stuff... The bigger files, still nothing.

The fsck is a pile of garbage. You can move to https://bugs.freebsd.org/bugzilla/, file a bug and wait a couple of years. Don't expect any fixes here.

I got it  ;D

had to create an file called "external-links" in same folder where is the pbi.conf

external-links

# Files to be Sym-Linked into the default LOCALBASE # One per-line, relative to %%PBI_APPDIR%% and LOCALBASE # Defaults to keeping any existing files in LOCALBASE # Use action binary for binaries that need wrapper functionality # TARGET                LINK IN LOCALBASE      ACTION #etc/rc.d/servfoo      etc/rc.d/servfoo        keep #include/libfoo.h      include/libfoo.h        replace #bin/appfoo            bin/appfoo              binary,nocrash #bin/appfoo2            bin/appfoo-test        binary bin/clamconf            clamconf                binary

IIRC if you add it here, someone will eventually pick it up and translate.

https://github.com/pfsense/pfsense/tree/master/usr/local/share/locale/en/LC_MESSAGES

(If you want it working locally, you need to regen the .mo files, read gettext docs.)

Yes, it can be a tag. Just something that can be easily found and used as a known comparison point.

FreeBSD 10.2-RELEASE is out: https://www.freebsd.org/releases/10.2R/announce.html