Recent content by abir1909

I managed to get it working. Regarding the port I think it has to do with TorGuard port forwarding. I emailed them.

thank you for the reply. added the details to my signature. i haven't changed my previous setup. i have both nat-start and firewall-start scripts still in place. the firewall-start only have

thank you for the reply. added the details to my signature. i haven't changed my previous setup. i have both nat-start and firewall-start scripts still in place. the firewall-start only have the ifconfig br0:0 192.168.1.xxx up and the nat-start have the below. i am getting peers and it...

Hi @ZebMcKayhan and team. you guys helped me two year ago writing the script to allow transmission through the wireguard client. that nat-start and firewall-start worked great for the past 2 years and now it stopped. not sure if it due to the amtm update or Asus firmware update but the same...

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

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

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

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

one more thing, does wireguard have kill switch?

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

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.

Let me try and advise. Thanks

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

The webui only supports OpenVPN

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?