Actions
Bug #7041
closedNot all mobile IPsec phase 2 entries pass traffic through the correct interface
Status:
Rejected
Priority:
High
Assignee:
-
Category:
VPN (Multiple Types)
Target version:
-
Start date:
12/26/2016
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:
Description
My phase 2 configuration is as follows:
VLAN 10 [Home]- 192.168.1.0/24
VLAN 12 [VMs] - 10.1.2.0/24
VLAN 13 [Legacy] - 10.1.3.0/24
Azure - 10.0.5.0/24
The device on the other end is running Android with the native IPsec client. Only the 192.168.1.0/24 VLAN subnet is accessible over the IPsec tunnel. None of the other phase 2 traffic is being passed.
States:
IPsec icmp 10.0.100.1:218 -> 10.0.5.4:218 0:0 1 / 0 84 B / 0 B IPsec icmp 10.0.100.1:220 -> 10.0.5.4:220 0:0 1 / 0 84 B / 0 B IPsec icmp 10.0.100.1:221 -> 10.0.5.4:221 0:0 1 / 0 84 B / 0 B IPsec tcp 10.0.100.1:37926 -> 10.1.2.18:80 SYN_SENT:ESTABLISHED 6 / 11 360 B / 660 B IPsec tcp 10.0.100.1:37927 -> 10.1.2.18:80 SYN_SENT:ESTABLISHED 6 / 11 360 B / 660 B IPsec tcp 10.0.100.1:38436 -> 10.1.2.16:80 CLOSED:SYN_SENT 7 / 0 420 B / 0 B IPsec tcp 10.0.100.1:38437 -> 10.1.2.16:80 CLOSED:SYN_SENT 7 / 0 420 B / 0 B IPsec tcp 10.0.100.1:47377 -> 10.1.2.1:80 SYN_SENT:ESTABLISHED 7 / 11 420 B / 660 B IPsec tcp 10.0.100.1:47378 -> 10.1.2.1:80 SYN_SENT:ESTABLISHED 7 / 11 420 B / 660 B HOME tcp 10.0.100.1:48095 -> 192.168.1.19:8080 ESTABLISHED:ESTABLISHED 74 / 43 17 KiB / 13 KiB HOME tcp 10.0.100.1:48158 -> 192.168.1.19:8080 ESTABLISHED:ESTABLISHED 37 / 20 8 KiB / 6 KiB
As you can see above, the tunnel is sending the traffic through the wrong interface for the 10.1.2.0/24 and 10.0.5.4/24 subnet.
Files
Updated by Jim Pingle over 8 years ago
- Status changed from New to Rejected
Most likely a configuration error. Please post on the forum for discussion before opening a bug report.
Actions