What's new

102.7 Alpha Builds available

Status
Not open for further replies.
Tried to install and run the ControlD Command Line Daemon (https://docs.controld.com/docs/ctrld). The script appears to install properly. When I try and start the ctrld service, I get a "ctrld: not found" error. I reverted to 102.6 firmware and everything works as expected.
This happens to me after first installing ctrld because the shell script directory just got added to a startup script that modifies the PATH environment variable. However, PATH itself is not actually modified upon completed installation.

Upon router reboot the issue is solved because PATH is now correctly including the /jffs/controld directory from that point forward.
 
Last edited:
My RT-AX68Pro losses the VPN more often than with the 102.6 stable version
 
Last edited:
On alpha 2 with RT-BE92U nearly all of my 5GHz devices drop off all at the same time due to WPA handshake failures and then requires me to restart the devices or turn on/off the wireless radios to reconnect. Had one of the 2.5GHz devices needing to be power cycled to reconnect to the network. Noticed if I stay on the General Log page too long, it eventually reports as unresponsive.
 
similar i should have saved the logs.. one of my wyzse cams was unabled to be pinged. rebooting didnt fix it.. log showed multiple connect disconnectsw per sec with reason other./unknown.. reboot of the router fixed it but i rolled back to release as i have never had this issue previously.
 
Zero change to anything related to wireless in 102.7 except for the GT-BE19000AI. There has been no GPL or SDK merge for any of the other models. People reporting wifi issues, your issues have absolutely nothing to do with this alpha release.
 
i believe you.. i think it may be a security issue even though i have no security turned on.. the router blocking the device from connecting.. i will post logs if it happens again.
 
Could someone please check this: In my configuration files for WireGuard clients, the brackets "[ , ]) around the IPv6 address for the endpoint are missing:

[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0
Endpoint = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:51820
PersistentKeepalive = 25

This prevents configuration via QR code or by importing the file into the Android client. If I manually add the brackets to the file, the import works perfectly.

Sorry if this has already been posted here. I'm a bit late and I haven't read the whole thread.

EDIT: an configuration file from RT-BE88U it`s working as expected!
 
Last edited:
Could someone please check this: In my configuration files for WireGuard clients, the brackets "[ , ]) around the IPv6 address for the endpoint are missing:

[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0
Endpoint = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:51820
PersistentKeepalive = 25
If it detects a valid IPv6, it should be adding the brackets.
 
Could someone please check this: In my configuration files for WireGuard clients, the brackets "[ , ]) around the IPv6 address for the endpoint are missing:

[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0
Endpoint = xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:51820
PersistentKeepalive = 25

This prevents configuration via QR code or by importing the file into the Android client. If I manually add the brackets to the file, the import works perfectly.

Sorry if this has already been posted here. I'm a bit late and I haven't read the whole thread.

EDIT: an configuration file from RT-BE88U it`s working as expected!
It could be the WAN DHCPv6 bound6 event is overwriting the correct entry. It doesn't pay any attention to whether the Endpoint was enclosed in brackets or not.
@Dedel66 If you restart the Wireguard server, do the brackets return? Or run service "restart_wgcs 1" where 1 is the number of the WG server (I'm guessing a bit since I don't use this at all).
 
Last edited:
It could be the WAN DHCPv6 bound6 event is overwriting the correct entry. It doesn't pay any attention to whether the Endpoint was enclosed in brackets or not.
@Dedel66 If you restart the Wireguard server, do the brackets return? Or run service "restart_wgcs 1" where 1 is the number of the WG server (I'm guessing a bit since I don't use this at all).
You guessed correctly!!!
Immediately after the router starts (including the WG server), there are no brackets in the configuration file:

"...
[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AllowedIPs = 0.0.0.0/0
Endpoint = xxxx.xxxx.xxxx.xxxx.xxxx.xxxx:51820
PersistentKeepalive = 25"


The brackets appear after restarting the WG server:

"...
[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AllowedIPs = 0.0.0.0/0
Endpoint = [xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]:51820
PersistentKeepalive = 25"

The QR code also works perfectly.
 
Beta is out:
 
Status
Not open for further replies.

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top