TOS 5.1.67 (X86) is Released for Update

Official news about TOS, mobile app, PC app updates or beta releases
Post Reply
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18
Russia

Re: TOS 5.1.67 (X86) is Released for Update

Post by XFNeo »

{L_BUTTON_AT}TMqiky
Very funny...

Code: Select all

ping 8.8.8.8 -t

Exchange of packets from 8.8.8.8 to 32 bytes of data:
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=65ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
#####Connecting to VPN#####
PING: transmission failed. General failure.
PING: transmission failed. General failure.
PING: transmission failed. General failure.
#####VPN is connected#####
Timed out request.
Timed out request.
Timed out request.
Timed out request.
Timed out request.
Timed out request.
Timed out request.
Timed out request.
#####VPN is disconnected#####
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
Reply from 8.8.8.8: number of bytes=32 time=49ms TTL=60
The same issue on my mobile device and laptop.
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18
Russia

Re: TOS 5.1.67 (X86) is Released for Update

Post by XFNeo »

TNAS:

Code: Select all

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth35f58bf
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 vethbacadd4
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth802eeac
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth659055e
172.10.11.0     172.10.11.2     255.255.255.0   UG    0      0        0 tun0
172.10.11.2     0.0.0.0         255.255.255.255 UH    0      0        0 tun0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-8b137c1fd954
172.20.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-d295c66d1d24
172.21.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-12a9da5f24a5
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
PC with connected VPN:

Code: Select all

#route print
IPv4 route table
===========================================================================
Active routes:
Network address Network mask Gateway address Interface Metrics
          0.0.0.0          0.0.0.0     192.168.31.1   192.168.31.122     25
          0.0.0.0        128.0.0.0      172.10.11.5      172.10.11.6    257
  109.229.119.120  255.255.255.255     192.168.31.1   192.168.31.122    281
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
        128.0.0.0        128.0.0.0      172.10.11.5      172.10.11.6    257
      172.10.11.0    255.255.255.0      172.10.11.5      172.10.11.6    257
      172.10.11.4  255.255.255.252         On-link       172.10.11.6    257
      172.10.11.6  255.255.255.255         On-link       172.10.11.6    257
      172.10.11.7  255.255.255.255         On-link       172.10.11.6    257
     192.168.31.0    255.255.255.0         On-link    192.168.31.122    281
   192.168.31.122  255.255.255.255         On-link    192.168.31.122    281
   192.168.31.255  255.255.255.255         On-link    192.168.31.122    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link       172.10.11.6    257
        224.0.0.0        240.0.0.0         On-link    192.168.31.122    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link       172.10.11.6    257
  255.255.255.255  255.255.255.255         On-link    192.168.31.122    281
===========================================================================
Regular routes:
   Absent

Code: Select all

#tracert 8.8.8.8

Trace route to dns.google [8.8.8.8]
with a maximum number of hops of 30:

   1 45 ms 45 ms 45 ms 172.10.11.1
   2 * * * Request timeout exceeded.
   3 * * * Request timeout exceeded.
   4 * * * Request timeout exceeded.
   5 * * * Request timeout exceeded.
.....
   30 * * * Request timeout exceeded.
Tracing is complete.
User avatar
ERESEN
Posts: 4
Joined: 22 Oct 2020, 18:16
Great Britain

Re: TOS 5.1.67 (X86) is Released for Update

Post by ERESEN »

{L_BUTTON_AT}ERESEN
TMwuu wrote: 09 Sep 2023, 15:44 You can refer to this link to check:viewtopic.php?f=76&t=3815
I have already tried all on that link. Direct access with http://1.1.1.1 example works. But this app can not find it. Regards Eresen
Kind regards
O.T.Eresen
User avatar
ERESEN
Posts: 4
Joined: 22 Oct 2020, 18:16
Great Britain

Re: TOS 5.1.67 (X86) is Released for Update

Post by ERESEN »

Haha.

I tried the last option on a NAS! Reboot. And it worked.

Thanks for the help.

Thanks
Eresen
Kind regards
O.T.Eresen
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18
Russia

Re: TOS 5.1.67 (X86) is Released for Update

Post by XFNeo »

XFNeo wrote: 10 Sep 2023, 19:06 TNAS:

Code: Select all

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth35f58bf
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 vethbacadd4
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth802eeac
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 veth659055e
172.10.11.0     172.10.11.2     255.255.255.0   UG    0      0        0 tun0
172.10.11.2     0.0.0.0         255.255.255.255 UH    0      0        0 tun0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-8b137c1fd954
172.20.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-d295c66d1d24
172.21.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-12a9da5f24a5
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
PC with connected VPN:

Code: Select all

#route print
IPv4 route table
===========================================================================
Active routes:
Network address Network mask Gateway address Interface Metrics
          0.0.0.0          0.0.0.0     192.168.31.1   192.168.31.122     25
          0.0.0.0        128.0.0.0      172.10.11.5      172.10.11.6    257
  109.229.119.120  255.255.255.255     192.168.31.1   192.168.31.122    281
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
        128.0.0.0        128.0.0.0      172.10.11.5      172.10.11.6    257
      172.10.11.0    255.255.255.0      172.10.11.5      172.10.11.6    257
      172.10.11.4  255.255.255.252         On-link       172.10.11.6    257
      172.10.11.6  255.255.255.255         On-link       172.10.11.6    257
      172.10.11.7  255.255.255.255         On-link       172.10.11.6    257
     192.168.31.0    255.255.255.0         On-link    192.168.31.122    281
   192.168.31.122  255.255.255.255         On-link    192.168.31.122    281
   192.168.31.255  255.255.255.255         On-link    192.168.31.122    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link       172.10.11.6    257
        224.0.0.0        240.0.0.0         On-link    192.168.31.122    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link       172.10.11.6    257
  255.255.255.255  255.255.255.255         On-link    192.168.31.122    281
