Re: [pfSense] IPSec not routing traffic over tunnel

2018-02-09 Thread Mark Wiater
On 2/9/2018 6:42 AM, Roland Giesler wrote: Ok, I'll try again with real (fake) addresses to make it better understood. WAN gateway: 197.212.127.194 (primary firewall interface), next hop gateway 197.212.127.193 Phase1: Interface: Virtual IP 41.22.123.70 Phase2: Local address: address

[pfSense] dnsmasq packages

2017-10-03 Thread Mark Wiater
Hi, Has anyone heard when we might see new dnsmasq packages available? Hoping to be able to do a pkg update and get that fixed up. Thanks Mark ___ pfSense mailing list

Re: [pfSense] massive CARP Failover

2017-06-07 Thread Mark Wiater
On 6/7/2017 10:10 AM, Daniel wrote: > Hi, > > the Sync interface is connected directly without a Switch. > But Carp is running WAN/LAB for example. Let's go back to your original email, this behavior can be duplicated with different software, it's not a pfSense issue. Is that right? Both Sophos

Re: [pfSense] Restoring at remote location before deployment

2017-05-18 Thread Mark Wiater
On 5/17/2017 3:44 PM, Steven Spencer wrote: All, When restoring a configuration for a site, we often do so from the home office and then deploy after we are sure hardware is working as expected. That means that we are restoring a backup and then on reboot, their is no active WAN (because the

Re: [pfSense] OpenVPN users no access to LAN - HA pfSense Setup

2017-05-12 Thread Mark Wiater
On 5/12/2017 12:49 PM, Steve Yates wrote: -Original Message- Hey guys, last night I did my first HA installation of 2 XG-2758 appliances. It worked great, my only issue is with OpenVPN Remote Access. At first it wasn't working on the WAN VIP because I had OpenVPN listening on the

Re: [pfSense] Running newer then released?

2017-03-03 Thread Mark Wiater
On 3/3/2017 8:45 AM, Yılmaz Bilgili wrote: 03-03-2017 15:38 tarihinde Doug Lytle yazdı: My home pfSense is reporting: 2.3.3-RELEASE (amd64) built on Thu Feb 16 06:59:53 CST 2017 FreeBSD 10.3-RELEASE-p16 The system is on a later version than the official release. Same with me. Didn't we

[pfSense] SNMP & Carp

2017-01-25 Thread Mark Wiater
Hi, I'm aware of this link [ https://forum.pfsense.org/index.php?topic=45973.0 ] that says that carp interfaces can be monitored like any other interface, however it seems like perhaps that's changed in more recent versions. When I snmp walk the interfaces in a 2.3.2p1 installation, I only

Re: [pfSense] Unable to Retrieve Page Information

2016-08-02 Thread Mark Wiater
On 8/2/2016 2:58 PM, Ron Lemon wrote: I am on Community Edition 2.3.1-RELEASE (amd64) This weekend I added the new replacement for VNSTAT2 (Traffice Totals I think it is now called). Any suggestions on how to fix this? Yes, I had the same problem. The day after 2.3.2 was releaseed, and I

Re: [pfSense] Errors when attempting upgrade to 2.3.2 from 2.3.1.5

2016-07-26 Thread Mark Wiater
I installed a package this morning, Openvpn-client I think, on a 2.3.1_5 machine, after that I couldn't see updates nor any package listings, locally installed or otherwise. >From ssh on one of the 2 machines impacted, I did a pfSense-upgrade -d and waited for a very long time until it completed

Re: [pfSense] IPSec nat issue

2016-05-27 Thread Mark Wiater
On 5/27/2016 3:57 PM, Lyle Giese wrote: > unsure how easy that might be. Couldn't you eliminate the conflict by re-addressing your 192.168.1/24 to something else in rfc1918 land? -- Mark Wiater ___ pfSense mailing list https://lists.pfsense.

Re: [pfSense] IPSec nat issue

2016-05-26 Thread Mark Wiater
On 5/26/2016 2:09 PM, Rosen Iliev wrote: > The other end has a conflict with our LAN addressing(192.168.1.0/24). > So in phase 2, we setup a Tunnel IPv4 using 193.168.1.0/24 for the > local Network. NAT/BINAT network of 192.168.85.0/24. Their remote > network is 192.168.75.0/24. It's probably

Re: [pfSense] Recipe to safely allow remote SIP phones to connect a local asterisk PBX?

2015-12-28 Thread Mark Wiater
On 12/28/2015 10:08 AM, Andrew Martin wrote: > I agree that this is ideal (both for security and ease of configuration), > however note that I am using an OpenVPN setup on pfSense with Yealink > phones and Asterisk and have run into intermittent quality problems where > audio will drop out for

Re: [pfSense] Recipe to safely allow remote SIP phones to connect a local asterisk PBX?

2015-12-23 Thread Mark Wiater
On 12/23/2015 12:43 PM, James Ronald wrote: > Is anyone aware of a pfSense config/recipe to safely allow remote SIP > phones to connect a local asterisk PBX? If you have the option of using OpenVPN on the phones (Grandstream, Yealink, Snom & maybe others?) that might be better than the

Re: [pfSense] Gateway failures, how to access everything behind it still so that I can debug?

2015-06-19 Thread Mark Wiater
On 6/19/2015 12:49 PM, Chuck Mariotti wrote: Are you asking how to connect into your rack from outside the data center? pfSense does have a CARP feature where a second firewall can be set up for failover. It needs a few things like three WAN IPs for the routers (1, 2, and