Something is seriously out of wack.  I would reinstall and if the problem persists start looking at potential hardware failures.

Do you have a IPSEC VPN Tunnel terminating to the 2nd LAN?? For some reason, i can not ping anything on my 2nd lan from pfSense when a IPSEC Tunnel is running.. If i turn it off, i can ping all day long..

hi did it really work with 1.2.1, i try installing 1.2.1 but i couldn't succeed running and provide internet,  any special setup i must do, isn't it like 1.2 in setup?

Im sorry. I didn't know if I needed to configure anything in pfsense. Thank you very much for the link. MUCH appriciated. Have a great day!!!

aray: send a blank email to announce-subscribe@pfsense.com to get on our announcements mailing list, we'll notify folks there when it's available for purchase. Of course you can also purchase per-install support right now, but for those with numerous installs the pricing on the new model may be much lower, depending on the level of assistance you require.

Using mrtg –> snmp data shows the same values as ntop, so only 20mbit (see screenshot) while the rdd graph in the gui on pfsense shows 50mbit? So even the SNMP data from the interface shows wrong values. Bug in the coding? Or rdd graphs in the gui not displaying correctly? Basicly if I could get the same graphs from the RDD in the gui I would be happy. Uploading it to antoher webserver with a script (with pass in it) wouldn't be such a good idea..

@ermal: Can you verify that the same case exist with 1.2.1 or 1.3? 1.2.1-RC1 built on Thu Aug 7 09:48:37 EDT 2008 I just found a related post with the "nodnssec" option…worked a treat. http://forum.pfsense.org/index.php/topic,7248.msg41434.html#msg41434 Thank you for all those who read this. I spent a few hours googling/searching to find a solution (before I posted).

What happens is that the internet is slow and doesnt finish loading pages. It goes at like 1Kb/s instead of 3Mbit! This sounds almost as if you have MTU problems. pfSense lowers the MTU on PPPoE links automatically so it shouldnt be a problem. But maybe you could try to lower the MTU manually to something very low like 1000 and try it again.

@submicron: The git repository isn't for public consumption at this time. It sure makes it harder to contribute if the source isn't available! [ Update ]  Ah, the instructions on http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso appear to still be valid.  I've updated the GitInfo page to make that clear. It's not clear which branch in CVS has the latest code though…?  Help! Is there an ETA for git access for the rest of us?  It is, as you know, much much much nicer to work with than CVS. - ask

it is also the same sysctl -a | grep net.inet.ip.fastforwarding net.inet.ip.fastforwarding: 1

Right, the result of yet more testing. To answer my own question 3. "testing the performance of a network drive" you can use a program called  PerformanceTest v6.1 which enables you to test the performance of network drives and compare them to previously saved baseline for comparison. Download Credits [image: linkstation-performance.jpg] To answer my own question 4. To set the MTU under Vista you can use a command prompt command called netsh Credits netsh interface ipv4 show subinterfaces to show current MTU netsh interface ipv4 set subinterface "Local Area Connection" mtu=7418 store=persistent to set a new MTU of 7418 Cool - Now I have my router set to 7418, my Vista PC and I know my NAS has a drop down that supports it. So I set the NAS and rebooted and hay presto I can ping the NAS, SSH to the NAS but can't bring up the web interface or browse the windows shares held on it. So knock my PC back to 1500 (netsh interface ipv4 set subinterface "Local Area Connection" mtu=1500 store=persistent) and it all instantly springs into life. So I do an # ifconfig eth0 on my NAS to make sure it is set for 7418 and sure enough it says MTU is 7420 (two more than it web interface) With all three devices set to 7420 they can ping each other with a fat packet (ping -l 7420 under windows ping -s 7420 under linux/freebsd) except that the windows PC can not ping the nas with a fat packet only with one of 1500 but the NAS can ping the PC, so I think that the NAS is lying and not capable of running with JUMBO frames even though it says it should so I will be giving the Qnap guy's an ear bending on their forum. Anyway, in summary Jumbo frames are supported and quite easy to implement and when I get my NAS playing ball I will be able to confirm the increase in speed. Cheers and hope this has given some people food for thought.

Reading the multi-wan forum would be helpful: http://forum.pfsense.org/index.php/board,21.0.html Also from the documentation: http://doc.pfsense.org/index.php/Multi_WAN_/_Load_Balancing Basically any old machine you have lying around will be able to handle your bandwidth.  The main load on these machines would be if you have multiple incoming VPN connections (i.e. employees, remote workers, etc.), traffic shaping, squid proxy, snort, etc.  Your config probably won't need anything fancy.  Just make sure the box has three network cards and you should be good to go.

It isn't practical to identify the motherboard by running commands in the OS.  The best you can achieve is a list of the devices identified, and then use that list to compare against the spec of motherboards you think it might be, until you find a number of matches - and then guess which one it might me ;) The only realistic option is to pop open the case (you may be able to do that while it's running) and look.