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

[RFE] sssd shouldn't use ipv6 if it is disabled #1945

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

[RFE] sssd shouldn't use ipv6 if it is disabled #1945

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/903


Description of problem:
If ipv6 is unavailable for your network, and the system has NETWORKING_IPV6=no
marked in /etc/sysconfig/networking, SSSD still tries to use ipv6
automatically. SSSD should be intelligent enough to not try to use ipv6 if it's
marked disabled.

Version-Release number of selected component (if applicable):
sssd-1.5.1-34.el6.x86_64

How reproducible:
intermittent

Steps to Reproduce:
1. set up SSSD
2. disable ipv6 via adding NETWORKING_IPV6=no to /etc/sysconfig/network
3. try to authenticate

Actual results:
timeouts occur because ipv6 is not enabled on the network

Expected results:
ipv6 dns requests should not occur

Additional info:
You can currently disable ipv6 for a service if you manually enter
lookup_family_order=ipv4_only.

https://bugzilla.redhat.com/show_bug.cgi?id=714993

This is not required earlier than next year this setting 1.7 right away.

Comments


Comment from dpal at 2011-07-22 21:55:36

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0


Comment from mkosek at 2011-12-16 16:00:40

Fields changed

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=714993 714993]


Comment from dpal at 2012-01-16 16:40:09

"Nice to have" for 1.9.

blockedby: =>
blocking: =>


Comment from dpal at 2012-02-09 15:24:27

Fields changed

feature_milestone: =>
milestone: SSSD 1.9.0 => SSSD Deferred


Comment from dpal at 2017-02-24 15:01:22

Metadata Update from @dpal:

  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:22:28

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.


Comment from pbrezina at 2020-03-24 14:22:29

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant