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

IPv4 [0.0.0.0] can't be dualstack #108

Open
dontcrash opened this issue Apr 29, 2024 · 2 comments
Open

IPv4 [0.0.0.0] can't be dualstack #108

dontcrash opened this issue Apr 29, 2024 · 2 comments

Comments

@dontcrash
Copy link

dontcrash commented Apr 29, 2024

Had some issues on an Ubuntu VM with Netplan and IPv6 forcing it to wait for network on boot every single time, so I disabled it in grub.
py-kms now refuses to run and spits out an error, even when I manually specify 0.0.0.0 as the IP to bind to.

I believe the issue lies in the pykms_Server.py srv_options array:

'dual' : {'help' : 'Allows listening to an IPv6 address also accepting connections via IPv4. Deactivated by default.',

'def' : True, 'des': "dual"}

This line should be False by default (if the description is to be believed).

@didotb
Copy link

didotb commented Apr 29, 2024

If you've changed it on your repo and works, you could submit a PR to update this repo.

Had some issues on an Ubuntu VM with Netplan and IPv6 forcing it to wait for network on boot every single time, so I disabled it in grub.

I got curious though, was the wait description on boot something along "Wait for network to be configured"? I had the same problem last week, I just followed this and I didn't have to disable anything in grub.

@dontcrash
Copy link
Author

If you've changed it on your repo and works, you could submit a PR to update this repo.

Had some issues on an Ubuntu VM with Netplan and IPv6 forcing it to wait for network on boot every single time, so I disabled it in grub.

I got curious though, was the wait description on boot something along "Wait for network to be configured"? I had the same problem last week, I just followed this and I didn't have to disable anything in grub.

Yes it was, I may have a look at iptables, could be something funky there.
Will submit a PR to this repo.

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 a pull request may close this issue.

2 participants