TOS 6.0.420 Beta Is Available for Testing

[TMzethar]

Question to TM: Is there a setting I can change to allow Special Characters (!@#$% etc...) in my User's passwords?

We connected to the SMB server using the special character you mentioned as the password and it connected successfully.
Maybe it has something to do with your password combination, please change the letters and numbers in your password, keep the position of the special characters the same, and then tell us the changed password string to verify it.

[thierrys73]

hello

i update to 6.0.436 from 6.0.420
the notifications are always broken and test send email too

cordialy

[fcs001fcs]

Question to TM: Is there a setting I can change to allow Special Characters (!@#$% etc...) in my User's passwords?

We connected to the SMB server using the special character you mentioned as the password and it connected successfully.
Maybe it has something to do with your password combination, please change the letters and numbers in your password, keep the position of the special characters the same, and then tell us the changed password string to verify it.

User Name: TestUser -- Assigned to NAS share "Test" with Read/Write access
Original Password: Test0001@$& - Not Working
Then modified password to: Test0001!? - Working
Then modified to: Test0001@ - Working
Then modified to: Test0001$ - Working

So, the issue seems to be the Ampersand "&. I did have the Ampersand in my previous TOS .299 User passwords and there were no problems.

[fcs001fcs]

Question to TM: Is there a setting I can change to allow Special Characters (!@#$% etc...) in my User's passwords?

We connected to the SMB server using the special character you mentioned as the password and it connected successfully.
Maybe it has something to do with your password combination, please change the letters and numbers in your password, keep the position of the special characters the same, and then tell us the changed password string to verify it.

User Name: TestUser -- Assigned to NAS share "Test" with Read/Write access
Original Password: Test0001@$& - Not Working
Then modified password to: Test0001!? - Working
Then modified to: Test0001@ - Working
Then modified to: Test0001$ - Working

So, the issue seems to be the Ampersand "&. I did have the Ampersand in my previous TOS .299 User passwords and there were no problems.

BTW - Then modified to: Test0001& - Not Working

[abs1ck]

Help me ))

Hi guys,

After updating the TOS to build 420, I have been unable to deploy a Pi-hole container, and I noticed that port 53 is already occupied by the systemd-resolved service. My router does not support configuring DNS queries to a non-standard port, so I cannot change the port for Pi-hole.

Could you please advise on how to properly set up Pi-hole in this situation? Is it possible to move the systemd-resolved service to another port or configure Pi-hole to work alongside the existing configuration?

I would also appreciate any recommendations for alternative solutions that could help me use Pi-hole without port conflicts.

Thank you for your assistance!

[fcs001fcs]

802.3ad Dynamic Link Aggregation - Not Working on F4-423 NAS

On prior versions of TOS (last was 6.0.229) I setup 802.3ad Dynamic Link Aggregation (Bond the 2 LAN Ports) and it worked fine.

I did a fresh install of TOS 6.0.420 Beta and I cannot get the Bonding to work.

I removed the setups on both the NAS and the Ubiquity Switch (USW-Lite-16-PoE) and followed the instruction on the switch as to setting up the NAS first with the Bond in "Network-Interface" TOS settings and then the switch ports on the Ubiquity switch.

It would not work once I tried to set it up and I lost connectivity. I needed to disconnect the NAS LANs and then connect to a normal non-aggerated port on the switch (Port 7) to regain access to the NAS.

My setup was working fine on TOS 6.0.229.

Question to TM: Is the Bonding using the 802.3ad protocol working on the F4-423 with TOS 6.0.420 Beta? Are there other commands (CLI) I need to use to get the Bonding working?

[Alex281]

Is the Bonding using the 802.3ad protocol working on the F4-423 with TOS 6.0.420 Beta?

I also lose all connectivity when attempting to bond with 802.11ad. F4-424. Switch is Unifi USW-16-poe on newest EA firmware.

[TMroy]

i update to 6.0.436 from 6.0.420
the notifications are always broken and test send email too

What specific problem did you encounter? Is it that the notification failed to send? Or the notification was sent successfully, but you cannot receive it?
Do you have any screenshot for the error?

[Alex281]

Is the Bonding using the 802.3ad protocol working on the F4-423 with TOS 6.0.420 Beta?

I also lose all connectivity when attempting to bond with 802.11ad. F4-424. Switch is Unifi USW-16-poe on newest EA firmware.

Updated to 6.0.436 and LACP seems to be working now.

[thierrys73]

i update to 6.0.436 from 6.0.420
the notifications are always broken and test send email too

What specific problem did you encounter? Is it that the notification failed to send? Or the notification was sent successfully, but you cannot receive it?
Do you have any screenshot for the error?

The red message is :fail to send to t*****@aol.com