Author | Message |
---|---|
![]() |
|
egc Replies: 1 Views: 46 |
![]() |
I have an R6400v2 which is more or less the same.
It works on that router running build 52086 (unofficial build) by pressing the WPS button for about 8 sec (that is the second button from the right ... |
|
![]() |
|
![]() |
|
egc Replies: 4 Views: 109 |
![]() |
Welcome to the forum.
Unfortunately you are using an old and outdated build. Upgrading is highly recommended. *After* upgrading reset to defaults and put settings in manually, never restore f ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
Glad I could be of assistance ![]() |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
If you connect to the same VPN server I can imagine it does not work.
What if you let your phone connect to a VPN in another server/city? Mullvad lets you use multiple addresses/cities |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
As a test you can use port 80 instead of 8080 for internal port and you should see your routers http page when doing http://<mullvad-external-ip>:55923 | |
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
I do not use lighttpd but maybe you have to use http:// instead of https:// ?
Note not all browser allow http:// When I want to connect to my routers GUI remote administration via the VPN (only fo ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
I am updating the instructions (still a WIP):
Port forwarding via WireGuard (oet) interface This is an example to port forward via the oet interface which might come in handy if you are connected ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
If lighttpd is residing on the router on port 8080 you have to allow port 8080 on the INPUT chain.
You are allowing the external port but the PREROUTING rule comes first so it is already translated ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
Looking into it you probably want remote administration?
If so the router is listening on port 80, so the internal port is port 80 and you also have to allow port 80 on the INPUT chain. I just d ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
What is it what should listening on port 8080? | |
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
You can see if your rules are hit with:
iptables -vnL INPUT iptables -t nat -vnL Note that the remote IP address you have to use is not the MV server address but the address you get with ipleak. ... |
|
![]() |
|
![]() |
|
egc Replies: 3 Views: 104 |
![]() |
Would not giving your clients, which you do not want to use Tor, a static lease of .98 or below do the trick? | |
![]() |
|
![]() |
|
egc Replies: 2 Views: 78 |
![]() |
Route selected destinations via WAN uses routing rules and not iptables rules.
For each destination you add a routing rule will be added to route that destination via the WAN. Edit: before you g ... |
|
![]() |
|
![]() |
|
egc Replies: 26 Views: 574 |
![]() |
The WireGuard Client setup guide has a paragraph about port forwarding.
Mullvad also has instructions |
|
![]() |
|
![]() |
|
egc Replies: 3 Views: 90 |
![]() |
Yes it is station bridge.
See my attached personal notes But a non-bridged solution aka Station mode is the more robust one |
|
![]() |
|
All times are GMT |