Yes it can do that.
However it's likely to to take a little playing around with the configuration to get it doing what you need. Still if you've got £12K to save that could be worthwhile!
What exactly do you mean by 'AD reporting'?
If you mean running a webproxy that each user has to login to authenticated against Active Directory then you may struggle to get exactly what you want. It can be done though, via captive portal and freeradius for example.

In my opinion the one part of pfSense you are likely to find lacking is logging/reporting. pfSense can export all it's logs to external reporting software though.

If you have VM servers setup then I suggest installing it and having a play around.

Steve

Yeah, it certainly looks something like that.

I don't have the log, from when the connection re-made, but here's a snippet from the point it was lost.  In this case, it was reporting the ISP's Gateway as the problem.

Is there any way that any process, that's using the gateway address, be re-started when the gateway changes, as the log shows:

dhclient: New Routers (re0): 192.168.100.1

So it does know that it could have changed.

Cheers.

llinfolog.txt

@jimp:

Probably worth applying the em tweaks from here:
http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards

Thank you, I'll have to take a look at this.

I don't think the mbuf's are the issue for me.

The pfsense guest became unresponsive again on Friday (just getting around to posting now), and the following was the last entry in my scripted log file:

Fri Mar 30 16:16:44 EDT 2012 514/5758/6272 mbufs in use (current/cache/total) 513/5541/6054/25600 mbuf clusters in use (current/cache/total/max) 512/5376 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)

This seems to suggest that mbuf's are not my issue.

@jupiters_spot:

It appears all the php files are to be found in /usr/local/www

the front end files, most of the back end work is done by files in /etc/inc/.  for packages, /usr/local/pkg/

Depends on what combination of traffic you have. If you have any VPN traffic it's going to lower your total possible throughput, by how much depending on how much VPN traffic you have. If you have the maximum possible VPN throughput going, you're not going to push a whole lot of traffic outside the VPN (though in reality what you'll see is more of an even split between inside VPN and outside VPN traffic, you're not going to achieve the full possible VPN throughput if you have a lot of non-VPN traffic going).

I've never seen anyone trying to use at on pfSense, I don't think it's meant to work.

To run something at bootup, look at the shellcmd package. It lets you setup commands to run at boot time.

I just figured it out.
This is actually multi-functional ethernet adapter.It could have firewire over ethernet, usb bus over ethernet or regular ethernet adapter.
On Pfsense web interface, from the INTERFACES menu> Assign Interfaces >Interface Assigment > change this option from "fwe0" to  "em" ( it could be em2 or em3 depending your interface number, this is usually the last interface)
and restart. You are all set.
Thanks everyone for their ideas.

@cmb:

Afraid so… without being able to use alternatives that NATing doesn't break, like RPC over HTTPS, you're stuck... Most everything will work through NAT, just most MS protocols won't (sounds like that's primarily what you need, go figure). Not really an answer here, you're stuck unless you can get routing put in place.

Thanks - at least you saved me some time wasting.

At the recommendation of a friend I installed another NIC in the device to segment IPTV traffic from regular traffic:

WAN: Public IP Address
LAN: 192.168.0.x /24
OPT: 192.168.1.x /24

The OPT interface is supplying IPTV/Multicast. - that works fine now with U-verse  ;D

Problem still remains with regards to CARP, adding a CARP interface to the WAN causes instabilities shortly after a reboot.  Is this a bug?  How does it get reported?

Thanks

i now tried it as only system in the lan, to test it real, meaning dialin pptp.
setting: WAN > pptp, local adr: 10.0.0.140/24, remote adr: 10.0.0.138

Still same prob, ping works from the lan pcs, internet not, same on pfsense.

I noticed strange entrys in the firewall log:
source: 10.0.0.138 Destination: 10.0.0.140 Proto: GRE
theres are a lot of that.

Any ideas ?

Yes, the different alias types are sometimes a little bit confusing. :)

The documentation on bridging is a little sparse. Especially for 2.0.X where bridging changed somewhat.
http://doc.pfsense.org/index.php/Interface_Bridges

It is my understanding that your second description is the correct way to bridge interfaces in 2.0. However if it's working for you….  ;)

If you do reconfigure your interfaces as described it's worth noting that since you can now assign a bridge interface, like any other, you can choose to have firewall filtering either on the bridge interface itself or on the member interfaces.
By default filtering is on the member interfaces which is suitable for a transparent firewall for example. However if you wish to bridge interfaces simply as a convenient way of connecting network segments, to connect a wifi AP say, then you can filter on the bridge interface instead. To do this you need to change two values in: System: Advanced: System Tunables:
net.link.bridge.pfil_member and net.link.bridge.pfil_bridge.

This is as I understand it from my own testing and reading other posts but I'd love to hear from one of the developers on this.

Steve

@Nonsense:

Could the lack of being able to be pinged cause my central office DSLAM to drop my connection?

I have never encountered that but it is conceivable.

There are many threads here about pppoe problems unfortunately. I have never had any trouble though.

I can't see anything in your log that looks unusual (not that I am any sort of expert!) other than the connection gateway being in a private subnet.

Steve

Thanks for your replies Steve, thats great info. I will give it a go soon!

This logging is all to ram only unless you have setup something different so I wouldn't worry about your disk.
You can set the rekeying interval to something higher if you wish. There is some trade off in security.

I have Key Rotation set to 3600 and Master Key Regeneration set to 7200.

Steve

You're probably looking to do it in the wrong place. Unless you have something like Squid setup where the firewall actually initiates traffic, the firewall has no control of that, has to be done on the actual source device.

Yes it should be in 2.1. Not sure what else there would be to "update" this - it was fixed in our repo (as I mentioned before) so it would be fixed in the next release.

@wetfish:

Is there a way I can fix this please?

Thanks in advance.

@sammy2ooo:

Same happens here on 2.0.1-RELEASE (i386). Resetting the RRD graphs did not help…

Nothing to fix, or to worry about, check this: http://redmine.pfsense.org/issues/1399