Why I cannot disable IPv6 autoconfiguration even if the sysctl values are set to this?

net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.default.accept_ra = 0
net.ipv6.conf.all.accept_ra = 0
net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.enp2s0.accept_ra = 0
net.ipv6.conf.enp2s0.autoconf = 0
net.ipv6.conf.enp2s0.use_tempaddr = 0
net.ipv6.conf.all.use_tempaddr = 0
net.ipv6.conf.default.use_tempaddr = 0

Thank you for your help.

I have a strange situation here. If anyone can help, please do so.

We're talking about a Linux Box running as Router using Ubuntu 18.04.3 LTS, with 2 interfaces: "lan" - which connects to my internal LAN and "wan" - which connects to my ISP.

However, my ISP requires PPPoE connection, so, basically, the "wan" interface is used only a starter for the ppp0 interface.

My problem is that I cannot get IPv6 global address on this server.

I am able to successfully connect to my ISP. I already followed the tutorial from here: http://gruffi.be/mediawiki/index.php/Ipv6_with_PPPoE_on_Ubuntu , but it doesn't work for me.

So, here is what I did:

1. /etc/ppp/options:

   +ipv6 ipv6cp-use-ipaddr
   

2. /etc/sysctl.conf:

   net.ipv6.conf.all.forwarding=1
   
   net.ipv6.conf.ppp0.accept_ra=2
   

3. /etc/wide-dhcpv6/dhcp6c.conf:

   interface ppp0 {
   
       send ia-pd 2;
       send ia-na 1;
   };
   
   # Use subnets from the prefix with id 0
   id-assoc pd 2 {
       prefix-interface lan {
           # Assign subnet 1 to eth0
           sla-len 8; # <----- BELANGRIJK: 8 omdat ons klein net 64 en ons groot 56 is en dat het verschil is
           sla-id 2;
       };
   };
   
   id-assoc na 1 { };
   

4. /etc/radvd.conf:

   interface lan
   {
       AdvSendAdvert on;
       prefix ::/64
       {
           AdvOnLink on;
           AdvAutonomous on;
           AdvRouterAddr on;
       };
   RDNSS 2001:4860:4860::8888  2001:4860:4860::8844
           {
                   # AdvRDNSSLifetime 3600;
           };
   };
   

My ISP told me that it doesn't use Router Advertisement, however it uses DHCPv6 Prefix Delegation and offers /64 subnets.

The problem is that I tried more configs from the net, non of them worked for me.

When I "ifconfig ppp0", it says:

inet 1.2.3.4 ...
inet6 fe80::xxxx:yyyy

No sign of a global IPv6 address.

If I turn on debugging on wide DHCP client and I examine /var/log/syslog, I see that it tries to send Solicit messages to ff02::1:2%ppp0 and the timers reset. I get no reply.

However, router advertisements are working, both on "ppp0" and on my internal lan, because I have a Default Route: "default via fe80::1" when I "ip -6 r". However, no global IPv6 address.

I suspect it something to do with DHCP. The address is not obtained correcly.

I can ping:

ping6 fe80::1%ppp0
64 bytes from...

But when trying to "ping6 google.com", it says: "Beyond scope of source address"

I need to do 2 things, in the long run:

1. Try to get a global IPv6 address on "ppp0" so my websites can be accesible from IPv6 addresses (DNS already taken care of)

2. I need to forward whatever /64 prefix my ISP gives me, let's say: "2001:abcd:dead:beef::/64" to my internal computers, but using a fixed part for the internal computers.[/COLOR]

For example:

Computer 1: 2001:abcd:dead:beef::1/64
Computer 2: 2001:abcd:dead:beef::2/64
Computer 3: 2001:abcd:dead:beef::3/64

I do NOT want EUI-64 addresses, NOR do I want Private Addresses. I want my computers assigned an ORDERly IPv6 address with the prefix given, regardless of the dynamic prefix.

For example, after reboot, I might get "2001:1234:beef:dead::/64". I want the same Host-part allocation using "::1", "::2", and so on...

Thank you !

Can someone tell me what this means, and how to fix it? Ubuntu 18.04.

Dec  4 14:37:16 myserver systemd-networkd[28369]: enp2s0: DHCPv6 address xxxx:xxxx:xxxx:xxxx::49/128 timeout preferred 3600 valid 3600

Lots of these in the log.

My server is connected to a network which supports ipv6, however, it can't connect to any ipv6 address. Ping6 returns a message "network is unreachable." and curl ipv6 don't work as well. How to check whether my network really supports ipv6 and if so, how to let my server connect to it?

My server's dhcp.conf:https://termbin.com/3gjh Linux 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I and trying to restart wide-dhcpv6 and I get this in the journalctl

Feb 03 12:09:49 router sudo[1285]: ciaran : TTY=pts/0 ; PWD=/home/ciaran ; USER=root ; COMMAND=/bin/systemctl restart wide-dhcpv6-client
Feb 03 12:09:49 router sudo[1285]: pam_unix(sudo:session): session opened for user root by ciaran(uid=0)
Feb 03 12:09:49 router systemd[1]: Stopped LSB: Start/Stop WIDE DHCPv6 client.
-- Subject: Unit wide-dhcpv6-client.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wide-dhcpv6-client.service has finished shutting down.
Feb 03 12:09:49 router systemd[1]: Starting LSB: Start/Stop WIDE DHCPv6 client...
-- Subject: Unit wide-dhcpv6-client.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wide-dhcpv6-client.service has begun starting up.
Feb 03 12:09:49 router wide-dhcpv6-client[1288]:  * Starting WIDE DHCPv6 client dhcp6c
Feb 03 12:09:49 router dhcp6c[1293]: ifreset: invalid interface(enp0s31f6): No such device
Feb 03 12:09:49 router dhcp6c[1293]: main: failed to initialize enp0s31f6
Feb 03 12:09:51 router wide-dhcpv6-client[1288]:    ...fail!
Feb 03 12:09:51 router systemd[1]: wide-dhcpv6-client.service: Control process exited, code=exited status=1
Feb 03 12:09:51 router systemd[1]: Failed to start LSB: Start/Stop WIDE DHCPv6 client.
-- Subject: Unit wide-dhcpv6-client.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wide-dhcpv6-client.service has failed.
--
-- The result is failed.
Feb 03 12:09:51 router systemd[1]: wide-dhcpv6-client.service: Unit entered failed state.
Feb 03 12:09:51 router systemd[1]: wide-dhcpv6-client.service: Failed with result 'exit-code'.

its trying to use an interface that was in my config file but I renamed it and replaced the name in my config

ciaran@router:/etc/wide-dhcpv6$ cat dhcp6c.conf
##
## This is/etc/wide-dhcpv6/dhcp6c.conf
##
## Replace the existing configuration with this one.

# Send a PD request on the external facing interface
# send ia-pd says ask for a prefix
# the script is run when the prefix is acquired
interface wan0 {
 send ia-pd 2;
 script "/etc/wide-dhcpv6/dhcp6c-script";
};

# Upon receiving a prefix use the
# information to set the internal facing interface
id-assoc pd 2 {
 prefix-interface wlan0 {
  ifid 1;
  sla-id 1;
  sla-len 0;
 };
};

## End of config.

any idea why its attempting to use the wrong interface?