NSA325v2 - no IPV6 with latest kernel / debian

Hi again,

is there something special i have to do to enable ipv6 support? All my other machines are getting an inet6 ip but the nas does not.

root@debian:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 5c:f4:ab:de:f2:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.45/24 brd 192.168.178.255 scope global eth0
       valid_lft forever preferred_lft forever

azriel,

Have you tried

modprobe ipv6

and/or put it in the modules loading section during boot?

Did it work before? ipv6 has been configured as a module for a long time in my kernel releases.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

i tryed it before but no difference. But lsmod lists ipv6 after boot so i think the module is loaded.

The system is maybe 2 weeks old (with your debian + kernel, thanks for that btw :-)). Recently i wanted to install openvpn and because my provider is ipv6 native i noticed the missing inet6 ip.

Maybe i have done something wrong? I enabled systemd and later updated the kernel (4.12.1 -> 4.18.4).

What is your output of

ifconfig -a

Quote

systemd

That could be the difference :) I don't use systemd.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/26/2018 05:16AM by bodhi.

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.45  netmask 255.255.255.0  broadcast 192.168.178.255
        ether 5c:f4:ab:de:f2:fa  txqueuelen 1000  (Ethernet)
        RX packets 20408  bytes 5558920 (5.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5739  bytes 2732450 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 35

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2921  bytes 331842 (324.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2921  bytes 331842 (324.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Is there a way to go back to sysinit? Or should systemd be disabled if i have set bootargs like so:

setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params

I have no uEnv.txt in /boot. But last time i tryed the uEnv.txt in /boot the custom_params were not read there and i had to fw_setenv:

fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params init=/bin/systemd'

Then i wanted to go back to sysinit but systemd stayed active.