WRT54G v.8 Different?

Discussion in 'Cisco/Linksys Wireless Routers' started by fred3, Dec 21, 2007.

  1. fred3

    fred3 Network Guru Member

    I know the antennas are different...
    I recently installed one behind another router/modem and expected to be able to reach through the WRT to the next up router's control panel / web page (at a normal private IP address).
    It didn't work.

    Since I do this sort of thing all the time, I wonder if somehow the v.8 has a "feature" that by default prevents reaching through to a private IP address?
  2. HennieM

    HennieM Network Guru Member

    You'll have to provide some more detail Fred. What does the "chain" of connections look like. How are the routers connected to one another, i.e. router LAN port to router B LAN port / wireless / WAN,.... Does, and if so, where, does the internet come in. What firmware are you running on which router?
    Can you ping the upstream router, etc., etc. Where in the chain and how (LAN, wireless, WAN) is the PC connected?

    But, to answer your question, no, I don't know if the v8 is different.... I would doubt though, that it would "feature" a connection on port 80 like this out:

    PC ---->LANport-V8-LANport---->OtherSomething
  3. fred3

    fred3 Network Guru Member

    PC <> WRT54G v.8 <> Modem/router
    192.168.2.x <> 1l2.168.2.1 = <> = internet IP
    LAN <> LAN = WAN <> LAN = internet
    PC can't ping or see - which, in my experience, is unusual.
  4. HennieM

    HennieM Network Guru Member

    Is your V8 set to ROUTER (not gateway)?
  5. fred3

    fred3 Network Guru Member

    I didn't check that setting. It should have been the default as it was new out of the box. So, that's Gateway, no?
  6. HennieM

    HennieM Network Guru Member

    Default (out of the box) would be gateway, which means to do NAT when routing through the WAN port. Router mode means just route without NAT. In your setup, you don't want double NAT for starters, but also because NAT would probably block any traffic coming from the WAN side of the NATted router.
  7. fred3

    fred3 Network Guru Member

    Double NAT doesn't cause any problems in typical situations and is often useful depending on the objectives of the network. I set them up both ways depending on what's going on and what's easiest. For example, one can't reach the 2nd layer from the 1st layer (of private IP addresses) - i.e. can't reach the 2nd router's LAN from the 1st router's LAN via the 2nd router's WAN. But the reverse isn't blocked.
  8. frenchy2k1

    frenchy2k1 LI Guru Member

    you'll have to add a static route on your v8 so that it knows that is on its WAN port, as this is normally a local address (hence expected on the LAN port).
    When you ping 192.168.X.X, this will be sent to the LAN ports, except if you have a static route going on.

    edit: you may need a 3rd party FW for that. I use thibor and i'm quite out of touch on which functions are from the original FW and which was added.
  9. fred3

    fred3 Network Guru Member

    Hmmm... I've always done this on Linksys routers like WRT54xx v.x on WAN and on LAN.
    I would call "local" the LAN side.
    Note that both are "private" .. is that what you meant?

    Why do you say 192.168.x.x and not 192.168.1.x?

    LAN can see WAN devices in this case. Devices on WAN can't see this LAN.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice