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. S

    Unbound Unbound DNS VPN Client w/policy rules

    You should put this line in /jffs/scripts/x3mRouting/vpnclient1-route-up: /jffs/scripts/unbound_via_vc1.sh start & and You should put this line in /jffs/scripts/x3mRouting/vpnclient1-route-pre-down: /jffs/scripts/unbound_via_vc1.sh stop & This will enable the rules every time vpn client 1...
  2. S

    Best practice question - How to check for entware/3rd party script.

    Okay Thanks! I figured a check for the existence of a file would suffice but I wanted to ask because I learning more and more everyday how little I know :p. I appreciate your feedback. I’ll refer to amtm for an example.
  3. S

    Best practice question - How to check for entware/3rd party script.

    Is there any preferred method for validating that a 3rd party script is installed? Should I just check that the script/file exists or should I do something more robust in case the file is empty or really out of date?
  4. S

    Solved Unbound stats went a little crazy after update.

    awesome! Reboot this morning with no problems. My removal of the extra call did persist through reboot and the stats page loaded up just fine. I currently have it running in the background of post_mount w/ the ampersand at the end. Would you recommend keeping it that way? I want to say I added...
  5. S

    Unbound Unbound DNS VPN Client w/policy rules

    Yep that’s the problem. (Note that in the newer versions of the script the rules have comments.) If you don’t have the line: modprobe xt_comment in your init-start file the rule creation will fail. If I had to take a wild stab at it I would guess that’s going to be the problem. Add that line to...
  6. S

    Solved Unbound stats went a little crazy after update.

    Hmmm some how the unbound stats call found it’s way into post_mount twice. Something tells me this is probably the culprit.
  7. S

    Unbound Unbound DNS VPN Client w/policy rules

    Okay it sounds like x3mRouting did it’s thing and your dns setup looks fine. check to see if the iptables rules are created by running iptables -nvL OUTPUT -t mangle post the output of that. It should contain 6 rules created by my script. Also check the ip rules. So post the output of this...
  8. S

    Solved Unbound stats went a little crazy after update.

    Here is my dump for the unbound stats database as well. https://pastebin.com/cGZVEB8S
  9. S

    Solved Unbound stats went a little crazy after update.

    https://pastebin.com/2e59kzr7 Sorry if the formatting is off. Copy and paste from my phones ssh app edit: new paste from the file rather than a coping the output of a cat from my terminal. (Should have fixed those extra \n that we’re in the first one) *edit 2*: big face palm... I deleted the...
  10. S

    Solved Unbound stats went a little crazy after update.

    Yeah it’s repeated data. I just cated that file and it looks like I have the same arrays defined at least twice for monthly and weekly data.
  11. S

    Unbound Unbound DNS VPN Client w/policy rules

    The files are created when you run an x3mRouting command for the vpn you want to use. The only file you should need to make is the script file. The rest should just be modifying files that already exist. running these two commands will direct x3mRouting to make the vpn up/down files and set up...
  12. S

    Unbound Unbound DNS VPN Client w/policy rules

    I’m getting the automated install together. Stay posted.
  13. S

    Unbound Unbound DNS VPN Client w/policy rules

    The reason is..... I’m a bash novice lol I now have exit 1 as an error and exit 0 as a success
  14. S

    Solved Unbound stats went a little crazy after update.

    Opened the web interface this morning and unbound stats is looking a bit wacky again. Not a big deal but whatever caused this isn’t permanently fixed by updating the stats. Just a temporary fix until next reboot. View after rebooting:View after updating stats:
  15. S

    Unbound Unbound DNS VPN Client w/policy rules

    https://github.com/swinsonterry/Unbound_via_vpn I’ll make a release post once I get the readme and install stuff done but this is where the code is going to live now.
  16. S

    Unbound Unbound DNS VPN Client w/policy rules

    Make a backup of your working script and run: /jffs/scripts/unbound_via_vc1.sh start with the new one to make sure it doesn’t throw any errors. I’m pretty sure it’s good but if you notice it looks pretty different from the last version since I’ve learned some new bash tricks.
  17. S

    Solved Unbound stats went a little crazy after update.

    Looks like unbound had some fun with the firmware update and I figured I would share the weird behavior. The stats are easily fixed by pressing the “Update stats” button.
  18. S

    Unbound Unbound DNS VPN Client w/policy rules

    #!/bin/sh Check_Tun11_Con() { ping -c1 -w1 -I tun11 1.1.1.1 } Delete_Rules() { iptables-save | grep "unbound_rule" | sed 's/^-A/iptables -t mangle -D/' | while read CMD;do $CMD;done } Add_Rules(){ iptables -t mangle -A OUTPUT -d "${wan0_dns##*.*.*.* }"/32 -p udp --dport 53 -m comment --comment...
  19. S

    Unbound Unbound DNS VPN Client w/policy rules

    x3mRouting ALL 1 xx dnsmasq=xx x3mRouting 1 0 xxx dnsmasq=xxx are the two options that are required for the script to work.
  20. S

    Unbound Unbound DNS VPN Client w/policy rules

    Ohh I wonder if moving the x3mRouting commands to run when the tunnel resets would fix that. @Xentrk can you advise on how the ip rules are created and removed? Edit: I need to look at what vpnmgr does to reset the connection because it kind of seems like maybe the vpntunnel is reset followed...
Top