Project

General

Profile

Bug #8

MOBIKE selects disappearing IPv6 address

Added by Martin Willi about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
charon
Target version:
Start date:
Due date:
Estimated time:
Affected version:
5.9.0
Resolution:

Description

In the ikev2/mobike UML scenario, roadwarrior alice is connected with 192.168.0.50 (eth1) to the 192.168.0.0/24 network. eth1 also has an IPv6 address fec0::5.

At the beginning an IPv4 tunnel from 192.168.0.5 (alice) to 192.168.0.2 (sun) is established.
When eth1 is disabled, first 192.168.0.5 goes away and alice immediately starts the MOBIKE
protocol on fec0::5 trying to connect to fec0::2 (sun) but never receives an answer probably because the IPv6 address also went down a split second later. When this event is detected, alice does not try to connect to 192.168.0.2 (sun) via the eth0 interface 10.1.0.10 and router moon.
ip xfrm policy shows chaotic entries on alice.

Question: should a switch from IPv4 to IPv6 be allowed if there are other IPv4 alternatives?

History

#1 Updated by Martin Willi about 13 years ago

Oops, there is a typo in the ikev2/mobike scenario URL.
Please use [http://www2.strongswan.org/uml/20070702-2148/ikev2/mobike/]

#2 Updated by Andreas Steffen about 13 years ago

  • Status changed from New to Closed
  • Affected version set to fixed

Also available in: Atom PDF