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:\
>
>
On Fri, Apr 3, 2009 at 3:29 PM, Borowicz, Paul
wrote:
> I have a problem with a vpn between my pfsense box and an ASA box. I've
> noticed the same problem between PIX and pfsense. The VPN works fine, but
> when there is no traffic for awhile it will stop receiving connections. The
> ASA side wi
I used to see this happen a couple years ago when I worked for an ISP.
I agree with Dimitri. Try his suggestion to find out if the ISP (likely the
modem or their DHCP server) is the source of your 10.xxx lease. If you find
this fixes it, then I would try the following:
- Spoof a new WAN MAC ad
The easiest way to see if it's something from the ISP's side is to boot up
your pfSense with the WAN plugged into a switch _all by itself_, or boot up
with a loopback adapter plugged into the WAN port. If it boots up and
doesn't get an IP when it's set up like this, then it's something from the
ISP
Can be anything... you're best off wiresharking the WAN interface during a
reboot to see whether its anything from the outside...
Although, this reminds me of a cable-operator here whose cable-modems are
responsible for answering incoming dhcp-requests using the config they get
via tftp. If one res
