Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send CISCO FLexVPN vendor ID #180

Closed
wants to merge 1 commit into from

Conversation

Thermi
Copy link
Contributor

@Thermi Thermi commented Jul 24, 2020

Send CISCO FLexVPN vendor ID if send_cisco_flexvpn_vendor_id is set to "yes".
Option description:
Send the CISCO FlexVPN vendor ID. It is required in order to make CISCO brand devices allow negotiating a local_ts (from strongSwan's point of view) that is not the assigned "virtual" IP address, if a "virtual" IP address is requested by strongSwan. Sending the CISCO FlexVPN vendor ID makes the CISCO peer allow this peer to negotiate a TS of 0.0.0.0/0 == 0.0.0.0/0 instead (unknow if it works for IPv6 too). This has been tested with a "tunnel mode ipsec ipv4" CISCO template but should also work for GRE encapsulation.

…o "yes".

Option description:
charon.send_cisco_flexvpn_vendor_id = no
	Send the CISCO FlexVPN vendor ID. It is required in order to make CISCO
	brand devicesallow negotiating a local_ts (from strongSwan's point of view)
	that is not the assigned "virtual" IP address, if a "virtual" IP address is
	requested by strongSwan. Sending the CISCO FlexVPN vendor ID makes the CISCO
	peer allow this peer to negotiate a TS of 0.0.0.0/0 == 0.0.0.0/0 instead
	(unknow if it works for IPv6 too). This has been tested with a "tunnel mode
	ipsec ipv4" CISCO template but should also work for GRE encapsulation.
@Thermi
Copy link
Contributor Author

Thermi commented Jul 25, 2020

Check failures are unrelated to the PR.

@tobiasbrunner
Copy link
Member

Thanks, Noel. I've pushed a modified version of your patch to the cisco-flexvpn-vendor-id branch (renamed the option to match that for Cisco Unity and modified description and commit message).

Do you know of any documentation of this feature/vendor ID from Cisco? While I found some documentation of FlexVPN, this particular vendor ID is never mentioned.

@Thermi
Copy link
Contributor Author

Thermi commented Sep 5, 2020

Thank you for pushing it to that branch.

Other than that, which I just found, I have no documentation.
The behaviour was discovered by observing behaviour and checking against the sent vendor IDs.

@tobiasbrunner
Copy link
Member

Other than that, which I just found, I have no documentation.

Thanks. Interesting, the workaround (only visible after logging in) actually refers to strongSwan and sending the VID payload to fake support for FlexVPN.

@johnfzc
Copy link

johnfzc commented Sep 23, 2020

That bug was was opened in response to a support ticket I created with Cisco about the issue, you can use this public link for a more cursory description of the issue without a Cisco support account. It's a request for an improvement that would allow a Cisco side configuration to permit clients to use the 0.0.0.0/0 tunnel selector instead of forcing the remote side selector to use of the assigned IP when the VID is not received.

There is no other public documentation of this behaviour that I am aware of; there was another bug but I can't locate it. I believe the support team identified the cause of the issue from the IOS source code. I'll update the issue if I can obtain any other public information about it.

@tobiasbrunner
Copy link
Member

Thanks for the update.

@Thermi Thermi deleted the cisco-flexvpn-vendor-id branch April 11, 2021 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants