Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[superloupiot]

Hello all,

I have an adsl modem connected to the DIR-655 router.
This modem is configurable through web pages (as the DIR-655 router is).
But because it is connected to the WAN access, i can't access the configuration pages anymore.

How can i access the configuration pages of the modem when it is connected to the DIR-655 WAN access?

Thanks.

[EddieZ]

You should normally put the devices on two different subnets, so you will have 2 addresses for the devices: 192.168.0.1 for the Dlink and 192.168.1.254 (or.1) for the modem

It seems they are both on the same sunbet...no idea how to get to the modem now. 2 options:
1. Remove the DIR, connect to the modem and change settings (probably also doing double DHCP, NAT. Which can cause serious issues.)
2. Get into the DIR and change router IP address and DHCP server range. (http://192.168.0.1/Basic/Network.shtml)
192.168.0.1 is the default, change it to 192.168.1.1. I guess the modem is also on the 192.168.0.x subnet.

[lotacus]

if it's connected to the wan port, you can just apply the static route no?

otherwise, just plug the modem into one of the LAN ports. but you'll have to disable the dhcp server.

[EddieZ]

if it's connected to the wan port, you can just apply the static route no?

otherwise, just plug the modem into one of the LAN ports. but you'll have to disable the dhcp server.

Looking at the post and making an educated guess about the level of expertise I would be very surprised if he had the DIR connected to the WAN port. 

[superloupiot]

The modem is using a different subnet than the router.
But perhaps the problem comes from the fact that the modem is configured in bridged mode only?

Is there an other way than bridged mode to connect the modem to the router?

[smlunatick]

I'm also curious on this as with the years I have been using a router (either wired or a DIR wireless router) I have yet found a way to access the DSL modem's internal web configuration pages while it is connected on the WAN port. 

[lotacus]

Hello all,

I have an adsl modem connected to the DIR-655 router.
This modem is configurable through web pages (as the DIR-655 router is).
But because it is connected to the WAN access, i can't access the configuration pages anymore.

How can i access the configuration pages of the modem when it is connected to the DIR-655 WAN access?

Thanks

Go to the dlink and set it's internet to a static ip address of the dsl modem. Your modem is probably residing on 192.168.1.1, so set the dlink internet settings to 192.168.1.2, and the LAN settings to 192.168.3. If your certain no dhcp server resides on the modem then keep dhcp server enabled. reboot dlink and make sure your computer has a new ipaddress.  You should be able to access both setup pages. kinda wierd setup and there is likely a better one, but yanno,i'm tired of typing.

[superloupiot]

I confirm that in bridged mode only, the modem configuration pages can't be access.
In the other mode (RFC 1483 ..., PPPoE, PPPoA, ...) it is possible to access the modem pages when the DIR-655 router internet access is configured for static or dynamic IP.
However, in these modes, I was not able to configure the modem to access the web from my computer (though the adsl connection was OK, login OK).
I've tried several options in the routing section of the modem (but disable the NAT) and all failed to access the web.
I was able to access the web only in bridged mode.
Because it is not possible to access the modem pages, it is not possible to get the information concerning the adsl line quality (margin, attenuation ...) nor it is possible to manage the modem itself. That is a pity!
So, if someone know how to solve this problem, he is welcomed.

[lotacus]

I'd like to try the static routing. I myself have a siemans gateway that was provided by aliant and I to was not able to access the configuration in one of the configurations I have set up. I was able to get to the login, but it would not let me actually log in (as if the admin/admin was wrong).

That I think is double nat. I'll see what I can try without disrupting my network. then i'll get back to you.

[superloupiot]

I'm not sure double NAT is the source of the problem because the modem has the option to disable the NAT (and that is what i did).

[lotacus]

I'm guesing your "modem" is actually an ADSL gateway like mine is. I'm still not clear on your physical configuration.

My config is as follows:

             PPoE                         
cat5----[WAN]--------[LAN]     [ATM]-------->[internet]
           [DLINK]          [DSL Gateway]
        192.168.0.1         192.168.2.1

This naturally will never work because the WAN link now has an external ip address.

If you leave the ethernet cable on the WAN port of the dlink and connect the other end to the lan port. like said post, you would have to configure the dlink with a static ip address on the WAN side that matches that of your DSL gateway, then configure a static route, and let the DSL gateway handle the PPoE session. As well you would want to make sure that the ethernet cable is not plugged into the WAN port of the DSL Gateway.

So your setup should look like this:

       192.168.2.254                  PPoE
cat5----[wan]--------[LAN]     [WAN]-------->[internet]
           [DLINK]          [DSL Gateway]
        192.168.0.1         192.168.2.1

With a static route so that requests from 192.168.0.0 can be sent to 192.168.2.0

I think anyways. I'd really test it out on my end first but yanno, nothing but people on the internet 24hrs a day because they're to lazy to go to work, to bed, do dishes, clean up their mess or whatever other than spending their lives playing pointless flash games.

it would probably be alot easier if d-link so graciously steps up and removed the commented out code and added the proper code.

set_subnav_link(router_mode_enabled, "Status_Routing_nav_link");
 <!-- Only support WAN <option value="LAN">LAN</option> -->, //set_subnav_link(router_mode_enabled, "Status_Routing_nav_link"); and adds <li> <div> <a href="../Status/Routing_Status.shtml" onclick= blah blah...

Whenever I actually get a better chance at it, i'll test the WAN port configuration. I know I did once get it working when I first got all the equipment, but opted for my current configuration

[lotacus]

OK,, well my first reply? was correct. I hate reading so i'm not going to verify. Sometimes people (myself included) can over complicate the simplist of things.


for your scenerio.

Your dsl gateway's LAN side ip address is 192.168.2.1
Your dlink is at it's defaults.


connect wan port of dlink to dsl gateway. Set WAN port to static 192.168.2.2 using appropriate settings for gaway etc.

Keep everything else on DLINK as defaults. 192.168.0.1 w/ DHCP enabled. Let dynamic routing do it's job.
You will have access to both the internet and both web gui's. Remember, on DLINK, you will be connecting to 192.168.0.1 for setup, not 192.168.2.2.