@Mr.:

BB has pfBlockerNG 1.0 ready, and awaits code review by the admins. pfblockerNG 2.0 (which BB is working on) is planned to have adblocking support.

Wooow, sounds awesome. I can´t wait to test the pfblockerNG :-p

Thanks to all for your replies
Regards

I understand
Thank you

I don't think I ever got any newsletter too. I think  ;D

.sfw,.flv  extensions would only throttle loading the video players, but not the video stream. I wonder if you can throttle videos without just throttling sites.

This is one of the most informative pages i have ever seen regarding this matter.

http://www.dd-wrt.com/wiki/index.php/3G_/_3.5G

@Harvy66:

At the time of this post, all 2.2 bugs are closed out

https://redmine.pfsense.org/projects/pfsense/roadmap#2.2

I'm eagerly awaiting 2.2.1

Some people just want to watch the world burn.

I worked on a Submarine Tender so it was a large ship. We had the big iron upstairs(VAX 8600) But i only did data entry and requisition status on that via a terminal in our workspace down in the bowels of the boat…Next door to our shop was "Tech Library" for the repair department and they had microfiche and TRS-80's. What a contrast... Was really surprised to see Tandy onboard. The VAX was mounted on special shock mounting and the TRS-80's were commodity. The VAX was actually a Sperry unit but Unisys had bought the company. From the looks of the above pictures it may have been a rebadged DEC maybe ruggedized by Sperry for shipboard use..

I, for one, welcome linux's new robot overlord.

Where are you seeing seemingly wrong interface stats? Status>Interfaces pulls from one set of counters, the RRD graphs from another, and they should match up.

The last person making that claim here a few days ago found out his ISP was clearly wrong and way off in their stats, the interface stats were correct. That's eventually found to be the reasoning in most all the cases.

Didn't see your PIC so i can't comment on that.
If you already have the PoE card then might it be possible to write some drivers for it or interegate it in some cruder fashion.

Steve

@stan-qaz:

@Harvy66:

BTRFS is not going to be production ready for a long time, it also has a lot of logic design issues that make it less than ideal for sysadmins. It wasn't designed by sysadmins, so they don't know the kinds of issues sysadmins have to deal with.

Thanks for that information, it is interesting stuff to think about and I've filed a copy away for review prior to my next Linux upgrade. OpenSuse Linux is shipping BTRFS as the default filesystem for some partition types today in version 13.2 and they intend to fully move to it at some point. They have jumped too early before on technical decisions, recently on systemd, so I am a bit leery of their choices at this point and don't wish to have another mess like I did when they went to Reiser (spelling?) as a file system and then it went away.

I don't see ZFS as a realistic option for my Linux needs due to the non-support by Linux distributions but since I'm not wedded to Linux as an operating system you make some interesting points that recommend an OS that offers native support for ZFS. For someone wedded to Linux the use of the ZFS format from the project might be a good option but it seems like it would be a lot safer to just go with a BSD and native ZFS.

I hear the recent FreeBSD implementation of ZFS supports feature flags, which allows upgrades to not change the current ZFS, so you can properly snapshot and roll-back your OS. Say you have 10.1 installed, snap shot before upgrading to 10.2, and if something goes wrong, just switch back. Even maintain two snapshots and you can reboot into the other, or possibly run it in a jail.

Always back-up your stuff  :p

To disable webgui redirect go to: System: Advanced: Admin Access , then check the 'Disable webConfigurator redirect rule' checkbox.

I don't have a tutorial.. But if you click around a bit it shouldnt be that hard to figure most things out..

Frontent listens on a ip:port for incomming connections, then uses a backend that contains the webservers to loadbalance between.
Using multiple shared frontends you can use acl's to add to the existing ip:port and send traffic to a different backend, for example when www.domain.com needs to be handled by a different backend&servers than mail.domain.com , while still listening on 1 port.

@Derelict:

Right, which is a "whatever's there is there" approach which makes perfect sense.

I second that!

It's just that I don't like to over-emphasize WiFi with pfSense. I own and sometimes use an alix3d2 with b/g card inserted and configured. But I surely don't jump the bandwagon demanding .11ac from pfSense which would be next.

Reliable WiFi is way more than entering an SSID, pass-phrase and off-we-go.
Just recently I heard >30 competing APs in my living room within the 2.4GHz band. Not counting Bluetooth and ZigBee devices.
Adding a WiFi card to my APU would only add to air pollution and be counter productive. However, the right AP in the right place does the trick.
FWIW

just create an iscsi target on your nas  & connect it on you windoze machine.

should be completely transparent to almost any application

Can't complain at that price.  ;)
Via padlock is nice. You'll find it can probably smoke the firebox in VPN throughput (with the correct encryption type) even though the processor is considerably less powerful.

Steve

You can get ZFS on Linux, just not along with Linux due to licence issues:

http://zfsonlinux.org/

http://zfsonlinux.org/faq.html#WhatAboutTheLicensingIssue

ZFS is licensed under the Common Development and Distribution License (CDDL), and the Linux kernel is licensed under the GNU General Public License Version 2 (GPLv2). While both are free open source licenses they are restrictive licenses. The combination of them causes problems because it prevents using pieces of code exclusively available under one license with pieces of code exclusively available under the other in the same binary. In the case of the kernel, this prevents us from distributing ZFS as part of the kernel binary. However, there is nothing in either license that prevents distributing it in the form of a binary module or in the form of source code.

Comparing them is beyond me and I've decided to reset the OpenSuse defaults and stick to Ext4 rather than the recommended BTRFS / XFS and sit it out until 13.3.

Lots of good reading if you do a Google versus search.

https://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs

I'm no snort person or aware of their functions but I would say that as long as you can prove you have tried to contact them to cancel, then via your bank (or payment service) block any new or future payments to them.  Eventually the snort bods should get in touch to say hey…you owe us xxxx and you re-open communication or your subscription may just die on its own.

Honestly, I wasn't planning to release it as a product. Creating it has been primarily something that I've done for fun and I've offered to set it up for people as a ministry. If it is something you (or your friends) would be interested in I'd be happy to setup a box at cost. Likewise, you could simply download and use the install scripts from my dropbox site and do it yourself.