[tpqnew]

Hi,
I'm using dd-wrt 54420.

If I set a wireguard VPN client does checking the 'kill switch' enough to prevent any connections outside the vpn tunnel or are some firewall rules needed?

What about openVPN? I haven't seen any kill switch option there.

(My goal is to prevent any device connected to the router to leak my ISP IP, if the VPN is down not to fallback to my ISP connection.)

My old VPN provider on an old DD-WRT version said to add the following as a startup script:
route add -host WG_HOSTNAME gw DEF_GW dev DEF_IFACE
route del default
route add default dev oet1
iptables -t nat -I POSTROUTING -o oet1 -j MASQUERADE
iptables -I FORWARD -i br0 -o DEF_IFACE -m state --state NEW -j REJECT --reject-with icmp-host-prohibited
iptables -I FORWARD -i br0 -p tcp -o DEF_IFACE -m state --state NEW -j REJECT --reject-with tcp-reset

Is it needed?

Thank you

[egc]

[tpqnew]

In my (very weak) defense... the guide version I was working with was older and only had 10 pages
Downloaded the new one.

As always, thank you for your help!

[egc]

Glad you solved it and if you have any other questions feel free to ask, we are here to help

[tpqnew]

turns out my very old ddwrt version does not have the kill switch option for the openVPN.
Would the following firewall rule be enough as a kill switch alternative:
iptables -I forward -i br0 -o `nvram get wan_iface` -J REJECT

Thanks

[egc]

Old version has security issues so better upgrade

[tpqnew]

Thank you.

Old router. all my upgrade attempts failed (had a thread about it)

[tpqnew]

sorry, just checked and get_wanface returns 'vlan' while nvram get wan_iface returns 'vlan2'.
If I check ip route , default route is named vlan2.
which one is correct?

[egc]

Cannot tell the rule I gave is for modern builds.

That is why we do no longer support old versions

Just try and check if the killswitch is really working.

[dale_gribble39]

[tpqnew]

I've tried that multiple times, it says upgrade successful, but after reboot it stays on the same old version.
I've bricked my other tp-link 1043 v2 a week ago... its last words were 'update successful'. tried all the resets and tftp methods i could find, but nothing worked.

so, maybe there is NO reason for the upgrade to fail... but it still does sometimes

until I'll get a newer router, this one will have to do I guess.

[dale_gribble39]

Tangent reply regarding upgrade issue continued in "Unable to upgrade tplink 1043 to a newer version" so as not to further litter this thread with off-topic discussion.