jose thomas schrieb:
Hi all.
I am new to the pfsense list and like to know from your experience
about the pfsense 1.2 installation on a 64-bit hardware.
We are planing to protect the Data Center (consists of around 40+ RH
Servers running Apache and MySQL). Intention is to
install pfsense on
pfSense is based on i386 code so it is only 32-bit. it will run perfectly fine
on a Dell R200.
-Sean
Date: Wed, 20 Aug 2008 09:56:40 +0400From: [EMAIL PROTECTED]: [EMAIL
PROTECTED]: [pfSense Support] 64-bit pfsense
Hi all.I am new to the pfsense list and like to know from your experience
Found part of the problem, I installed a clean pfsense, and setup
again the three interfaces.
WAN-- Connected to our isp trought a /30 private newtork
OP1-DMZ-- With the public range address assigned by our isp
LAN- Private segent.
Nothing configured, I mean, nat, bridge etc.
Added to simple
On Wed, Aug 20, 2008 at 11:56 AM, Aliet Santiesteban Sifontes
[EMAIL PROTECTED] wrote:
Found part of the problem, I installed a clean pfsense, and setup
again the three interfaces.
WAN-- Connected to our isp trought a /30 private newtork
OP1-DMZ-- With the public range address assigned by our
I'd like to configure my pfSense box with 5 NICS
1- WAN1 - x.x.x.169
2- LAN - 192.168.15.1/24 - internal secure network
3- PUBLIC - 192.168.1.1/24 - public wireless network
4- WAN2 - transparent
5- DMZ - transparent - webserver
I have been assigned two blocks of IP's on two separate incoming
Advanced Outbound NAT (Manual Outbound NAT) Menu...Firewall - NAT -
Outbound
You'll need to research this a bit but basically you will need to specify an
interface in which the traffic will be NAT'd, the source network range,
source ports (*) , Destination and Destination ports (*), the address
Hi,
Disabling the FTP-Proxy will stop allowing your clients to access outside
ftp servers.
If you want this, you can disable, otherwise makes no sense.
After some research, i found a problem with some FTP Server running
Microsoft IIS.
Not every server is well setup, and the returned IP from
This is similar to how I had our box configured before our recent ISP
change. It was tricky to set up, but pfSense worked where a PIX/ASA box
basically melted down.
We had Dual WANs, multiple 1:1 NAT entries (w/Proxy ARP across both WAN
subnets), DMZ port and 6 VLANs across 3 physical LAN
Yes,
Advanced Oubound NAT, works fine for me too.
I'd WAN,LAN and VPN interfaces.
Using automatic NAT, the traffic stop flowing in the VPN interface
(Bridging over LAN).
But enabling Manual Outbound NAT, everything works.
Best Regards,
Luiz Vaz
2008/8/20 Curtis LaMasters [EMAIL
Hi all,
I have just had a squid box configured and am about to implement it on on my
network.
I would like to ask you how you suggest I place it and route traffic
accordingly. Is anybody currently using squid boxes with pfsense. I can't use
the onboard package as I have multiple WAN ports.
I recently implemented a pfSense + Squid setup for a school. You'll need to
make sure that the box you're running squid on is on a different interface than
the subnet(s) you want filtered. The rules that redirect traffic destined on
port 80 apply globally to an interface so if your squid box
Hi Tim,
Thank you very much for that feedback. One question. Once I have setup
things as you suggested below, will requests from the squid box out to the
internet cloud be load balanced ?
I.e.: How do I ensure that the outgoing traffic that is not on the proxy
server is load balanced ?
As long as your setup already supports load balancing, it'll continue to do
just that. You're simply redirecting traffic on TCP/80 to another location aka
your squid box. Any traffic that is going to the 'Interwebs' from the squid box
will also be load balanced (assuming proper configuration of
I probably shouldn't introduce any further issues here... but aren't there
issues having a 192.168.1.0/30 and a 192.168.1.0/24 on the same router? If you
ping 192.168.1.1 or 192.168.1.2 from your router, what interface will it route
those requests to?
Tim Nelson
Systems/Network Engineer
On Wed, Aug 20, 2008 at 6:12 PM, Tim Nelson [EMAIL PROTECTED] wrote:
I probably shouldn't introduce any further issues here... but aren't there
issues having a 192.168.1.0/30 and a 192.168.1.0/24 on the same router? If
you ping 192.168.1.1 or 192.168.1.2 from your router, what interface will
On Wed, Aug 20, 2008 at 4:55 PM, Aliet Santiesteban Sifontes
[EMAIL PROTECTED] wrote:
People, here I attach you an image with my current settings and the
migration, is just replace one firewall with pfsense, without changing
anything else. Notice that my wan is a private /30 network only for
Sorry, that was a typo, Wan and Lan are on differents private
networks, really sorry about that, just let me repeat again something
here I guess I have not been clear, current setup don't use NAT at
all, the ISP just use /30 network to connect equipment, and they route
all the public addresses on
17 matches
Mail list logo
