Services not being offered via IPv6

[dsrebnick]

I'm running software version 4.2.3 on a TS-469L.

IPv6 is configured. I'm using automatic configuration and the system gets a link local address on the bond0 interface:

bond0 Link encap:Ethernet HWaddr 00:08:nn:nn:nn:nn
inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0
inet6 addr: fe80::nnn:nnnn:nnnn:nnnn/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:62757 errors:0 dropped:0 overruns:0 frame:0
TX packets:20113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8142086 (7.7 MiB) TX bytes:15297414 (14.5 MiB)

It does not get assigned a global IPv6 address.

The following services are exposed via IPv4:

PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
631/tcp open ipp
2049/tcp open nfs
3306/tcp open mysql
8080/tcp open http-proxy
8081/tcp open blackice-icecap
8200/tcp open trivnet1
30000/tcp open ndmps
49152/tcp open unknown

However, only the following is seen via IPv6:

PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind


Why aren't all the services documented as being supported over IPv6 being exposed to the network?

I've also tried a static IPv6 IP to no avail. Please assist!

[schumaku]

All services are available (and working) for me on IPv6 (link local as well as on static IPv6) on QTS 4.3.2 20170121 (and on QTS 4.3.2.0050). Please post the output of:

Code: Select all

netstat -lp | grep :::

[~] # netstat -lp | grep :::
tcp 0 0 :::nfsd :::* LISTEN -
tcp 0 0 :::shell :::* LISTEN 16200/rsyslogd
tcp 0 0 :::8899 :::* LISTEN 17267/qsyncd
tcp 0 0 localhost:5028 :::* LISTEN 12683/java
tcp 0 0 localhost:5029 :::* LISTEN 12683/java
tcp 0 0 :::rsync :::* LISTEN 16175/rsyncd
tcp 0 0 :::netbios-ssn :::* LISTEN 10058/smbd
tcp 0 0 :::sunrpc :::* LISTEN 18734/portmap
tcp 0 0 :::30000 :::* LISTEN 19359/rpc.mountd
tcp 0 0 :::webcache :::* LISTEN 11109/apache_proxy
tcp 0 0 :::www :::* LISTEN 9099/apache
tcp 0 0 :::30001 :::* LISTEN 19890/rpc.statd
tcp 0 0 :::tproxy :::* LISTEN 9099/apache
tcp 0 0 :::40595 :::* LISTEN -
tcp 0 0 :::ftp :::* LISTEN 11759/proftpd: (acc
tcp 0 0 :::ssh :::* LISTEN 12374/sshd
tcp 0 0 :::631 :::* LISTEN 9602/cupsd
tcp 0 0 :::https :::* LISTEN 12070/apache_proxys
tcp 0 0 :::445 :::* LISTEN 10058/smbd
udp 0 0 :::nfsd :::* -
udp 0 0 :::sunrpc :::* 18734/portmap
udp 0 0 fe80::208:9bff:fece:4af1:ntp :::* 9670/ntpd
udp 0 0 xxxxxx.xxxxxxxx.ch:ntp :::* 9670/ntpd
udp 0 0 ::1:ntp :::* 9670/ntpd
udp 0 0 :::ntp :::* 9670/ntpd
udp 0 0 :::677 :::* 18734/portmap
udp 0 0 :::5353 :::* 30698/avahi-daemon:
udp 0 0 :::30000 :::* 19359/rpc.mountd
udp 0 0 :::30001 :::* 19890/rpc.statd
udp 0 0 :::48626 :::* 30698/avahi-daemon:
udp 0 0 :::55270 :::* -

[dsrebnick]

[~] # netstat -lp | grep :::
netstat: invalid option -- p
BusyBox v1.01 (2017.01.20-17:48+0000) multi-call binary

Usage: netstat [-laenrtuwx]

Netstat displays Linux networking information.

Options:
-l display listening server sockets
-a display all sockets (default: connected)
-e display other/more information
-n don't resolve names
-r display routing table
-t tcp sockets
-u udp sockets
-w raw sockets
-x unix sockets

[schumaku]

Ok, no -p on your Busybox. Try

Code: Select all

netstat -al | grep :::

Is there any service binding in place on your NAS?

[dsrebnick]

Well obviously, see the portscan above for IPv4!

Code: Select all

netstat -al | grep :::

This just returns a prompt.

Here's a portion of the output of netstat -a showing some listening sockets:

tcp 0 0 localhost:58080 *:* LISTEN
tcp 0 0 *:49152 *:* LISTEN
tcp 0 0 *:nfsd *:* LISTEN
tcp 0 0 *:9251 *:* LISTEN
tcp 0 0 *:8200 *:* LISTEN
tcp 0 0 *:netbios-ssn *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:30000 *:* LISTEN
tcp 0 0 *:30001 *:* LISTEN
tcp 0 0 *:8913 *:* LISTEN
tcp 0 0 *:30002 *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 *:50103 *:* LISTEN
tcp 0 0 *:631 *:* LISTEN
tcp 0 0 *:8889 *:* LISTEN
tcp 0 0 *:445 *:* LISTEN

[dsrebnick]

Ah @schumaku, you mean something else by service binding. I'll get to that in a moment.

The problem turns out to be rr load balancing. I got into a chat session with support who suggested I turn off load balancing and IPv6 worked. I then saw the service binding tab, which had not been visible before. So I now understand you were asking something else than I thought.

I tried turning on load balancing again using rr and IPv6 failed again. So I tried alb and that worked. Must be a bug with rr.

Thanks @schumaku for trying to assist.

[schumaku]

I tried turning on load balancing again using rr and IPv6 failed again. So I tried alb and that worked. Must be a bug with rr.

Doubt it...

You are aware Balance-RR requires a managed switch with the two port configured into a static trunk (LAG)? Please review the Switch Required table -> http://docs.qnap.com/nas/4.3/cat2/en/network.htm FMI.

-Kurt.

[dsrebnick]

I was not aware! Thank you for pointing this out.