Tom Eastep <[email protected]> a écrit :
On Wed, 2011-06-29 at 20:39 +0200, Laurent Caron (Phone) wrote:
>
> The config is exactly the same however.
> Just with 2 isps it stays stuck.
Shorewall does not change the ipset configuration. It simply reports it
via 'setkey -D' and 'setkey -DP'. The output from 'setkey -DP' (which
dumps the IPSEC policy database) is completely different in the two
dumps. So something else is changing that has nothing to do with
Shorewall.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \_____________________________________________
_____________________________________________
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2_____________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
So it might be an openswan bug when dealing with multiple default routes?
--
Envoyé de mon téléphone.
Excusez la brièveté.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
