On Mar 24, 2015, at 9:47 AM, Steve Yates st...@teamits.com wrote:
I'm going to start a new thread since I think this is a different issue.
I have a rule to allow all IPv4 from PFSYNC net to PFSYNC net. That
network is on a VLAN with only those two interfaces on it.
To follow up,
True that, just a heads up for the people who do not have any virus scanners in
their network. ☺
Mikey
Van: List [mailto:list-boun...@lists.pfsense.org] Namens Moshe Katz
Verzonden: dinsdag 24 maart 2015 16:57
Aan: pfSense Support and Discussion Mailing List
Onderwerp: Re:
On 03/23/2015 03:03 PM, mayak wrote:
On 03/22/2015 12:38 AM, Bryan D. wrote:
We've had a pfSense-to-pfSense always on IPsec VPN connecting 2 offices since
2008 (pfSense 1.2 IIRC) and it's:
- been ultra reliable (if VPN is down, suspect ISP issue or pfSense box failure)
- it's been quick to
On 23/03/2015 14:34, Christopher CUSE wrote:
On 03/23/2015 03:03 PM, mayak wrote:
On 03/22/2015 12:38 AM, Bryan D. wrote:
We've had a pfSense-to-pfSense always on IPsec VPN connecting 2
offices since 2008 (pfSense 1.2 IIRC) and it's:
- been ultra reliable (if VPN is down, suspect ISP
On 2015-Mar-23, at 7:34 AM, Christopher CUSE cc...@ccuse.com wrote:
just got dropped again -- fourth time in last few hours -- something is
definitely wrong.
upgraded all my pfsenses to 2.2.1 over the weekend.
For me, the VPN drops in the absence of end-to-end traffic ... within
minutes.
Steve Yates wrote on Wed, Mar 25 2015 at 1:22 pm:
In my other thread, diagnosing why failback only moved back the WAN
IPs, if the physical host had its network restarted underneath my router VM.
Sorry, had that backwards FWIW; it only moved back the LAN. Again, not
a normal
