Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. Z

    kernel: wl0: random key value: -

    Hello, have you found the cause? I've started to see the same in my log a few days back without any obvious change to the network / device setup. I just noticed, while this happens, my guest networks goes down.
  2. Z

    wgclient-start with iptables nat rules after router reboot

    This actually could be nice all-in-one script :) Questions: Are /etc/wg/* files anyhow documented and stable (naming, existence, its purpose, whatever...)? I am a "normal" user who usually fiddle only with official APIs to avoid future problems (unannounced change of background stuff). I might...
  3. Z

    wgclient-start with iptables nat rules after router reboot

    Didn't try it yet but in general that could work with some adjustments. At first you can do the test more elegant way if grep -q "$NAT_RULE" $file; then and as second you should remove particular rules from /etc/wg/fw_wgc1_nat.sh in wgclient-stop, otherwise, when you stop/disable the client, the...
  4. Z

    wgclient-start with iptables nat rules after router reboot

    Argh, copy pasted from console and missed that overflowed one :) fixed...
  5. Z

    wgclient-start with iptables nat rules after router reboot

    Sure, anyway, I'll be thankful if you find any problem or possible vulnerability... Here you go: nat-start #!/bin/sh # cycle all running WireGuard clients for wgc in `ls /tmp/wgclient-enabled_* 2>/dev/null`; do # reload/re-run the `wgclient-start X` /jffs/scripts/wgclient-start...
  6. Z

    wgclient-start with iptables nat rules after router reboot

    At the end I have used nat-start, as suggested by @ZebMcKayhan, to check for running wg clients and rerun wgclient-start which has been made safe to reload/rerun - avoiding adding duplicate nat rules.
  7. Z

    wgclient-start with iptables nat rules after router reboot

    Thank you for the options. I have a few questions to 3) Does it persist between FW upgrades? Under what condition it is (re)generated? I presume I could loose customization from time to time.
  8. Z

    wgclient-start with iptables nat rules after router reboot

    Hi, your guess is correct at the end, just traces in syslog are not as originally expected, thx for a tip. I let log file to be polluted from nat-start and wgclient-start and (at least) in my case the nat-start is called 3 times during boot when the last call is done approx 13s after WG start...
  9. Z

    wgclient-start with iptables nat rules after router reboot

    Thrilled for a while, but this doesn't seems to be the case :-( @router:/tmp/home/root# grep -ni restart_firewall /tmp/syslog.log* /tmp/syslog.log:428:May 5 07:05:10 rc_service: service 1511:notify_rc restart_firewall /tmp/syslog.log:541:May 5 07:05:13 rc_service: waitting "restart_firewall"...
  10. Z

    wgclient-start with iptables nat rules after router reboot

    I have a wgclient-start (and its wgclient-stop counterpart) with some iptables rules to modify a nat. It works as expected when enabling/disabling wg client. However, after router (RT-AX86U with 388.2_2) reboot, all iptables rules set by the script are missing though the script has been...
Top