Hello all!
We have faced the following problem:
after the upgrade of pfSense from 1.2-Release to 1.2.3-RC1, the access from the
internal LAN1 network to FTP-server, located in DMZ, seized functioning (in both
modes: active/passive) (via the LAN2 network).
The scheme of access:
LAN1 --> Router
On Sat, Apr 4, 2009 at 9:06 PM, Chris Buechler wrote:
>
> There is another issue where TCP is always selected when you edit an
> existing pool, haven't fixed that yet but will.
>
Just fixed, diff here.
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/fe4df9b7b635cea04eb409a328f0a44
.us/portal
-Original Message-
From: cbuech...@gmail.com [mailto:cbuech...@gmail.com] On Behalf Of Chris
Buechler
Sent: Saturday, April 04, 2009 6:07 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] RE: Load Balancer Using TCP
On Thu, Apr 2, 2009 at 12:22 AM, Nathan Eisenb
On Thu, Apr 2, 2009 at 12:22 AM, Nathan Eisenberg
wrote:
> Here's what ends up in slbd.conf when I save my config:
>
>
>
> servicename:\
>
> :poolname=poolname:\
>
> :vip=x.x.x.x:\
>
> :vip-port=80:\
>
> :sitedown=x.x.x.x:\
>
> :sitedown-port=80:\
>
>
Given the log, I would say that they are set for TCP and not ICMP. On some
versions of pfSense, I have noticed that the option box reverts to TCP from
ICMP when you edit the service a second (or subsequent) time. Have another
look-betcha it's set to TCP.
Also, you might want to post what versio
Here's what ends up in slbd.conf when I save my config:
servicename:\
:poolname=poolname:\
:vip=x.x.x.x:\
:vip-port=80:\
:sitedown=x.x.x.x:\
:sitedown-port=80:\
:method=round-robin:\
:services=2:\
:service-port=80:\
:0=192.168
