Thanks ! I will waiting.

@gerdesj:

@databeestje:

I've committed some fixes, try it now

Off on hols for a while.  Will try when I get back.  Daren't break a running system otherwise the house sitter won't be able to get internet access and I wont be able to stream BBC iPlayer 8)

Cheers
Jon

Updated to current snapshot. Working nicely.

Thank you.

Cheers
Jon

I am so sorry for making another post about this.

Solution found in: http://forum.pfsense.org/index.php/topic,48749.0.html

Another question, will Widescreen be adapted to work at a later point?

squidguard-1.4_4-i386 has installed fine on top of squid3 and is happily blocking sites for me on a timed basis.
I'll post an update about the Time-based Restriction stuff on the post about that at:
http://forum.pfsense.org/index.php/topic,43352.15.html
From the command line, pbi_info shows that squidguard-1.4_4-i386 is installed.
But the Installed Packages GUI page shows 1.4_2
It's a bit difficult to keep these version numbers in synch when different pfSense releases are using different versions of a package!
Jim, thanks for all the work on PBIs - at least squid3 + squiguard on 2.1 is looking good.

I couldn't see an obvious change that broke this - I guess it was somewhere in changes to the various require_once calls that were done a while ago. Serching for uses of $syscfg, in other places it is defined and used in the same file.
I found the $syscfg['timezone'] invalid reference in 3 places. I have submitted a pull request to fix these up.

not sure why but we have been manually including that rather than using a freebsd package. Though it is in ports.

/usr/ports/www/phpsysinfo is only 3.0.10 though.

@stephenw10:

Edit:  :-[ What you already said!
[/quote]
Thanks for the post. It reminded me of a correction I needed to make: It seems some WiFi interfaces are offered as lagg members even though they are assigned to pfSense, despite what lagg configuration page says.

Upgraded to build of 20120619-1425 - that fixes it, thanks.

It is working after today's firmware upgrade.

I only checked after the firmware upgrade and the box is ticked and it is working fine now. Thx.

OK

Ok, thanks.

Don't know if the issues are related, but if they are it may be in config.xml?

uname -a FreeBSD hostname.domain 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #1: Thu Jun 14 19:12:21 EDT 2012    root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8  i386

Yeah, I wanted some hardware details about the modems, mostly manufacturers etc.

The PPP fix works for me on 3G and PPPoE. Which I think covers it. I can reliably lockup the 3G connection on a ZTE modem though, I blame the ZTE modem for that mainly. Not having any issues with Huawei modems, they stay online for weeks. My 3G signal here is so-so. So every now and again it drops, the huawei just drops out of data modem with no-carrier and on it goes.

The ZTE device does not, which means we can't talk AT to it unless we reset the device, which can only be done over the application port which is just wrong.

Sure, manual assignments are perfectly fine.

Just checked in another attempt, because we now know the address family (because we have a drop down) that makes this a lot easier to get right.

Thanks I got it working, it still would be nice as a general rule to have an easy way to manually install a package GUI (I looked at creating my own package repository but that seemed overkill)

:-)

//Danne