General

Profile

Brian Pruss

  • Registered on: 23.05.2012
  • Last connection: 22.05.2014

Issues

Activity

22.05.2014

18:50 strongSwan Wiki edit: AttrPlugin (#6)

13.03.2013

14:35 strongSwan Feature #312: Feature Request: Option to limit or disable sending of ADDITIONAL_*_ADDRESS list for MOBIKE Responder
I found that option in my research, but from the description in http://wiki.strongswan.org/issues/185 it didn't sound...
03:31 strongSwan Feature #312 (New): Feature Request: Option to limit or disable sending of ADDITIONAL_*_ADDRESS list for MOBIKE Responder
When configured as a responder with MOBIKE enabled, StrongSwan currently sends a set of ADDITIONAL_IP4_ADDRESS and/or...

20.02.2013

21:33 strongSwan Issue #288: StrongSwan-sourced DPDs coming from wrong IP address
Thanks for the help you've provided. Just to put some closure on the issue, we ended up changing the routes to point ...

07.02.2013

04:37 strongSwan Issue #288: StrongSwan-sourced DPDs coming from wrong IP address
Is there any additional information that would be helpful regarding this issue? Conversely, is there something we sho...

31.01.2013

05:31 strongSwan Issue #288: StrongSwan-sourced DPDs coming from wrong IP address
From the logs, it appears that StrongSwan is using the global routing table to source DPD packets instead of the SA's...
04:48 strongSwan Issue #288 (Closed): StrongSwan-sourced DPDs coming from wrong IP address
Background: We have a StrongSwan-based VPN gateway, to which multiple remote road-warrior endpoints are connected. Th...

14.12.2012

17:27 strongSwan Feature #263: Feature Request: NAT-T keepalive interval configuration for IKEv2
You are correct. For some reason I wasn't finding it after doing searches on the Wiki or through Google. Sorry for th...

13.12.2012

16:45 strongSwan Feature #263: Feature Request: NAT-T keepalive interval configuration for IKEv2
You're correct, of course, in that it would be difficult for an outside observer to tell the difference between NAT-T...
03:56 strongSwan Feature #263 (Closed): Feature Request: NAT-T keepalive interval configuration for IKEv2
In Pluto, the interval between NAT-T keepalives was configurable using the keep_alive parameter in the ipsec.conf con...

Also available in: Atom