 meowBB
join:2002-01-21
Hayward, CA | reply to jdmt
Re: USG 100 3.0 - VPN Issues? My L2TP works and site to site ipsec works in v3.
»USGs firmwares |
|
| Some people, I among them, seem to have a working connection but a flawed routing, ending up with IPSec errors like
SPI:0x0 SEQ:0x0 No rule found, Dropping packet [count=152]
My routing is an incoming tunnel for Default_L2TP_VPN_Connection for any user, dest, etc. Next hop is Auto and DSCP masking set to preserve, and the SNAT is outgoing-interface.
This worked under 2.20. Can it be the culprit now? |
|
jdmtPremium
join:2002-05-06
Seattle, WA | reply to meowBB
Good to hear your's is still working - just curious, do you see IKE and IPSEC activity in your logs? On my device, no IKE or IPSEC logs are generated during the "connection attempt" which leads me to believe no attempt is actually being made. Curious if that is a symptom of possibly another issue in of itself. |
|
meowBB
join:2002-01-21
Hayward, CA | said by jdmt:Good to hear your's is still working - just curious, do you see IKE and IPSEC activity in your logs? On my device, no IKE or IPSEC logs are generated during the "connection attempt" which leads me to believe no attempt is actually being made. Curious if that is a symptom of possibly another issue in of itself.
Yes, I see the IKE logs. I thing you can try is to clean all the browser cache and cookies before the upgrade. Then, clean all the cache and cookies after the upgrade. If that still doesn't work. Then you can try to load the default settings to v2.22 then do a upgrade as "Brano" suggested. |
|
tollota
join:2012-04-02
Alexandria, OH | reply to gargamel
I have the same issue, with an usg100 (3.00(AQQ.0) / 1.08) but routing from Lan1 to ipsecVPN.
He says:
Error / IPSec / SPI:0x0 SEQ:0x0 No rule found, Dropping packet [count=3] / 192.168.18.10 / 192.168.54.254
Policy Route was set from "any" to "net-54" and next hop to "vpn-tunnel" and "vpn-54"
Before changing the firmware version, it worked... |
|
