On Fri, Apr 24, 2015 at 12:55 PM, Gregory K Shenaut
wrote:
> On Apr 24, 2015, at 09:55 , Adam Thompson wrote:
>>
>> It's not a routing issue, it's a bug/mis-feature in FreeBSD's IPSec stack.
>> See
>> https://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_
On 2015-Apr-24, at 7:37 AM, Gregory K Shenaut wrote:
> I have two pfSense boxes connected via an IPSEC tunnel.
>
> I'm confused about whether a route gets added automatically to the remote
> network end of an IPSEC tunnel when the tunnel comes up.
>
> However, currently the tunnel can be up,
On Apr 24, 2015, at 09:55 , Adam Thompson wrote:
>
> It's not a routing issue, it's a bug/mis-feature in FreeBSD's IPSec stack.
> See
> https://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN
> for more info.
Ah. Thank you, that makes sense.
Greg
> On Apr 24, 2015, at 09:55 , Adam Thompson wrote:
>
> It's not a routing issue, it's a bug/mis-feature in FreeBSD's IPSec stack.
> See
> https://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewa
It's not a routing issue, it's a bug/mis-feature in FreeBSD's IPSec stack.
See
https://doc.pfsense.org/index.php/Why_can%27t_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN
for more info.
-Adam
On 04/24/2015 09:37 AM, Gregory K Shenaut wrote:
I have two pfSense boxes connected via an IPSEC tunnel.
I'm confused about whether a route gets added automatically to the remote
network end of an IPSEC tunnel when the tunnel comes up. I was under the
impression that there was no need to be concerned with routing between the two
subnets withi
