How to force all traffic through oet1 interface?

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking
Author Message
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Tue Sep 08, 2020 0:16    Post subject: How to force all traffic through oet1 interface? Reply with quote
I have a Wireguard tunnel setup on oet1, and while doing traceroute -i oet1 works as intended, by default network traffic is not going through the tunnel, in spite of setting 0.0.0.0/0 in AllowedIPs.

I've been googling around trying out different iptables commands that people have suggested, but none of them seem to work (If I'm being perfectly honest though, I still don't really understand iptables even after reading up on it).

Here's my current router information and config:
Router: Linksys EA6350 (v1)
Firmware: DD-WRT v3.0-r40559 std (08/06/19)
Current firewall rules:
Code:
iptables -t nat -A POSTROUTING -s 10.0.1.0/24 -o oet1 -j MASQUERADE
iptables -A FORWARD -s 10.0.1.0/24 -i br0 -o oet1 -j ACCEPT
iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
Sponsor
Zyxx
DD-WRT User


Joined: 28 Dec 2018
Posts: 288

PostPosted: Tue Sep 08, 2020 7:23    Post subject: Reply with quote
Since your installed release, the Wireguard interface received many additions, including "Endpoint mode".

I'd advise to update your router to a newer release, discarding the bad 40559 (this wasn't a great build at all).

Newer Builds ftp://ftp.dd-wrt.com/betas/2020/ (like 44251) "just work" incl. wireguard. No additional iptables entries are needed. The GUI covers everything.

My config at home (on an old N66u) consists of
-enabling wireguard,
-disabling CVE-2019-14899 Mitigation,
-enabling NAT via tunnel
-adding the "other side"
-peer tunnel IP and DNS 0.0.0.0
-enabling endpoint
-allowed IPs 0.0.0.0/1,128.0.0.0/1
-enabling Route allowed IP's via tunnel
-set persistent keep alive to something suitable like 20-30 seconds

done Cool

Many devices of my network use this router on a regular basis each day.

edit
Re-reading everything I stumbled across your allowed IP setting 0.0.0.0/0 this setting might also be cause of problems.
Have a look into @Egc's excellent Wireguard .pdf guide. It is pinned as important thread in this forum.
Everything is covered there, including this setting Smile
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Tue Sep 08, 2020 20:24    Post subject: Reply with quote
Zyxx wrote:
Since your installed release, the Wireguard interface received many additions, including "Endpoint mode".

I'd advise to update your router to a newer release, discarding the bad 40559


Wow, that is a big difference.

Is there any reason why the wiki entry for my router only has build 40559 as the latest? I can see browsing the link you gave that the EA6350 is there for the newer builds, I just honestly had no idea since the database only had up to 40559 listed.
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 1751

PostPosted: Tue Sep 08, 2020 23:06    Post subject: Reply with quote
It's one of life's mysteries.

https://wikidevi.wi-cat.ru/Linksys_EA6350

08/28/2020 - r44251
Zyxx
DD-WRT User


Joined: 28 Dec 2018
Posts: 288

PostPosted: Wed Sep 09, 2020 7:09    Post subject: Reply with quote
The database was already in this state when I flashed my wrt54 many many years ago.
It recommended out of date/bad builds like today.

Somehow some(-one/-thing) takes random releases and inserts them on the website, without refreshing those data if problems are found.

*shrugs*

In my opinion: reading the release threads, maybe taking a look into svn.dd-wrt.com is sufficient.
Good feeling about the release or you have some spare time to revive your device if it gets lost --> "do the flash" Very Happy
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 6625
Location: Netherlands

PostPosted: Wed Sep 09, 2020 8:32    Post subject: Reply with quote
If we could make it clear for all users to follow the forum guide lines (link in my signature at the bottom) than it would be general knowledge not to use the router database Sad
_________________
Routers:Netgear R7800, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000 (converted WRT320N), WRT54GS v1.
OpenVPN Policy Based Routing: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321686
Install guide R6400v2:http://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
OpenVPN Server Setup:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=318795
Install guide R7800: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Wireguard Server setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1183135
Wireguard Client setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324624
Wireguard Advanced setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324787
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Wed Sep 09, 2020 15:58    Post subject: Reply with quote
egc wrote:
If we could make it clear for all users to follow the forum guide lines (link in my signature at the bottom) than it would be general knowledge not to use the router database Sad


