no problem. PFSENSE rocks and i have "turned" at least 3 people onto this and we have been using since 1.2.3 and started testing 2.0 and have not looked back. :)

Nice to hear! Thanks for your feedback. Have fun :-)

Are you using the ip address of the server or a dns to reach it? Just a thought…

thanks! :)

thanks i will try it!

Have you read this: http://doc.pfsense.org/index.php/Interface_Bridges Not much there though. You shouldn't need to select static/dhcp etc for bridged interfaces, they will all take their values from the interface you're bridging to. Steve Edit: You could read through this thread as well. Edit: Hmm, I going to have to play around with this but from reading through this stuff it seems you have to: Create a bridge interface, br0. (you'll need to assign at least one interface to it) Assign br0 to be LAN. Add other interfaces to the bridge. This seems to be causing much confusion and I can why since it seems more logical to create a bridge and then add the lan interface to it. I'll be very interested to see how this works out for you.

Fastest way is to get a packet capture of 2000-3000 packets or so, download the pcap and use Wireshark's analysis tools.

Binding should be to all IPs by default, unless you've changed that on the server in which case you'll have to go in and change every service. I would expect you would lose access to one interface or the other because of the routing complications dual homing induces, though both would work from the same subnet. If the services are inaccessible from both IPs you have something weird going on with the server (host firewall maybe?).

Did I put this in the wrong forum? :)

Yes, this can be done, with slight modifications to your plan.  If you place the proxy servers inside a separate network segment, you can then intercept the outbound HTML traffic and redirect it, either load balanced or in a failover configuration to your proxy servers.  We did exactly this configuration for a client who was pushing sustained 100mb through that system and it works flawlessly in 1.2.3.  If I remember correctly, there were some minor modifications that needed to be done to pfSense in order to support load balancing from a CARP IP and that work was done by the BSDPerimeter guys under contract (can't recommend their work highly enough btw).  I suspect all this can be done off the shelf inside pfSense 2.0, but I've never set it up.  As always, the limitation of this setup is that only HTTP, HTTPS will not proxy transparently.

Usually that indicates that it can't send traffic there. Either because it doesn't have permission (blocked by firewall rules) or perhaps because it doesn't have a default route going that way.

Thank you Cry Havoc and Gimp. I don't know why but email is working fine now. I wish I knew why that ws happening but I can't even reproduce it to try checking things. I guess it's just one of those "ghost in the machine" things. Thanks again!!

The root user is the admin user. Set the key for the admin user in the GUI, it works for root. FYI: root and user share the same uid and home directory, they just have different shells.

Unless you have something else tracking your internal usage (squid, netflow, etc) there isn't likely to be any kind of record you can refer to for that. pfSense doesn't keep a log of every incoming/outgoing connection, and even if you made the rules log every connection it may not give you the info that you would need to match up the information they gave with internal activity.