Decided to try from a DVD install.  Now this is really messed up.  It wont even get to the point of where it was hanging before.  Gets to recgonize my keyboard then nothing.  Tried switching the storage mode ACHI/IDE.  Not working.

I'm going to try a 2.1 image.  Perhaps my hardware is too new.

http://www.asrock.com/mb/AMD/E35LM1/

I've installed pfsense on systems from a pentiumII all the way up to core 2 duo's and have never had these problems. 

I've tried all those options.  Hangs at the same place.  All other options also hang at the IPsec (?) config load.

I've waited over a half hour.  Its instant when the internal hard drive is disconnected.

I think its trying to mount the image from the wrong drive.

I get this when installing from USB using both methods of the stickied posts here.

If I disconnect the internal hard drive it loads just fine.  

v2.0.2

I've sucessfully installed Samba on my 2.0 pfsense awhile back but never got around to configuring it.

In many ways pfSense is a victim of it's own popularity and flexibility. 

If this did happen I would probably use it!

Steve

Exactly.  I think people should just stick to what the OP wants and the other poster who offered up another $20.  If it doesnt suit YOUR need then so what?  If this ever comes to be, then dont install it.  Obviously there is a demand out there for it as this is not the first thread I've seen that came up with this. 

I have a pfsense box at the office.  But I also have a dedicated NAS there.  I also have a pfsense here at home that connects site2site vpn.  I'd love to install something like this on the one here at home.  I'd use the crap out of it. 

Do you guys offer live webinars?

Not yet, but soon.

as someone who doesnt visit the forums often, is there some sort of mailing list I can sign up for to be notified of webinars?

Would DHCP Relay match your needs?

It would but....  the server I'm trying to reach is on the other side of my site to site openvpn, and I get this in the system log: 

Code:

php: /services_dhcp_relay.php: The command '/usr/local/sbin/dhcrelay -i ovpnc1 -a -m replace 10.0.1.8' returned exit code '1', the output was 'Internet Systems Consortium DHCP Relay Agent 4.2.1-P1 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Unsupported device type 23 for "ovpnc1" If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting.'

Hi everyone I'm looking for something like IP HELPER.  My understanding is its used to direct broadcasts to a specific machine on another subnet that it wouldnt otherwise get to.

pfsense have this functionality?

Not sure if this belongs here or in the dhcp forum as I understand that its used mostly for this purpose.

Ok using the above info i found that it the ip address ending in 104 was not my old CSS server.  It was the UT3 server that had a port alias of 27000:28000.

Removed it, and redid those port forwards and its all good. 

However it still doesnt explain the weird stuff I was seeing with the FTP servers.  Though that seemed to have stopped this morning as well.

Note to self.... no working on the firewall at 11 at night when you're too tired to see the most obvious things.

In my state table I can still clearly see its pointing traffic on 27015 to my old CSS server even though ALL traces of that config are gone from the firewall.  The port forward is no longer there, the alias is no longer there.

10.0.1.104:27015 <- x.x.127.124:27015 <- x.x.250.159:27390

I have about 15 VM's behind my pfsense v2.0.1 all running multiple game servers at a remote location.  Keeping in mind I also have VPN to this location through OpenVPN

With CS:GO coming out soon I thought it was time to deploy a new VM and install the server.

I was running a CSS server which used the same ports.  I had shut that down.  Removed the port forward entries for that machines as well as the port alias associated with it.

I created a new port alias for CS:GO which contain 27015 and 27005. I forwarded UDP the ports to the new machine using the alias and I cannot connect through the WAN IP.  I turned off Windows Firewall just to be sure. However I can connect through VPN.  Problem must be in the firewall soemwhere.  

Thinking that by some off chance that maybe the game server itself was rejecting some sort of connections I setup an FTP server and had it run on port 2121.  Forwarded that port and same thing.  Cannot connect through WAN, but can connect through VPN.  

I then changed my production FTP server over to port 2121 and changed the port forward ip to that machine.  I could connect through WAN!!  

Changed it back to the CS:GO server (which is still running ftp server on 2121) and cannot connect.  <-------Interestingly though!  Even after applying the port forward change, when I try to connect I can clearly see the FTP admin interface on my production FTP alerting me of a connection!  WTF!  The port forward isnt even on that machine anymore.  Thinking this was way out of whack i removed the port forward for 2121 altogether.  It STILL connects to the production ftp server.  I'm at a total loss.  

I've cleared the states on this thing so nothing is still hanging around.  Rebooted it to clear anything.  I'm stumped!  Any ideas?  

"it" = ?
"config file" = ?

I assume you're referring to what Steve just told me, but just like in the other thread you gave no indication what those things are.

In case anyone else finds this thread, this is what works for me regarding the MaxTerm 8300B, with a 4GB CompactFlash card (SanDisk, if it makes any difference).

1.) Install on the CF card as normal
2.) Boot into safe mode (Option 4 IIRC - you need VGA or console access)
3.) Go to WebConfigurator
4.) Diagnostics > Edit File
5.) Enter '/boot/loader.conf' for the file
6.) The file is blank currently, add 'ahci_load="YES"'
7.) Reboot, should work fine.

I have tried adding ata_dma before and it didn't seem to work, however try adding:

hw.ata.ata_dma="0"
hw.ata.wc="0"

If you still have issues.

SOLVED

1.  Boot pfsense in safemode
2.  Once booted fully enter the shell
3.  i changed folders to /boot
4.  run command

Code:

mount -u /

5.  run command

Code:

vi loader.conf

6.  enter two lines of code supplied by Steve (THANKS!)

hw.ata.ata_dma="0"
hw.ata.wc="0"

7.  save
8.  exit shell
9.  reboot

Now THATS how you write a resolution post.  With the way I named it, this thread will more than likely show up in searches in the future.  Glad we gave a resolution.

Should i create it and add the two lines just like the other one?  You're saying that even if i update that any changes an update might do will not have any effect on the loader?

I'm using the nano 512MB image vga console on a 1GB card.

There is no loader.conf.local.  Should there be one?  Should I make it?