Static Route to Access Modem Config?

Hi Folks,

I have got a problem accessing the setup pages of my modem from behind
my router. My modem is in bridge mode. I could access the setup pages
when it was in half bridge ok.

Anyway, my setup looks like this:

ISP-------Modem--------Router--------------PC
ISP---192.168.0.1---192.168.1.1---192.168.1.100

Again the modem is in bridge mode with DHCP turned on. Its a Dlink
302G.

The router does the login via PPPoE and has DHCP turned on. Its a
Linksys WRT54G running DD-WRT v24.

I tried setting up a static route with:

Target IP Net: 192.168.0.1
Subnet Mask: 255.255.255.0
Gateway: 0.0.0.0
Interface: WAN

My modem is plugged into the WAN port.

If I plug my modem into my PC directly I can see that the gateway is
indeed 192.168.0.1.

Why is this not working????

I am not sure that there is much I can do to try and isolate where its
failing?

Any help or suggestion appreciate.

-Al

The modem is not a modem. It is a "router" and modem built into the same
box. The bridging mode simply tries to nullify the "router" componenet
(a.k.a. remove Layer 3&4 abilites and run only Layers 1&2). A "straight"
modem has no such thing as a bridging mode because it only operates at
Layers 1&2 in the first place.

My advice is to "forget it".

Choose one:

1. Get rid of the bridging mode and run the "modem" with full abilities
(modem/router) and get rid of the DLink box.

or

2. Get rid of that thing and buy a "straight" modem and use it in
combination with the DLink.

I recommend #2.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


<BigAl.NZ@gmail.com> wrote in message
news:6e19fae4-e485-4bc2-b401-40ae750c22c8@t12g2000prg.googlegroups.com...
> Hi Folks,
>
> I have got a problem accessing the setup pages of my modem from behind
> my router. My modem is in bridge mode. I could access the setup pages
> when it was in half bridge ok.
>
> Anyway, my setup looks like this:
>
> ISP-------Modem--------Router--------------PC
> ISP---192.168.0.1---192.168.1.1---192.168.1.100
>
> Again the modem is in bridge mode with DHCP turned on. Its a Dlink
> 302G.
>
> The router does the login via PPPoE and has DHCP turned on. Its a
> Linksys WRT54G running DD-WRT v24.
>
> I tried setting up a static route with:
>
> Target IP Net: 192.168.0.1
> Subnet Mask: 255.255.255.0
> Gateway: 0.0.0.0
> Interface: WAN
>
> My modem is plugged into the WAN port.
>
> If I plug my modem into my PC directly I can see that the gateway is
> indeed 192.168.0.1.
>
> Why is this not working????
>
> I am not sure that there is much I can do to try and isolate where its
> failing?
>
> Any help or suggestion appreciate.
>
> -Al
>
>

> 1. Get rid of the bridging mode and run the "modem" with full abilities
> (modem/router) and get rid of the DLink box.

The D-link box IS THE MODEM. Not exactly smart to suggest getting rid of
it.

> 2. Get rid of that thing and buy a "straight" modem and use it in
> combination with the DLink.

Erm, the D-link is the modem, getting another modem would help, how?

> I recommend #2.

With some corrections, it's basically the only choice. What he should keep
is the LINKSYS unit, not the D-link one.

Most DSL services are compatible. I've swapped out several over the years.
Westell units lasted the longest. Get one of those and plug it into the DSL
telephone line. Then plug the WRT54G into the ethernet port on it. That's
the most common DSL setup, and what I've used for years.

-Bill Kearney

What's your problem?? So I got a few brand names turned around! We are
still both telling him to do exactly the same thing!


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Bill Kearney" <wkearney99@hotmail.com> wrote in message
news:wq-dnaOHqaglIh3VnZ2dnUVZ_j2dnZ2d@speakeasy.net...
>> 1. Get rid of the bridging mode and run the "modem" with full abilities
>> (modem/router) and get rid of the DLink box.
>
> The D-link box IS THE MODEM. Not exactly smart to suggest getting rid of
> it.
>
>> 2. Get rid of that thing and buy a "straight" modem and use it in
>> combination with the DLink.
>
> Erm, the D-link is the modem, getting another modem would help, how?
>
>> I recommend #2.
>
> With some corrections, it's basically the only choice. What he should
> keep is the LINKSYS unit, not the D-link one.
>
> Most DSL services are compatible. I've swapped out several over the
> years. Westell units lasted the longest. Get one of those and plug it
> into the DSL telephone line. Then plug the WRT54G into the ethernet port
> on it. That's the most common DSL setup, and what I've used for years.
>
> -Bill Kearney

Bill Kearney wrote:
> Most DSL services are compatible. I've swapped out several over the
> years. Westell units lasted the longest. Get one of those and plug it
> into the DSL telephone line. Then plug the WRT54G into the ethernet
> port on it. That's the most common DSL setup, and what I've used for
> years.
>
> -Bill Kearney

Bill is very correct. Just switch the DSL modem to bridge mode and let
your Linksys or whatever router do the routing. I do know that you have
to turn off the Westell DHCP server in bridge mode.

Its done all the time.

>
> Bill is very correct. Just switch the DSL modem to bridge mode and let
> your Linksys or whatever router do the routing. I do know that you have

The modem is in bridge mode (see my first post).

> Choose one:
>
> 1. Get rid of the bridging mode and run the "modem" with full abilities
> (modem/router) and get rid of the DLink box.

The modem/router only has one ethernet port (I need more than one,
hence the router) so getting rid of the router is not an option.

>
> or
>
> 2. Get rid of that thing and buy a "straight" modem and use it in
> combination with the DLink.

What is a "straight modem"? All the modems that I have seen here in NZ
have a ethernet port to connect to the computer and have DHCP. I have
never seen a modem without it.

Incidentially I have got the following script to work and allows me to
access the modem config pages from behind the router:

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

-Al

<BigAl.NZ@gmail.com> wrote in message
news:6458b5b7-b4b3-413a-90cf-06df47d2f6f6@v1g2000pra.googlegroups.com...
> >
>> Bill is very correct. Just switch the DSL modem to bridge mode and let
>> your Linksys or whatever router do the routing. I do know that you have
>
> The modem is in bridge mode (see my first post).

If it's in bridge mode then it would just pass ethernet packets to the
router and would not be running DHCP, nor would it need to be accessed via
TCP.

The westell unit I'm currently using is pretty 'dumb'. It can be accessed
via TCP but in general practice there's no point in doing that. It's a
set-and-forget kind of box. I don't know that the D-Link can be configured
to act in as basic a manner.

On Jul 20, 12:11*am, "Bill Kearney" <wkearne...@hotmail.com> wrote:
> <BigAl...@gmail.com> wrote in message
>
> news:6458b5b7-b4b3-413a-90cf-06df47d2f6f6@v1g2000pra.googlegroups.com...
>
>
>
> >> Bill is very correct. Just switch the DSL modem to bridge mode and let
> >> your Linksys or whatever router do the routing. I do know that you have
>
> > The modem is in bridge mode (see my first post).
>
> If it's in bridge mode then it would just pass ethernet packets to the
> router and would not be running DHCP, nor would it need to be accessed via
> TCP.
>
> The westell unit I'm currently using is pretty 'dumb'. *It can be accessed
> via TCP but in general practice there's no point in doing that. *It's a
> set-and-forget kind of box. *I don't know that the D-Link can be configured
> to act in as basic a manner.

The only reason I need to access the Dlink is I have been having a bit
of line trouble and its nice to be able to keep an eye on the line
stats.

Anyway it seems sorted now....