Menu
What's new
By:
Filters Better Search

Recent content by abir1909

  • 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. A

    VPN Director & Port Forwarding?

    Check out this thread: Post in thread 'Port forwarding on WireGuard seems unsupported in 388.1' https://www.snbforums.com/threads/port-forwarding-on-wireguard-seems-unsupported-in-388-1.83486/post-861028
  2. A

    Port forwarding on WireGuard seems unsupported in 388.1

    thanks Jeffrey, i made the changes and seems to work just fine. port is open on the wireguard vpn. will report if any issues.
  3. A

    Port forwarding on WireGuard seems unsupported in 388.1

    With that said, would you change something in my settings? You previously mentioned to move the nat rules to nat-start. Do I still need to do it? Should I create a nat start script? Also, you mentioned the delete rules (-D). Do I still need it? If so how would you add it to my existing script...
  4. A

    Port forwarding on WireGuard seems unsupported in 388.1

    I am running transmission on the router. in transmission settings.json I setup a bind ip for transmission "bind-address-ipv4": "192.168.1.xxx" that way I can have that specific ip go through the vpn. In order for this ip to get internet I had to add the br0 bridge command to firewall-start...
  5. A

    Port forwarding on WireGuard seems unsupported in 388.1

    one more thing, does wireguard have kill switch?
  6. A

    Port forwarding on WireGuard seems unsupported in 388.1

    I was able to open the port on the fireguard vpn using the following lines only in firewall-start ifconfig br0:0 192.168.1.xxx up iptables -t nat -A PREROUTING -i wgc2 -p udp --dport 55xxx -j DNAT --to-destination 192.168.1.xxx iptables -t nat -A PREROUTING -i wgc2 -p tcp --dport 55xxx -j DNAT...
  7. A

    Port forwarding on WireGuard seems unsupported in 388.1

    unfortunately no luck. i am also not sure i am doing it 100% right. i added the lines to both firewall-start and created nat-start. i changed the port to the one i am using and also change to wgc2 and port showing closed. have to run more tests.
  8. A

    Port forwarding on WireGuard seems unsupported in 388.1

    Let me try and advise. Thanks
  9. A

    Port forwarding on WireGuard seems unsupported in 388.1

    agreed. but what are the lines I should add add to firewall-start in order to forward wireguard port?
  10. A

    Port forwarding on WireGuard seems unsupported in 388.1

    The webui only supports OpenVPN
  11. A

    Port forwarding on WireGuard seems unsupported in 388.1

    This is very interesting as I have the same issue with TorGuard. Only works with OpenVPN not with Wireguard. There were couple firmware updates since that post, has anything changed? Also, @RMerlin mentioned that it should be configured manually, do you know how to do it at firewall-start script?
  12. A

    VPN Director & Port Forwarding?

    did you get anywhere with this?
  13. A

    Domain-based VPN Routing Script

    is there a way to add bunch of domains at once? or have to be done one by one?
  14. A

    Domain-based VPN Routing Script

    Thanks for the tip! hope i will be able to achieve it.
  15. A

    Domain-based VPN Routing Script

    I read somewhere that Moldova and couple other counties VPN is blocking all YouTube ads! I tried it and it works like a charm, However, try to figure out the hundreds streaming domains they are using for selective routing 🤔
See more
Top