The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Not able to ping WAN side network from LAN side

    Discussion in 'Networking and Wireless' started by tufani, Dec 2, 2008.

  1. tufani

    tufani Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Hi ,
    I have flashed my WGR614L with OpenWRT but I am not able to ping a host in my WAN side network from LAN side ......
    Could any body plz tell me what should I do ....
     
    tufani, Dec 2, 2008
    #1
  2. focusfre4k

    focusfre4k Notebook Evangelist

    Reputations:
    149
    Messages:
    569
    Likes Received:
    0
    Trophy Points:
    30
    by WAN side you mean a host out on the internet somewhere correct? you personally should not have any devices on the WAN unless you have some type of hosting or something. please clarify.

    if its a public device whats the IP/hostname?
     
    focusfre4k, Dec 2, 2008
    #2
  3. tufani

    tufani Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    Yes it is a public device with IP 192.168.10.1 .
    I have given the WAN interface on the board an IP 192.168.10.133.
    If i ping 192.168.10.1 from board its working but if I try to do the same from a PC connected to LAN port its not working .....
    Please let me know if I m able to clarify my point or not ...
     
    tufani, Dec 2, 2008
    #3
  4. blue68f100

    blue68f100 Notebook Virtuoso

    Reputations:
    1,020
    Messages:
    3,439
    Likes Received:
    0
    Trophy Points:
    105
    First you will need to disable the routers firewall or put the pc in a DMZ. The PC must also be setup to respond on ping. If it is running a Personal FW it too must be disabled or ports open for this to happen. If your trying to setup a web server ISP block these ports. You must have a business class service to run servers. FTP ports are not normally blocked, but you will be pounded by hackers 24/7 .
     
    blue68f100, Dec 2, 2008
    #4
  5. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    It cannot be a "public" device if it's got an IP of 192.168.10.1 - all of the IP addresses that start 192.168.xxx.yyy are so-called "private" IP addresses that can only be used within private subnetworks (i.e., networks that are separated from the internet by one or more gateways, like your router).
     
    Shyster1, Dec 2, 2008
    #5
  6. blue68f100

    blue68f100 Notebook Virtuoso

    Reputations:
    1,020
    Messages:
    3,439
    Likes Received:
    0
    Trophy Points:
    105
    Some ISP issue private IP's to prevent users from setting up servers. This way they do not use up there limited number of IP's, save for business. As you know if you have a private IP (192.168.x.x.) it can not be located on the www. So if you have a IP in the 192.168.x.x you are just a node on a larger private network.

    I don't even thing the DynDNS services will work.
     
    blue68f100, Dec 2, 2008
    #6
  7. nizzy1115

    nizzy1115 Notebook Prophet

    Reputations:
    2,557
    Messages:
    6,682
    Likes Received:
    1
    Trophy Points:
    205
    Your absolutely right, i do not understand how he thinks his private address is public.

    Private addresses are:

    10.0.0.0 – 10.255.255.255
    172.16.0.0 – 172.31.255.255
    192.168.0.0 – 192.168.255.255
     
    nizzy1115, Dec 2, 2008
    #7