View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003909Kali LinuxGeneral Bugpublic2017-03-07 09:532018-02-21 09:41
Reporteredermi Assigned To 
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version2016.2 
Summary0003909: Settings (disabling IPv6) in sysctl.conf are not applied after reboot
Description

In order to disable IPv6, I followed the guidelines from Debian wiki [1] and added following lines to /etc/sysctl.conf:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1

After running "sysctl -p", IPv6 is disabled (checked with "ip a", interfaces do not have an IPv6 address anymore). Unfortunately, after a reboot IPv6 is enabled again which should clearly not be the case.

[1] https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6

Steps To Reproduce
  1. Disable IPv6 by appending following lines to /etc/sysctl.conf:
    net.ipv6.conf.all.disable_ipv6 = 1
    net.ipv6.conf.default.disable_ipv6 = 1
    net.ipv6.conf.lo.disable_ipv6 = 1
    net.ipv6.conf.eth0.disable_ipv6 = 1

  2. sysctl -p

    The output contains the settings that were applied.

  3. ip a

    Shows all local interfaces and the assigned addresses. There shouldn't be any IPv6 addresses anymore

  4. reboot

  5. ip a

Expected outcome:
After 5.), there shouldn't be any IPv6 addresses assigned to the interfaces

Actual outcome:
After 5.), link-local addresses were assigned to the interfaces

Additional Information

I initially configured the interfaces via network-manager, so I'm not quite sure how this is supposed to behave. I selected "only link-local" in the IPv6 configuration of the interfaces since I found no way of disabling it completely. In my opinion, a kernel setting should be prefered over a network manager setting.

Activities

g0tmi1k

g0tmi1k

2018-02-21 09:41

administrator   ~0008711

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.1), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2017-03-07 09:53 edermi New Issue
2018-02-21 09:41 g0tmi1k Note Added: 0008711
2018-02-21 09:41 g0tmi1k Status new => closed