1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Anyone help with configuration / static route

Discussion in 'Linksys Official Firmware' started by ffr58kk90, Oct 21, 2007.

  1. ffr58kk90

    ffr58kk90 LI Guru Member

    Hi guys'
    Here is the layout of my lan,

    ISP supplied ip 212.57.xxx.xxx
    Netgear WG302
    wireless link
    Netgear WG302
    Linksys WRT54G 212.57.xxx.xxx wan address
    | | | |
    192.168.0.xxx fixed ip's to local pc's

    The two WG302's carry the internet from my isp to a remote location which is
    not accessable by wired connection.
    The WG302 ip address's are effectiveley transparent, it is simply
    cat5 in ----- wireless connection --- Cat5 out
    Everything works perfectly, however I would like to add the facility of being
    able to monitor / configure the WG302 link from the 192.168.0.xxx machines connected to the lan side of the WRT54G.
    All units are running stock firmware, I use fixed ips' no dhcp.

    I have tried numerous things from threads on here but not managed to get it to work.
    Should I not simply be able to add a static route to assign to the Wan port? If so, I can't get it to work.

    If not how can I acheive it?
    I am a bit of a novice with lan's!!!!

    Any ideas much appreciated.

  2. mstombs

    mstombs Network Guru Member

    I'm not sure you can do this with stock firmware. I assume the WRT54G is running NAT so everything it sends via the WAN port appears to come from the ISP supplied WAN IP address.

    The problem may be that the WG302's do not have a route to be able to reply. You may just need to add a secondary IP address in the same local range as the to the WRT54G (which I don't think you can do with stock linksys firmware).

    If you give the WRT54G a static WAN address in the local range say, can you access the WG302's (but not the internet!)?
  3. ffr58kk90

    ffr58kk90 LI Guru Member

    Hello mstombs

    Thanks you for the reply, I don't think that it is running NAT, I have the same ip address in the static ip section that I have been given by my isp.

    Yep, If I make the static ip address in the WRT54G, I can access both WG302's but not the internet.

    I have another WRT54GS that has the latest Tomato firmware, tried it on this too but without any sucess.
    I guess that what I am trying to achieve is to have the 212.57.xxx.xxx ip range and the 192.168.1.xxx range on the WAN port simultaneously

  4. HennieM

    HennieM Network Guru Member

    The 192 addresses on the WGs are like apples in a crate full of oranges - they are there, but you can't use 'em. Private addresses don't work on a public net (except with some very fancy manual routing). Your connection to the WGs are going from IP 212.57.xxx.xxx to 192.168.x.x, without routing - the IP packets don't know where to go.

    Best solution IMHO is to move the WAN termination upstream (closer to the ISP), and carry the signal on your private net, but you'll most likely have to use both your WRTs; e.g.:

    212.57.xxx.xxx (WAN port)
    WRT1 (this can be any routing device - ethernet wired-to-wired) (LAN port)
    | (LAN port)
    | | |
    Other PCs (with IP addresses in the range -, netmask, gateway
  5. mstombs

    mstombs Network Guru Member

    In Tomato (same or equivalent in other 3rd party firmware) you can assign a secondary IP/Alias to the WAN port with the command

    ifconfig vlan1:0 netmask

    The WRT54GS should use this to communicate with the WG's and they should be able to reply. And when the command works you can add it to the init (may have to add delay if it runs too early) or wanup script.
  6. ffr58kk90

    ffr58kk90 LI Guru Member

    Thanks for the info, I tried the command

    ifconfig vlan1:0 netmask
    on the WRT54G with Tomato firmware and it works!!
    I can access the WG302's now.
    I will put the commands in the stratup later this evening.

    Thanks again for the info

  7. mstombs

    mstombs Network Guru Member

    Glad that it works - just one issue - you don't normally use the .0 address in a netmask, as this is used to define the network and not an entry in it. The .255 at the other end of the range is used as a broadcast address. But if it works it works!

Share This Page