So it's all working as you wish now? As I mentioned above when 2.2 is released, or you try a 2.2 pre-release snapshot, there will be a new outbound NAT mode that will function as you expected it to. @https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes: Hybrid outbound NAT style that allows the user to keep the existing automatic behavior but layer manual rules on top of it. Steve

@kenshirothefist: Any other suggestion to accomplish that, besides the one that BBcan17 posted? Could create some phantomjs scripts to automate the process through the pfSense GUI. Not as elegant as an API, but it would work.

@verigoth: Same issue as this? https://forum.pfsense.org/index.php?topic=75163.0 Hello @verigoth Thanks. I'm sorry I did not see.

@abard: Thanks for the input. Jason - I was actually eluding that you could justify, before Cisco, with "Support the Community" logic but with the acquisition, it becomes a dollars and cents decision. BBCan - I'll look into those, appreciate the suggestion. That doesn't make any sense.  You were willing to spend $500 before but not now simply because Snort was bought by a larger company.  Sourcefire was never a not-for-profit and they got paid something fierce when they were purchased (it was almost $3B if memory serves). Anyway, this price is way cheaper than the IDS options on Cisco's ASAs.

Possibly. There seems to be a hard cap at 3Mb and about 2-2.5 on upload. I dont have vLans setup though, but I too cannot find anything in the logs that would give a clue as to where the restriction is. Its very odd… I am not running the proxy in transparent mode as I have a .pac file that points systems to the proxy. I have tried running in transparent mode by manually setting a client PC to pfsense as the gateway, and the problem goes away. Since I will eventually replace my original firewalls with the pfsense ones, this will be a non-issue soon.

in update: I did the Alix firmware upgrade. And I did fresh 2.1.3 install on a new 4G CF card. For now it looks like all is fine again  :) I was thinking to do some extensive testing on the old CF, but lacked motivation (After all, all it took was some time + price of the new CF. Though I really hate problems without hard-pointed cause… >:( I guess I'm going to blame the CF anyway and get over it ::))

This for clients:: http://ltsp.org/ Pfsense would be used for Routing/Firewalling/Proxying….. maybe even Captive portal on Wifi.

And, Possibly VLAN's to segregate your VOIP and DATA traffic.

Hmm, shouldn't this be the other way around? Server host tells you what settings to use? As podilarius said all the settings are in the config.xml file. That includes things you may not want to send to your hosting company.  ;) Steve

Are you booting from that drive while you try to modify it? Or are you booting from CD? You'll have to boot from something else to make that work, I believe.

Awesome!  Thanks for the information!  It's exactly what I was looking for (and confirmation that it wouldn't be do-able in the GUI).

it's a 'feature" from our fruity friends ;)

I managed to install the sudo package as I'm accessing remotely and don't have RSA Keys setup for the root user. The IGMP Proxy was restarted from the command line with: #sudo pfSsh.php playback svc restart igmpproxy I then played around with the cron job tool and have managed to schedule a working IGMP Proxy restart at 01:00 every morning with the following command ran as root: /usr/local/sbin/pfSsh.php playback svc restart igmpproxy Hopefully now the 2 channels which kept going off after a couple of days (Nickelodian and Disney) will stay working and my wife will be off my case. Thanks a lot!!

@priller: Are you trying to reach your CM interface via the commonly used http://192.168.100.1 address? That just works for me with no special configuration.  Always has. Well now I feel like an idiot.  I just assumed that wouldn't work so I didn't even try it.  It works fine, thanks.

The LAN IP can be used for DNS if you have the DNS forwarder (Services->DNS Forwarder) turned on. If you want to make use of the DNS forwarder make sure it's on and change the DNS address given to DHCP clients in the settings of the DHCP Server (Services->DHCP Server) to the LAN IP address.

https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting