Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Sat Aug 28, 2021 22:32 Post subject:
Try the old method. I just edited the wiki to de-foncuse the sidexlic edits on the code to use and how to enter it. Not sure why we would need to change anything; because the original method should work fine.
Code:
ifconfig `nvram get wan_ifname`:0 192.168.100.2 netmask 255.255.255.0
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Sat Aug 28, 2021 23:36 Post subject:
Try using $(nvram get wan_ifname) instead of `nvram get wan_ifname`. If that works, then I will make another edit. I seem to recall @egc mentioning a quirk with this. Sorry, I completely forgot to suggest this before
Code:
ifconfig $(nvram get wan_ifname):0 192.168.100.2 netmask 255.255.255.0
I smell a(nother) wiki edit coming, lol. Waiting on verification of @egc's method.
Let's not count our objects before they're compiled.
I had already mentioned that both variants don't work (any differently).
Code:
# ifconfig
vlan2:0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Code:
# iptables -vnL -t nat|grep M
507 38064 MASQUERADE all -- * vlan2 0.0.0.0/0 0.0.0.0/0
9 2952 MASQUERADE all -- * br0 192.168.x.0/24 192.168.x.0/24
And adding the port forward didn't seem to help.
Now, my apologies for forgetting some likely crucial details. For devices on the LAN on which a VPN is not enabled, the ifconfig and iptables commands are unneeded to facilitate access to the modem. Disabling the VPN solves the problem. So, although this issue seems to be due to the VPN, might a workaround be possible by changing something on the router?
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Tue Aug 31, 2021 23:22 Post subject:
Or rather, it's not an issue. VPN will not connect because there is no route to the modem; this isn't something that is broken, IMHO. The VPN connects the router via tunnel to the internet; it will not connect to your modem directly, ever. This is by design. I don't know how this basic networking concept is not understood. Perhaps you can use PBR to mitigate this in some way for a particular client, but I will let @egc or @eibgrad or one of the other folks answer and confirm.
And please do not reference development or software coding or anything technical since you completely pooched this. Here we are chasing our tails because you're expecting a VPN client to connect to your modem's webUI. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
The VPN connects the router via tunnel to the internet; it will not connect to your modem directly, ever.
While this may be true for other VPNs, mine allows local connections (192.168.0.0 - 192.168.255.255 and 10.0.0.0 - 10.255.255.255), which I've confirmed only for IPs on the same subnet as the gateway.
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Wed Sep 01, 2021 1:17 Post subject:
But it's not working until you kill the VPN, and it won't. Your VPN bypasses the modem completely. LAN -> router -> VPN service provider. I really don't know how difficult this is to grasp. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
