SHA-1 problems to other routers
-
Hi, After much much messing around with trying to connect IPSec sha-1 to drayteks and watchguards(real ones).
I think I come to the conculsion that maybe there is a problem with sha-1 in pfsense 2.0.1
After coming across other peoples issues on this forum with sha-1 this is what I did.
1. drayteks (2600v) were connecting fine using 3des sha-1 to watchguards and other drayteks- rock solid…
2. remove 1 draytek and put in pfsense (on a watchguard x500) at the sub office
3. try and re-establish connections with drayteks watchguards and pfsense(watchguard)Result IPSec comes up, no routing, nothing. :(
change from sha-1 to md5 connection comes up, routing possible. :)no other changes were need...
Anyone have and experiences of there own on this?
Thanks
Chris -
I haven't seen that, but I don't think I've used those models. Though I've seen people connect with all kinds of other devices using sha1: cisco, sonicwall, juniper, etc, etc.
-
I can confirm that issue with SHA1 and our Watchguard XTM for a Site-to-Site VPN ???
Crazy to me is that another box running pfSense version 1.2.3 is working perfectly since a long time using SHA1 and same settings (except PSK and WAN stuff of course). It appears as the tunnel is up-n-running but in fact to traffic is going through.
My solution is so far changing to MD5 instead on both, Phase 1and 2. After that every thing is OK immediately. :o
Would like to see this can be fixed some how as I don't know if i'm missing a security option or anything alike.
