Project

General

Profile

Actions
Copy link

Bug #38

closed

Settle the fate of net.ipv6.bindv6only in DC

Added by Marc Dequènes about 14 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
Marc Dequènes
Category:
System :: Network
Start date:
2010-04-11
Due date:
% Done:

100%

Estimated time:
Patch Available:
No
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
No
Help Needed:

Description

Spotted problems

Please improve the list and close this ticket only when we are sure everything is OK.

Actions
Copy link
 #1

Updated by Marc Dequènes about 14 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Marc Dequènes over 13 years ago

  • Status changed from In Progress to Blocked
  • Priority changed from High to Normal
  • % Done changed from 30 to 90
  • Security set to No

Only minbif is problematic, but it has been reported upstream. The init script has been patched to use the previous behavior for this service only.

Actions
Copy link
 #3

Updated by Marc Dequènes over 13 years ago

  • Status changed from Blocked to Resolved
  • % Done changed from 90 to 100

No other problem detected, this ticket is no more useful. We will remove the workaround as soon as minbif is fixed.

Actions
Copy link
 #4

Updated by Marc Dequènes over 9 years ago

  • Subject changed from check services having problems with net.ipv6.bindv6only=1 to Settle the fate of net.ipv6.bindv6only in DC
  • Priority changed from Normal to High

Currently Debian reverted this change, see Debian#560238, so it may be unwise to diverge.

Note that not all server have the same settings, so at least we should decide for a unified setting.

Actions
Copy link

Also available in: Atom PDF