Is it possible to either:

A - remove the router database on the website and instead have it redirect to the forum guidelines
OR
B - If there's just no one to manage the database, I would be interested in talking about taking over managing that as a way to give back to the project and make it easier for newcomers.
jauch888888
DD-WRT User


Joined: 23 Apr 2020
Posts: 108

PostPosted: Thu Sep 10, 2020 8:15    Post subject: Reply with quote
wuubb wrote:
egc wrote:
If we could make it clear for all users to follow the forum guide lines (link in my signature at the bottom) than it would be general knowledge not to use the router database Sad


Is it possible to either:

A - remove the router database on the website and instead have it redirect to the forum guidelines
.


+1

And or remove the build 40559...
they can’t do everything


Rolling Eyes Wink
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Fri Sep 11, 2020 1:14    Post subject: Reply with quote
Zyxx wrote:


My config at home (on an old N66u) consists of
-enabling wireguard,
-disabling CVE-2019-14899 Mitigation,
-enabling NAT via tunnel
-adding the "other side"
-peer tunnel IP and DNS 0.0.0.0
-enabling endpoint
-allowed IPs 0.0.0.0/1,128.0.0.0/1
-enabling Route allowed IP's via tunnel
-set persistent keep alive to something suitable like 20-30 seconds

done Cool

Many devices of my network use this router on a regular basis each day.


I'm not sure if it was the CVE mitigation, or the allowed IPs, but your settings worked perfectly for me. Traceroute is now going through the tunnel without any other configurations. Many thanks!
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Fri Sep 11, 2020 1:22    Post subject: Reply with quote
wuubb wrote:
worked perfectly for me. Traceroute is now going through the tunnel without any other configurations


Ok I spoke too soon. Ping and traceroute work fine, but now many sites (including google, duckduckgo, etc) simply timeout in the browser. I'm currently stuck using Bing as as my search engine unless I turn off the VPN Shocked
Zyxx
DD-WRT User


Joined: 28 Dec 2018
Posts: 288

PostPosted: Fri Sep 11, 2020 6:26    Post subject: Reply with quote
In my case this happened due to wrong MTU settings.

Try lowering the tunnel MTU.
DSL PPPoE usually uses 1492 in my area but Wireguard brings its own overhead resulting in up to 80 bytes (if IPv4 and IPv6 headers are in use).
So I set my tunnel to 1412 and timeouts on my end did not happen anymore.

Have a look here:
https://kb.netgear.com/19863/Ping-Test-to-determine-Optimal-MTU-Size-on-Router

Test your WAN MTU, after this reconfigure your Tunnel MTU.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 6625
Location: Netherlands

PostPosted: Fri Sep 11, 2020 7:54    Post subject: Reply with quote
Besides an MTU problem it might be DNS related.

Some browsers like chrome use different DNS settings.

Are you using Policy Based Routing?

What have you set for the Static DNS servers?

_________________
Routers:Netgear R7800, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000 (converted WRT320N), WRT54GS v1.
OpenVPN Policy Based Routing: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321686
Install guide R6400v2:http://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
OpenVPN Server Setup:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=318795
Install guide R7800: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Wireguard Server setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1183135
Wireguard Client setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324624
Wireguard Advanced setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324787
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
wuubb
DD-WRT Novice


Joined: 13 Aug 2020
Posts: 7

PostPosted: Sun Sep 13, 2020 17:58    Post subject: Reply with quote
Lowering the MTU seems to have fixed everything, though I had to lower it way more to around 1200, even though 1500 (default) without the tunnel works fine. IDK ¯\_(ツ)_/¯.

Just to not leave things hanging - the DNS was PiHole running on the VPS.

Thanks for the help everyone!
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum