Ip route add default via 192.168.1.1 dev vlan2 table 200 DD-WRT connected to OpenVPN using built-in client feature in 'Services' tabĮdit 05 March: What I have tried in the meantime:Īdding the following to the Policy Based Routing field in OpenVPN client settings (idea: traffic that comes from the WAN ip should be routed back to the WAN interface, vlan2 or ppp0): ip rule add from 192.168.1.1 table 200.DD-WRT set to allow remote GUI management at 8080, also from remote IPs and SSH access at 22, SSH activated in services, also at 22.ADSL router with port forwarding activated for ports 22 / 8080, DDNS to 192.168.1.100.DDNS alias pointing at the ADSL router’s connection: 115.x.x.x.TP-Link WR1043ND router with DD-WRT 25544.I am having a similar issue with the web GUI at port 8080 and a PPTP VPN server at port 1723, so I believe the issue is not related to SSH as such. Is it correct that I would need to define a custom iptables setting for requests coming in through WAN to be responded via WAN, as well? If yes, how would I go about it? If no, what else could I do? I am reading that this may be related to all traffic being routed outbound through the VPN gateway, including traffic coming in through WAN. The OpenVPN connection works fine but the remote SSH access only works when the VPN client is disabled. However, the DD-WRT is supposed to be permanently connected to a VPN server (using the built-in OpenVPN client). The DD-WRT is behind an ADSL router which has port forwarding for port 22 enabled, DD-WRT SSH access and service are set to port 22, as well. I have a DD-WRT router which I would like access remotely via SSH.

Dd wrt v24 sp2 openvpn client