===========================================================================
Regular routes:
   Absent

Code: Select all

#tracert 8.8.8.8

Trace route to dns.google [8.8.8.8]
with a maximum number of hops of 30:

   1 45 ms 45 ms 45 ms 172.10.11.1
   2 * * * Request timeout exceeded.
   3 * * * Request timeout exceeded.
   4 * * * Request timeout exceeded.
   5 * * * Request timeout exceeded.
.....
   30 * * * Request timeout exceeded.
Tracing is complete.
I delete VPN Server, rebooted the NAS and installed it again. It did not help.
The same issue.
But veth* interfaces are disappeared.

Code: Select all

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
172.10.11.0     172.10.11.2     255.255.255.0   UG    0      0        0 tun0
172.10.11.2     0.0.0.0         255.255.255.255 UH    0      0        0 tun0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-8b137c1fd954
172.20.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-d295c66d1d24
172.21.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-12a9da5f24a5
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
User avatar
ostaporomo
Posts: 28
Joined: 02 Sep 2023, 13:23
Finland

Re: TOS 5.1.67 (X86) is Released for Update

Post by ostaporomo »

Hello!
An incompatibility has been detected between my NAS - F2 -223 and NVME SSD - Western Digital WD SN770 (500 GB).
The TOS 5.1.67 does not display the disk temperature. How can I safely use the disk if I cannot control its state?
What do you recommend to do?
Attachments
Снимок экрана 2023-09-11 171404.png
TNAS F2-223
TOS 5.1.79-00214
2x RAM Samsung 16GB DDR4 2133 MHZ
2x HDD Segate IronWolf ST4000VN008 4TB [RAID1]
DAS D4-300
2x HDD Seagate SkyHawk ST3000VX010  [RAID1]
2x HDD Toshiba DT01 DT01ACA300-3TB
User avatar
tommi2day
Posts: 45
Joined: 10 Jan 2023, 02:15
Germany

Re: TOS 5.1.67 (X86) is Released for Update

Post by tommi2day »

For me temperature on nvme drive is visible:
Attachments
Crucial NVME Disk on TOS 5.1.67
Crucial NVME Disk on TOS 5.1.67
main: T9-450
User avatar
ostaporomo
Posts: 28
Joined: 02 Sep 2023, 13:23
Finland

Re: TOS 5.1.67 (X86) is Released for Update

Post by ostaporomo »

tommi2day wrote: 12 Sep 2023, 18:19 For me temperature on nvme drive is visible:
Hello! I'm sure that this is not a bug in the system, but a compatibility problem in the hardware, which should be fixed by editing the drivers
TNAS F2-223
TOS 5.1.79-00214
2x RAM Samsung 16GB DDR4 2133 MHZ
2x HDD Segate IronWolf ST4000VN008 4TB [RAID1]
DAS D4-300
2x HDD Seagate SkyHawk ST3000VX010  [RAID1]
2x HDD Toshiba DT01 DT01ACA300-3TB
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18
Russia

Re: TOS 5.1.67 (X86) is Released for Update

Post by XFNeo »

{L_BUTTON_AT}TMqiky

Why are you always breaking something with a new TOS update?
I have found root cause of broken VPN - it is DDOS protection. When I disable it, internet started working with VPN.
User avatar
XFNeo
Posts: 90
Joined: 10 Oct 2022, 23:18
Russia

Re: TOS 5.1.67 (X86) is Released for Update

Post by XFNeo »

But the most interesting thing that FORWARD chain policy changed from DROP to ACCEPT when I disabled DDoS protection.

Chain FORWARD (policy DROP)
Chain FORWARD (policy ACCEPT)

Before:

Code: Select all

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DOS_PROTECT  all  --  anywhere             anywhere

Chain FORWARD (policy DROP)
target     prot opt source               destination
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain DOCKER (3 references)
target     prot opt source               destination
...

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (3 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain DOS_PROTECT (1 references)
target     prot opt source               destination
RETURN     icmp --  anywhere             anywhere             icmp echo-request limit: avg 1/sec burst 5
DROP       icmp --  anywhere             anywhere             icmp echo-request
RETURN     tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/RST limit: avg 1/sec burst 5
DROP       tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/RST
RETURN     tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 10000/sec burst 100
DROP       tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/SYN
RETURN     icmp --  anywhere             anywhere             icmp echo-request limit: avg 1/sec burst 5
DROP       icmp --  anywhere             anywhere             icmp echo-request
RETURN     tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/RST limit: avg 1/sec burst 5
DROP       tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/RST
RETURN     tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 10000/sec burst 100
DROP       tcp  --  anywhere             anywhere             tcp flags:FIN,SYN,RST,ACK/SYN
After:

Code: Select all

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DOS_PROTECT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain DOCKER (3 references)
target     prot opt source               destination
...

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere

RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (3 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain DOS_PROTECT (1 references)
target     prot opt source               destination
Post Reply

Return to “Update Notice”