Portál AbcLinuxu, 11. května 2025 09:24
# show running
# show ip route static
# show log
show ip route static 192.168.17.0/32 is subnetted, 1 subnets S 192.168.17.16 [1/0] via 0.0.0.0, Virtual-Access3 S 192.168.2.0/24 is directly connected, Tunnel10 S 192.168.18.0/24 is directly connected, Tunnel10 S* 0.0.0.0/0 is directly connected, Dialer0pokud se připojuji vzdaleně prostřednictvím vpn tunelu tak se to tváří na mém serveru /pomocí tcpdump/ že k tomu ciscu přistupuji z IP 192.168.17.* . Je tedy možné že když na tom ciscu nemám naroutovanou síť 192.168.4.0 /což je síť za mým linux-routerem / tak mi to spojení padá při přenosu objemnějších dat ?
*Mar 26 06:54:30.423: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=IP_CISCO_ROUTERU, prot=50, spi=0x568963EA(1451844586), srcaddr=IP_LINUX_ROUTERUtohle se obejevuje /mnoho řádku / v show log
show crypto isakmp sa show crypto ipsec sa show crypto engine connection active debug crypto isakmp debug crypto ipsecInfo ohledně chyby:
IPsec Packet has Invalid SPI This output is an example of the error message: %PIX-4-402101: decaps: recd IPSEC packet has invalid spi for destaddr=dest_address, prot=protocol, spi=number The received IPsec packet specifies a Security Parameters Index (SPI) that does not exist in the security associations database (SADB). This could be a temporary condition due to: Slight differences in the aging of security associations (SAs) between the IPsec peers The local SAs having been cleared Incorrect packets sent by the IPsec peer This might also be an attack. Recommended Action: The peer might not acknowledge that the local SAs have been cleared. If a new connection is established from the local router, the two peers can then reestablish successfully. Otherwise, if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer's administrator.
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.