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

Add the possibility to send the Virtual Hub Name to an external DHCP server #133

Merged
merged 15 commits into from Nov 27, 2016

Conversation

@yehorov
Copy link
Contributor

yehorov commented Feb 10, 2015

No description provided.

@dnobori dnobori force-pushed the SoftEtherVPN:master branch from 67fbd56 to 64fd19e Feb 12, 2015
@dnobori
Copy link
Member

dnobori commented Sep 6, 2015

Your great patch is much appreciated. We are considering to apply your patch into the SoftEther VPN main tree.

SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch

You have two options which are described on the above policy.
Could you please choose either option 1 or 2, and specify it clearly on the reply?

@yehorov
Copy link
Contributor Author

yehorov commented Sep 6, 2015

I'm choosing "Option1: Allowing us to apply the same patch into PacketiX VPN".
Thanks.

@dnobori dnobori merged commit 5f8ce28 into SoftEtherVPN:master Nov 27, 2016
@dnobori dnobori mentioned this pull request Nov 27, 2016
@dnobori
Copy link
Member

dnobori commented Nov 27, 2016

Thank you so much for your contribution to enrich the SoftEther VPN source code.

Your patch has been merged on the main source-tree of SoftEther VPN.

As a token of our gratitude, your GitHub username has been added on the AUTHORS.TXT file and on the header of the related source file.
Please see: https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/AUTHORS.TXT

Thanks again for your contribution.

@jacac
Copy link

jacac commented Sep 14, 2018

I could not get this to work. Wireshark does not report any option 77 set. Is this only working in a SecureNat environment with an external DHCP Server?

@yehorov
Copy link
Contributor Author

yehorov commented Sep 14, 2018

You need to switch the UseHubNameAsDhcpUserClassOption on to enable this functionality.

@jacac
Copy link

jacac commented Sep 14, 2018

Yes, this was enabled and still not getting the user class identifier set. A restart of the service was also performed.

The AssignVLanIdByRaduisAttribute is also enabled. Could it be that the DHCP traffic is handled differently if VLANS are used?

@yehorov
Copy link
Contributor Author

yehorov commented Sep 14, 2018

If you can see DHCP requests and responses in tcpdumps, then VLAN processing doesn't affect DHCP traffic.
Could you show your configuration?

@jacac
Copy link

jacac commented Oct 2, 2018

Thanks yehorov for looking into this. I had finaly more time to troubleshoot this. Here are my results:

With IPsec I can see the user class defined in the DHCP Discover packet. Using the Softether VPN client Ver 4.25 the user class is not added.

Is this feature only for IPsec connections?

@jacac
Copy link

jacac commented Oct 3, 2018

This is the Virtual Hub configuration. As far I remember most of the settings are default except for UseHubNameAsDhcpUserClassOption and radius authentication.

VPN HUB.txt

@jacac
Copy link

jacac commented Oct 12, 2018

Upgraded the VPN Manager and see now in the description that it is only available for L2TP/IPsec. Thanks for looking into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.