|
||||||||||
Hello all, Is anyone seeing any issues with dn/loading a backup of the config file ? .. When attempted to dn/load I get a PHP file rather than the XML file as I have in the past .. Also we are now seeing these errors via our IPSec clients SafeRemoteLT, it will normally go away after a few hours or so .. 2-12: 19:12:43.364 2-12: 19:12:43.635 My Connections\ABS m0n0wall - Initiating IKE Phase 1 (IP ADDR=10.10.10.254) 2-12: 19:12:43.795 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK AG (SA, KE, NON, ID, VID 5x) 2-12: 19:12:43.965 My Connections\ABS m0n0wall - RECEIVED<<< ISAKMP OAK AG (SA, KE, NON, ID, HASH, VID) 2-12: 19:12:44.025 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK AG *(HASH, NOTIFY:STATUS_INITIAL_CONTACT) 2-12: 19:12:44.025 My Connections\ABS m0n0wall - Established IKE SA 2-12: 19:12:44.035 MY COOKIE 77 1c 50 d0 f0 54 d0 ed 2-12: 19:12:44.035 HIS COOKIE 7 6c 71 8c 74 fa 2f 62 2-12: 19:12:44.086 My Connections\ABS m0n0wall - Initiating IKE Phase 2 with Client IDs (message id: B615A003) 2-12: 19:12:44.086 Initiator = IP ADDR=192.168.1.102, prot = 0 port = 0 2-12: 19:12:44.086 Responder = IP SUBNET/MASK=192.168.2.0/255.255.255.0, prot = 0 port = 0 2-12: 19:12:44.086 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 2-12: 19:12:44.246 My Connections\ABS m0n0wall - RECEIVED<<< ISAKMP OAK QM *(HASH, SA, NON, KE, ID 2x) 2-12: 19:12:44.246 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK QM *(HASH) 2-12: 19:12:44.356 My Connections\ABS m0n0wall - Loading IPSec SA (Message ID = B615A003 OUTBOUND SPI = 949FF1E INBOUND SPI = 1495CE8B) 2-12: 19:12:44.356 2-12: 19:12:46.329 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:46.339 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:49.233 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:49.243 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:52.327 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:52.327 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:55.242 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:12:55.242 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:16.652 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:19.596 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:22.581 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:25.595 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:31.654 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:39.925 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:42.820 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:43.641 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:45.894 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:48.828 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) 2-12: 19:48:54.897 My Connections\ABS m0n0wall - SENDING>>>> ISAKMP OAK INFO *(HASH, NOTIFY:INVALID_SPI) Any ideas ?? Brian |