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

[BUG] VPN IP address not getting generated in case of IPv6 only envirounment #1936

Open
fti-rbahalaskar opened this issue Dec 18, 2023 · 1 comment

Comments

@fti-rbahalaskar
Copy link

fti-rbahalaskar commented Dec 18, 2023


SoftEther version: 4.29
Component: Client
Operating system: Linux
Architecture: 64 bit

Description

In case of IPv6 only environment in linux system, VPN IP was not getting generated by SoftEther, it's getting empty and there is no steps or configuration available to generate IPv6 VPN IP address.

Expected behavior:
In IPv6 only environment in linux system, user able to generate IPv6 IP address.

Actual behavior:
In IPv4 environment in linux system, i'm able to generate IPv4 VPN IP address and VPN interface with the help of SoftEther vpn client command but after switching to IPv6 only environment the VPN IP address is not getting generated instead it shows empty IP but virtual VPN interface is created.

Steps to reproduce

  1. Switch to IPv6 only environment in linux system.
  2. Run SoftEther vpn client command to generate VPN interface and IP address.
  3. Check VPN interface is created or not.
  4. Check VPN IPv6 IP address is generated or not.
@fti-rbahalaskar fti-rbahalaskar changed the title VPN IP not getting generated in case of IPv6 only envirounment [BUG] VPN IP not getting generated in case of IPv6 only envirounment Dec 18, 2023
@fti-rbahalaskar fti-rbahalaskar changed the title [BUG] VPN IP not getting generated in case of IPv6 only envirounment [BUG] VPN IP address not getting generated in case of IPv6 only envirounment Dec 18, 2023
@PizzaProgram
Copy link

Have You tried manually enable the option at "Security Policy" restrictions:

  • "Disallow DHCP Server Iperation (IPv4)"

Also maybe enabling

  • "Deny Operation as TCP/IP server (IPv4)"

could help. I did not test it ever, so there is a good chance it will not work this way either.

So yes, the DHCP server should be aware of the server's current state of disabled IPv4, so the BUG is valid.
(Actually I hear about this unix feature the first time in my life, so I guess most people did not hear about it either. Also do not really understand the concept of why it would be do any good to disable IPv4 ?)

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

No branches or pull requests

2 participants