🚀 go-pugleaf

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
>
>