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.

Sign up for GitHub

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

Jump to bottom

Iptables always uses the wildcard IP to bind HostIP #7891

Closed
Nino-K opened this issue Dec 6, 2024 · 0 comments · Fixed by #7890
Closed

Iptables always uses the wildcard IP to bind HostIP #7891

Nino-K opened this issue Dec 6, 2024 · 0 comments · Fixed by #7890
Assignees
@Nino-K
Labels
area/networking area/wsl WSL integration component/bats BATS tests
Milestone
1.17

Comments

@Nino-K
Copy link
Member

Nino-K commented Dec 6, 2024

The Iptables scanner always uses the wildcard IP 0.0.0.0 to bind to the HostIP, which can cause issues in situations where port mappings are bound to localhost and should not be accessible via other interface IPs. This fix addresses the current Traefik BATS test failure on Windows.
@Nino-K Nino-K added area/networking component/bats BATS tests area/wsl WSL integration labels Dec 6, 2024
@Nino-K Nino-K self-assigned this Dec 6, 2024
@Nino-K Nino-K added this to the 1.17 milestone Dec 6, 2024
@Nino-K Nino-K mentioned this issue Dec 6, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Nino-K Nino-K

Labels
area/networking area/wsl WSL integration component/bats BATS tests
Projects
None yet
Milestone
1.17
Development

Successfully merging a pull request may close this issue.

Fix iptables scanner to assign correct HostIP rancher-sandbox/rancher-desktop
1 participant
@Nino-K