what should i say. after all i tried at last i did it. and by the by i want to give thnx those two brothers. thnx guys. now i wanna tell you how i solve the problem. First I changed my hard disk. I mean sata to IDE. Then I make it Primary hard disk. before my sata hard disk was third primary hard disk and my dvd room was primary. so i change it to primary. i am sure if i can make sata as a primary then i can do it with sata also. My all problem was about to set of primary and secondary.thnx guys. take care

1.2-Release is based on FreeBSD 6.2 Various 1.2 snapshots may be based on 6.2 or 6.3 1.2.1-BETA and 1.3-ALPHA are based on 7.0 Only 1.2-Release is what I would consider a stable release (though 1.2.1 and the 1.2 snapshots may be stable enough for you).

Hey, Thanks for the advice - we were already doing something very similar before, but tried things exactly as suggested here (plus set the DHCP server address, and tried a different network card for the wan interface) and something must have worked because it seems to be running fine now :) we were assigned an address and it's been great ever since. pfSense definitely solved the problem of the crappy VM-supplied netgear router not being able to handle torrenting (and barely being able to handle 20meg in general). Cheers guys!

@ToxIcon: Hi all I am new to pfsense and have a couple of question do pfsense block all inbound connection by default after installation or do i have to set it up to do so. It does, why would anyone create a firewall software that didn't do just that on default installation  ::)

I've fixed this now. My PFSense box is bridging with my DG834. I've assigned a public ip to the WAN NIC card & the LAN NIC Card. All my points point there gateway to the LAN NIC card which is then bridged to the WAN NIC. Everything appears tobe OK.

Hello, Is this helps? : http://forum.pfsense.org/index.php/board,37.0.html cheers,

@m.econome: I installed version 1.2 on a VIA 501+ … On the console screen it shows the interfaces with configured IPs, if names etc. on top. Do both interfaces you're using have a  '*'  behind their names? Like:   WAN*                     ->   fxp0    ->      12.34.56.789(PPPoE)   OPT1(WLAN)            ->   xl0      ->      10.0.1.1   LAN*                      ->   fxp1    ->      192.168.1.1   OPT2(DMZ)*            ->   fxp2    ->      10.0.2.1 This would show a detected link at least and serve as a starting point for further trouble shooting. I have no link at the OPT1(WLAN) if in the example given above.

@soul710: still theres one issue. when booting, the machine hangs like 3 minutes when synching system time. is that normal? I think part of what is happening here is that the system is synchronizing over the network with an external time server (ntp). Perhaps in your case it is timing out. "Like 3 minutes" seems a bit long for that pause but its a while since I restarted my box.

A driver from a 6.3 kernel won't work with a 6.2 kernel - you need to use the same kernel and platform.

Thanks for your help as well!

Oooops, it happened to me several times… ;D Have fun m8! cheers,

http://forum.pfsense.org/index.php/topic,11016.msg61193.html#msg61193

The VLB sync patches you are referencing are for FreeBSD 4.x The structure of FreeBSD 6 (pfSense 1.2) and 7 (pfSense 1.2.1/1.3) is sufficiently different and the patches will not work. This is why I settled on m0n0wall 1.2 (based on FreeBSD 4) to run on my FireBox III. The only way to get the hardware working under modern FreeBSD would be to involve a developer familiar with the ata code, and I'm not sure there is much interest in getting this fixed. I saw someone was working on an OpenBSD based m0n0wall fork, but have not tried it. You could check it out here: http://www.thewaffle.org/

http://forum.pfsense.org/index.php/topic,7001.0.html

Thx a lot…..everything works fine now...

http://forum.pfsense.org/index.php/topic,7001.0.html –> http://devwiki.pfsense.org/OpenVPNasWAN

If the switch were ASUS GigaX 1024P then it's a bit confusing. Although the spec sheet doesn't say anything about .1Q but it does support .1Q, tag-base and/or port-base vlans. Eagleeye, you may want to configure your ASUS switch correctly, via CNM. Check your CNM manual, pp35, 4.7.5 VLAN setup.

I had the similar problem related to boot-time freezing related to several reasons. I had to enable the legacy USB support to fix that issue (provided that your BIOS allows that setting). For further setup hint, look at your MoBo and pull out every PCI/e etc device to see if the system boots normally (Live-CD) . Introduce the cards (and USB driven devices such as CF cards) one by one to see which one is the problem. I have Jetway J7F4K1G2E and BIOSTAR GF8200 M2+ (with AMD Athlon X2 -45W & Intel dual NIC pci-e) for my firewall/proxy. Jetway MoBo did not work with the PCI network cards. All sorts of freezing came down to PCI card issue. Still do not know why (although I have a hunch that it could be related to filmsy PCI extender or PCI-memory-overlap). I used a USB ethernet adapter to make it work. Go figure! For the Biostar MoBo I had legacy USB support issue as well. Also EHCI handout disabling needed. Good luck!