Final 6.2.1 update causing LAN instability/sluggishness

mdgm wrote:
jimbo123 your disk's SMART stats look bad though they haven't changed in some time. Can you reproduce this issue if you use a disk from the compatibility list?

I am due to replace the disk in the new year, I only use this NAS for video streaming and relaying data through so there is nothing of note on there, was hoping the last remaining disk would force my hand and break but alas it lives on! I will not be able to replace the disk until the new year unfortunately as I have to wait for the next pay packet before purchase. I am looking to purchase 2 x WD RED WD40EFRX 4TB so in the new year I can certainly try to reproduce.

OptimusPrime wrote:

For the IPv6 address showing inet6 addr: XXXX::2ac6:8eff:fe34:681/64 Scope:Link That is known as link local and exists the moment IPv6 is enabled The packet trace if can take a small window (not huge trace) and send in us same process as send logs would help see what is generating the packets and if really is same issue. The size seems large if you were only rebooted short time, but going to sleep and waking up may not releade and you would need a full reboot cycle I think, but must confirm. Unplug and replug cable for example does not rest the counter.

From what short reading I have managed with regards the counters it would seem that if the counter is held within the kernel then it may not reset with the NAS however, the NAS does appear to reset. I am having to turn off the NAS in order to access the internet and the reading is resetting on reboot -

ifconfig

eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:192.168.1.xxx  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: xxxx::2ac6:8eff:fe34:681/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:683 errors:0 dropped:0 overruns:0 frame:0
          TX packets:525244 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:512
          RX bytes:171646 (167.6 KiB)  TX bytes:556406576 (530.6 MiB)

Once again this is moments after boot.

I have emailed over the log post the NAS completing boot nothing bar Anti-Virus Plus operating. Having read the log it does not appear to show any IPv6 traffic.

After running tcpdump I was curious to see how much of an increase ifconfig recognized...

ifconfig

eth0      Link encap:Ethernet  HWaddr 28:c6:8e:34:06:81
          inet addr:192.168.1.99  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2ac6:8eff:fe34:681/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:81407 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6557582 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:512
          RX bytes:112781611 (107.5 MiB)  TX bytes:2594505207 (2.4 GiB)
          Interrupt:10

This was perhaps 5 minutes after the initial test.

I am curious as to whether there is any way to monitor the NAS prior to boot completion, I have tried SSH prior to boot completion but cannot connect, given that the error happens almost immediately after boot I would query what is able to run prior to complete boot?

Having scanned through the largest and the 002.pcap one tx appears to be the most prominent which is

45	0.021083	192.168.1.XXX	192.230.68.111	TCP	1061	30716→80 [SYN] Seq=0 Win=65535, bogus TCP header length (0, must be at least 20)

This repeats itself some 10,000 times in the space of 10 seconds or so. Perhaps my issue is not IPv6 related...