[fcs001fcs]

I have a WRT 1900AC that connects to my ISP via PPPoE through a NetGear DM200 VDSL2 Modem/Router that is set in "Bridge Mode" (no routing).

The DM200 is just the VDSL2 connection and the WRT1900AC handles the login, routing, WIFI, and WAN IP etc..

The DM200 keeps the default static IP of 192.168.5.1 in Bridge Mode with no DHCP or other routing functions and if I plug in the Ethernet cable from my PC directly, set a static IP for it of 192.168.5.2, then I can access the DM200 GUI for checking VDSL2 connection status.

There is only one LAN port on the DM200 (and a DSL RJ11 port) and the LAN Port is normally connected to WAN port of the WRT1900AC during normal operation.

My local LAN (WRT1900AC) is set at 192.168.1.1 and I cannot seem to find static routing or other setups that allow me to access the DM200 Modem 192.168.5.1 from my PC through the WRT1900 Router to the DM200 on the WAN side of the WRT1900AC.

Can anyone suggest a setup that will allow me to check the DM200 Modem GUI without having to unplug WRT1900AC from it and directly connect PC and set static IP on PC?

I think Static Routing will do it but I cannot seem to get a setup that will work.

I am running Kong's DD-WRT v3.0-r30840M kongmv (11/03/16)

WRT1900AC Router in PPPoE Mode as a Gateway - 192.168.1.1
DM200 as a VDSL2 Modem in Bridge Mode - 192.168.5.1

[fcs001fcs]

I tried it as you wrote it and then I changed it to 5.1 vice 5.2 since the DM200 is 192.168.5.1.

It did not work as planned but it did redirect me to the WRT1900AC GUI start page on the second try. I need to get to the DM200 GUI start page with 192.168.5.1

The DM200 has no routing NAT or routing functions active, it is just a bridge.

What an I doing wrong and how would I check if the commands are set?

[Per Yngve Berg]

http://www.dd-wrt.com/wiki/index.php/Access_To_Modem_Configuration

[fcs001fcs]

Tried following the WIKI but it seems outdated and did not work.

I put the commands in via Putty, and various versions of the commands that I could figure out from the WIKI, but no success.

Does anyone have a working set of commands I could try for my access to the Modem from a WRT1900AC?

[Per Yngve Berg]

After executing the commands posted by eibgrad.

ifconfig $(get_wanface):1

Do you see the address 192.168.5.2?

Route

Do you see 192.168.5.0 listed?

[fcs001fcs]

I ran the commands again and got the following through Putty:

[Per Yngve Berg]

It's "route" with lowercase r.

You are putting the ip address on the wrong interface. It shall be the wan port, not the ppp0 interface. usually vlan2

[fcs001fcs]

I have the WRT1900AC set up as PPPoE and I confirmed that ppp0 is my WAN and the IP of ppp0 matches the WAN IP.

With lower case "route" I see the following:

192.168.5.0 * 255.255.255.0 U 0 0 0 ppp0

Anything else I need to do to get it working?

[Per Yngve Berg]

You have to bypass pppoe and access through the physical wan port.

[fcs001fcs]

How is that done?

[Per Yngve Berg]

By changing the interface name.


ifconfig vlan2:1 192.168.5.2 netmask 255.255.255.0 broadcast 192.168.5.255
iptables -t nat -I POSTROUTING -o vlan2 -d 192.168.5.0/24 -j SNAT --to 192.168.5.2

[fcs001fcs]

The commands below did not work.

I then ran IFCONFIG and noticed that the WAN port MAC was assigned to "eth1" (vice vlan2). I then ran the commands with eth1 and it worked! I can access the VDSL2 Modem directly through the WRT1900AC without unplugging and plugging in Ethernet cables.

The commands I used were:

ifconfig eth1:1 192.168.5.2 netmask 255.255.255.0 broadcast 192.168.5.255
iptables -t nat -I POSTROUTING -o eth1 -d 192.168.5.0/24 -j SNAT --to 192.168.5.2

One more question: Do I have to consider any additional security measures after I made the above changes to the WRT1900AC settings for the config and firewall?

[Per Yngve Berg]

No, you are perfectly safe.

[fcs001fcs]

Thanks to you (@Per Yngve Berg) and @eibgrad for all your assistance.

[pwhalley]

Thank you all, this was very helpful. Using the second variation worked in my case. I have a set of Ubiquity radios providing a point to point link on the WAN side of the router connecting to the ISP router/modem. Having he modem end of my WAN almost 1.5 miles away makes this a real timesaver! At present there are 3 IP addresses that I need access to and this does it!

For the record, The second variation worked for me (my WAN subnet is 192.1.2.0/24).