Talk:Access To Modem Configuration
From DD-WRT Wiki
This article is not very illuminating. Try to explain the concepts in different words ADDITIONALLY, starting with: "in other words" .....
It could be an easy example to learn how this bridging works.
Computer MIKE:is connected to a 192.168.c.d network. Now I browse to http://10.0.0.138/ and I will be connected?
Shall MIKE use 10.0.0.138 as a gateway?
Please, folks! Make us some good example pages!
 Getting Modem Config to work
The commands as listed in the original wiki article did NOT work for me. After checking a few other websites, i found the following settings / commands that worked for me:
FYI: a) I'm using WRT54GL, DD-WRT v24beta (6/20/07)
1. set your router IP address to 192.168.1.1
2. set your modem IP address to 192.168.2.1
3. On you DD-WRT control panel, go to administration>commands
4. Type in "ifconfig vlan1:0 192.168.2.2 netmask 255.255.255.0" without quotes and press <Save Startup>
5. Type in "/usr/sbin/iptables -I POSTROUTING -t nat -o vlan1 -d 192.168.2.0/24 -j MASQUERADE" without quotes and press <Save Firewall>
Note: Yes, ur modem ip address is 192.168.2.1 but the ip address in the startup script is 192.168.2.2, and the ip address in the save_firewall script is 192.168.2.0
Now, you should be able to access the modem page via the router by going to 192.168.2.1
Hope this works for you.
I removed following notion as this is after all DD-WRT wiki and more importantly if especially first command (ifconfig vlan1:1 ..) is run in firewall script it means that there is no access to modem until router gets an WAN IP, thus no access to modem if no WAN connection ever made, this makes troubleshooting non-working connection much more difficult ;)
" #The above method does not work in all Linux based firmware, e.g. it does not work in Tomato. A broader solution is to put both lines of code into the Firewall script and none into the Startup script. Adding both lines to the Firewall script allows this to work in DD-WRT and in Tomato and probably other Linux based firmware.Cdkiller 11:55, 13 August 2008 (CEST) "