At the very least upgrade to 1.2 release, if not to 1.2.2.  You'll get no meaningful help for a beta or release candidate.

Restore to factory defaults, run the initial configuration wizard.  The system handles initial setup for you.

Download a file with name like pfSense-1.2.3-20090129-0009.iso.gz, unzip it with winzip (or the like) to a file with a name like pfSense-1.2.3-20090129-0009.iso
and use your CD burning program (Nero or the like) to burn a CD from this ISO image.

It might help to see exactly what command line you are using for scp and the error that results. Or try it exactly how I did in my prior post. I'm not doubting your ability to use the commands, I just think that some extra clarification and information will help.

It works fine for me with via fish as well:

fish://root@192.168.1.1/etc/inc/

Pulls up a list of files in /etc/inc, though I had to wait a few seconds for it to prompt me about accepting the key and then a few more seconds to enter the password.

Problem solved by applying patch from GIT. If someone need this patch to, I can send patched file by e-mail.
TNX to cmb and perry for help.

Sasa

Glad it helped  :)

From /etc/passwd:

root:*:0:0:Charlie &:/root:/bin/sh admin:*:0:0:Admin User:/root:/etc/rc.initial

Root's shell is /bin/sh and has a .profile that calls /etc/rc.initial, but things like scp can still bypass .profile and execute another command.

Admin's shell is /etc/rc.initial directly, so it is locked into running that on each login.

http://forum.pfsense.org/index.php/topic,7001.0.html
Maybe this one:
http://devwiki.pfsense.org/FTPTroubleShooting

You may be able to get some pointers from my setup - Obviously I have a procurve switch and not a Cisco but the principles are the same,

http://www.cheesyboofs.co.uk/home.htm

procurve.jpg
procurve.jpg_thumb

Sorry to bump such an old thread, not had the time to look at this until last weekend.

I am now pretty certain that the issue is with the NIC, or Pfsense, and the AP and DHCP works fine through the LAN interface. I've tested different cables and all work fine through the LAN interface.

DHCP just isn't server through the OPT1 interface. I am going to try swapping the interfaces to try to pinpoint what the issue may….

OK swapping had no impact, and the NIC only had an amber light not green light. I am fairly certain the NIC is ok, pretty sure I used it with Fedora before I installed Pfsense on this box.

So now I'm thinking the onboard and Pfsense don't play well together - is there a way to get them to play nice?!

If you don't have control of the router, you have to wait for their arp-cache to expire. Although it will be cleared if the provider's router just happens to get power cycled accidentally. You could also call them and ask them to clear it.