rm /var/db/rrd/*, then go to the RRD settings and press save. Check the system log after doing that and if there are any errors with the files, it should show you there. Also check after loading the page.

Hi Steve… I am pulling the Kingston memory and my guess there is something going on there. This x700 also has an upgraded used pIII processor so I may even have to look at that and put the OEM celeron back in if the symptom does not stop with the memory. I am building a drive copy off the working x700 and will retest this x700 again with the OEM memory to see if that changes anything. No, the symptom is not on all ports... And somehow this was all working on the dlink switch prior to this "On off" issue... which was really confusing. I thought this box was completed and went to the customers business to install and then the fun began. It would not pass DHCP on his unmanged Cisco switch. Since bringing the box back to my lab it is getting worse so will have to test the OEM mem and processor to see if this clears up. When you see this port issue happen there is no link light on the Cisco 3750 switch port and in the serial console you can see the port going up on down on the x700 re1. It started acting up and then with no link light and then shutting off and on. I moved this hard drive to my second x700 and it runs fine when installed. My guess is the memory. Will update later. Thx... H.

If you run the PPPoE server, does that mean everything upstream of the WAN port such as ADSL routers need to have their MTU also changed to 1492?

Switch might be better idea. Have you tried bridging, i'm not sure if it works with vlans, but try and inform

I can't see a problem with this. They mention pfSense on their web page. They seem to be offering an appliance with a fork of pfSense. Of course my Portuguese isn't great!  ::) Steve

I have seen them before. Maybe they did not like your post/ad as there are other items for sale. Here's one: http://forum.pfsense.org/index.php/topic,28893.msg150117/topicseen.html#msg150117

Thank you

If you perform a network capture on the WAN port of pfSense, what is the protocol, source and destination address of the traffic which you are seeing hitting the WAN interface?

I can confirm, that since I'm using built Sat Jun 11 the bug is corrected and there are no more log entries and the history is no longer flooded. There is also no more possibility to adjust the time of storing to database. I assume, it's still done all 5 minutes, but now silencely.

@Cry: It may be a Squid problem - have you checked the Squid logs? Apparently that was it, I switch my host to point to the same gateway, apparently, I was using the wrong one… so now, the host cannot resolve it too, i am digging into pfsense to see what's wrong in there. Thanks.

Are you meaning default vlan, or making that port as access mode?

oh right thanks for clearing that up for me i thought because the router handled the dhcp i thought all the traffic went through that clearly not! learn something new everyday. so my plan is to run pf in vm for a while install an adsl pci card (to do away with the router completely) and have it manage the lot. thanks for all your help. i'll probably be back when i get stuck installing it somehow

Hello jimp, thanks for your answer. yes, that's what I checked first, but all the settings are ok (ip, dns, gw). Even when I config static settings I'm not able to get a connection anymore. It's always after the first reboot. I now tried smoothwall, and there I have no connection issues, but I prefer pfsense ;) Another error I had sometimes is that after disconnecting wan or setting anything up on network interfaces, the web ui had some problems an I had to reboot the web ui. Maybe a driver issue?

If you are using squid this is normal. I have 4GB RAM and when I run squid form some days there are 75% RAM in use ~ 2.2GB only for the squid process: SQUID uses RAM for the index of your "Hard disk cache size".  (I use 10240 ~ 10GB) Its dependent on the "Memory cache size" (I use 1024 ~ 1GB) and it is dependent of the "Maximum object size" (I use 524288 ~ 512MB)

Thank you :) That is what I needed to know. So I will be ordering the 1.2.3 book & will purchase the 2.0 book when it comes out :) Thanks for all your hard work on this stuff! It's much appreciated… My CEO just wanted an automatic WAN failover. When I was able to build one that did that, plus replace our old router/firewall, as well as do load balancing, traffic graphs, and all the other great stuff by using old hardware we already had, and not even having to pay for the software... Needless to say it got me some brownie points with my CEO for adding way more features than the requirements called for as well for doing it at a grand total cost of $0.00. So much appreciation and will try to show some love back by purchasing the official books written by members of the project.

OK, fixed. Thanks Jimp!! I left the firewall rule to handle things other than port 80. For Squid: As Jimp implied, leave "General tab -> Bypass proxy for these source IPs" blank. Place the IP in "Access Control tab -> Banned host addresses" and that should take care of port 80.

ok - tnx :: i did try out that 'reset button' with several limit of time, without                 success - so i made a 'null-modem'