If I was looking to understand what was going on I would start with:
1. What does "didn't work" really mean? Is too vague a problem description to be useful. A description along the lines of "I did … and I saw ... but I expected to see ..." is much more informative and may even give some hints that help resolve the mystery. Additional information might immediately answer some of the following questions.
2. Is there another system on the network using 1.2.3.122? Perhaps the upstream router? 
3. Does an ftp access to 1.2.3.122 actually arrive on the correct pfSense interface for the port forwarding? A packet capture can help verify this.
4. Does the port forward go to the correct system? A packet capture could help answer the question.

Wally Bob,

Thanks for the help...

To test this I used an on-line ftp tester, ftptest.net, which is really helpful.  I put in my external IPs, it either connected successfully or it didn't.  That's what I mean by "didn't work".

I decided to wipe out my pfSense machine and reinstall from scratch.  So many changes have been made with all the testing and moving it in and out of production, etc., so I thought it might be best to start with a clean install.

I just completed the reinstall.  First thing I tried was ftp coming in to two different IPs.  Not a surprise, it works fine.

Thanks,

Julien

Disabling gateway monitoring is fine for local gateways. There is no benefit to monitoring them.

You really only need to monitor WAN-facing gateways.

Thanks for the reply again :)

Learning to set up VLANs are not a problem for me, it's a skill I was hoping to learn anyways, however I thought my switches supported VLAN tagging, and it seems they do not, so I think a new hardware order is in my future, haha.

Thanks everyone for all your help :D

My BIL gave me the Dell Dimension 2400 I'm using for my pfSense box and 4600 I use for my everyday computer running FreeBSD 9.0. Both were originally running XP but he had taken the HD out of each and had them sitting in his basement.

I had taken the 13.6GB HD out of a Gateway PC and replaced it with an 80GB Seagate around 2000 and used them both for the Dell's. I don't want to jinx myself, but neither have given me any problems over the past 3 months I've been using them since.

because WAN is the only required interface. WAN is the only interface on single interface appliance-type deployments. Nothing prevents you from assigning em1 as WAN and em0 as LAN.

What is your host os/ Dom0? Virtualizer/Emulator/Hypervisor?

Some OSs love to cache. This is good.

@wallabybob:

So nobody takes the previously quoted set of IP addresses as definitive

Yes, re-reading my previous post I failed to make it clear that anyone doing this must do it themselves locally in order to get a useful set of IPs. The IPs used by Youtube (or any large distribution network) will vary geographically. Wallabybob and I are about as geographically separated as possible but you get the idea.  ;)

Steve

Try without squid.

That's fine, empty always means defaults as Steve noted. If a field is required, we force you to fill it in, it'll kick back an input error if you leave fields that must be filled in blank.

Yep that seems to have done the trick for the strange timestamps  ;)
cheers

I am using both manual outbound NAT, but my optimization is set to normal. I am running Cisco phones. I have heard that polycom phones are more forgiving.

@robpal:

Stephenw10as a test i ssh'd into my pfsense with putty and key as usual and then from there pressed F8 for a shell and ssh'd into my linux box - though maybe a key auth for this one is overkill at the mo seen as though you need to get into my pfsense with a key to access the linux box i the 1st place??

Not sure if that's a question but I would agree, no point in having key authentication on the second stage. In fact it's better not to do that. If somneone cracks the key on your ssh session to your pfSense box they would then have the key for your linux box since it would have to be stored on the pfSense box unless you copied it across every time.

The advantage of using an ssh tunnel or just nested ssh sessions is that ssh is pretty much omnipresent in the unix world so it requires almost no setup.
I haven't really researched it in security terms but as far as I know SSH with key based authentication is considered secure. As secure as a VPN? Depends on the vpn encryption used. I'm open to opinions.

Steve

Out of inodes is either something (would have to be a package) has gone wild and created a huge number of small files (usually you run out of disk space before you run out of inodes, unless there is a huge number of small files). The other alternative is what Jim mentioned, a failing HD or CF will at times cause out of inodes messages rather than the more common read and/or write errors.

@jimp:

http://doc.pfsense.org/index.php/Why_can%27t_I_view_view_log_files_with_cat/grep/etc%3F_%28clog%29

GOSH… i'm sorry :-X

Thanks!
You saved my day.

I forgot I had it set to Manual and the source was still the old Lan subnet.
Works as a charm now.

/Nicklas