Search results

Stop it

Lol. Happy New Year to you as well!!

Try this to see if it works for you. First create this test script called doubleknock.sh in /jffs/scripts/: #!/bin/sh logger -t "doubleknock.sh" "Sensitive command executed by double knock" Make it executable:chmod 755 /jffs/scripts/doubleknock.sh Add this to your /jffs/addons/knock.d/knock.cfg...

Knock.sh updated to version 1.2! Update includes a new built-in "double knock" functionality for sensitive commands (partially addressing @Reef2009 's request). If the configuration line has two port numbers listed (separated by a comma), the command will only be executed if a knock is received...

The interface that triggers the command is one of the configuration parameters for each command you set up: Interface Description br0Main LAN ethXWAN (# depends on model and config) wgs1Wireguard VPN Server #1 loLoopback (used by Tailscale server) For each command, multiple...

This is the type of "double knock" I was talking about: Executable script #1 knock1.sh in /jffs/scripts/ folder: #!/bin/sh #Wait for knock2.sh to appear before executing cmd='logger -t knock1.sh Executed command in forked process. PID $$' logger -t "knock1.sh" "Waiting 30 seconds to check for...

Thanks. Not my idea, but I tried to make it easy to implement. No. The behavior of the firewall is not changed - it just logs the knock and the script detects the log entry and acts. Because the default behavior of the browser is to retransmit, I put a 10 second delay after each trigger to...

It's just a crazy idea and was hoping for someone to shoot it down. I wouldn't recommend subscribing to a VPN service like NordVPN just to try it out. You can search VPN client discussions on this board to learn more. Usual protocols are either OpenVPN or Wireguard, depending which the provider...

Here's a crazy suggestion, that will probably get laughed at here. Maybe try a VPN service and use VPN Director for that one user to use it exclusively. This could solve the isp throttle problem (they won't know what the data is, so no special rules) and it becomes the VPN provider's problem to...

That I do have and it's 1. Thanks for clarifying!

Updated to beta. Checked out a couple of functions. All still working great as usual!

I'm happy to see I have ipv4/ip_forward existing and set to one (and don't seem to have any issues with Tailscale). By the way, do you know the symptoms if this is an issue for someone? Note: I don't see a ipv6/ip_forward entry. Is it because I don't have ipv6 functionality enabled? Does the...

If it helps, here is my config file: track=0 keepalive=1 timerloop=60 logsize=2000 autostart=1 schedule=1 schedulehrs=3 schedulemin=30 updatetm=1 updatets=1 amtmemailsuccess=1 amtmemailfailure=1 ratelimit=0 tsoperatingmode="Userspace" persistentsettings=1 exitnode=1 advroutes=1 accroutes=0...

Yes, I tried adding all those kinds of those types of commands after those listed. The only fix was to end the autoupdate routine with a tsdown. That way, the main loop detects this and restarts tailscale. I agree it's must be some kind of cache issue with either tailmon or tailscale. I'm sure...

Yes, in the Subnets area I have my subnet listed and approved. Thanks.

Not sure what setting you are referring to, but as stated above, all works fine after the Tailmon's monitoring loop restarts the Tailscale service.

Not sure if anyone has this issue with the autoupdate, but for me after any update, even though Tailmon reports everything is connected properly, and the Tailscale client also shows connected and no issues, I cannot connected to my router through the Tailscale network. The only fix I have found...

Updated node to 3004.388.11_beta1. Performed same node update procedure as is now required: remove node, re-add node, then update Guest Network Pro to re-push the 2.4GHz SSID to the new node. Only thing new this time was after the last step, the main router WiFi never returned. After a power...

I reported this issue on the beta. Luckily for me, after ignoring it for a while, the client eventually bound itself to the correct node.

Knock.sh updated to version 1.1! Updates include : Added better reporting of current configuration including URL example based on interface and port (see new screen shot in the Install section of the first post) [Partially addressing @jksmurf request] Documented "Update" function which will...