@mibovrd:

I take it the LAN interface is similar, with no collisions, etc.
Any mbuf errors in syslog? type in mbuf in the filter at the bottom. I had an issue with a realtek gig card that I added for an opt interface. I think my issue was running too many Gig cards on a PCI interface, and I had similar problems, a little more frequent than yours though. Need PCIe or x for Gig cards really.
I would Google for the intel and realtek chipset models cards to see if there are any issue that might require tweaks, there are a few that have issues. More with Realtek than Intel, but intel has some too. I would try Google pfSense 2.0.1 + chipset model numbers and then FreeBSD 8.1 + chipset model numbers.

Nothing shows up when I apply a filter for mbuf in Status: System logs: System

Thank you for the input. I'll research more into the chipsets.

Anyone use any other tools?

I am running a SmokePing test as well. NY looks interesting, have a look.

http://www.dslreports.com/r3/smokeping.cgi?target=network.0e4309b87aadaaef433745f5ccdd14ce

Edit:
Tests are done. Looks like route through NY is the worst. For the overall test through NY, it looks to be about over 2% packet loss. The others were slightly better.

No, mbuf errors and the WAN interface doesn't show any errors.

Based on this, it doesn't appear that the problem is on my end, but how can I be sure?

Media 100baseTX <full-duplex>In/out packets 21190740/20936341 (17.38 GB/1.62 GB)
In/out packets (pass) 20936341/14416830 (17.35 GB/1.62 GB)
In/out packets (block) 254399/0 (29.57 MB/0 bytes)
In/out errors 0/0
Collisions 0</full-duplex>

It turned out that also the "libpng.so.6" was missing, after transferring the files with pscp (from a virtual installation) it seems the graphs are live again.

@dhatz:

"symmetric NAT" (more) i.e. the most restrictive (and secure) type of NAT.

Wow, 100% pure information on that page. I just discovered I knew nothing.
Thanks Dhatz.  :)

Steve

I have similar crashes with PPPoE client (WAN) from time to time (sometimes it is up and running for 80+ days), for me it looks like there is common problems with  PPP in pfsense. I did not reported them as it always reported in redmine. Those kernel panics are related to PPPoE reconnection in most cases.

Huh, that is not something I would have thought of.
Weird.  ::)

Steve

This will help for a start, eh?

http://doc.pfsense.org/index.php/Asterisk_VoIP

ohh i want to use:

squid and as parent havp anti virus

and

load-balancing with failover

ON ONE machine! ;)

No NAT reflection is the correct way to do this if you are using a URL to access an internal server.
The Winbox software appears to use it's own dynamic DNS lookup somehow so this would probably apply.
http://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F

Steve

Edit: I can't find where I read that about WinBox and DNS now.

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 ?