The router is displaying your local IP it is in the form 192.XXX.XXX.XXX. The ip that you need is your public IP. Now if you are self hosting your web site you will have to forward the correct port. This will pass it's location from the local net to the rest of the world. This topic is covered in the first link.
The next thing to consider is the matter of dynamic versus static IP
The most obvious way to self-host is to obtain a static IP address from your ISP, buy a domain name and map the domain name to the static IP. This solution is really for the technical user, since it requires configuration of the Server, ports, installation of security tools and so on. The prices for static IP address range from $10 per month to $15 per month. Many ISPs offer static IPs to their customers.
In situations where your IP address changes every time you reconnect to the internet (known as Dynamic IP), Dynamic DNS solutions provide a mechanism to keep your domain name pointed to your current IP address. This frees you from having to invest in a static IP. A software IP update-agent on your home computer continually updates the DNS map with your Dynamic DNS provider.
Although your Dynamic DNS server may update his mapping potentially every minute, there can be a considerable time lag for propagation of an update across ISPs around the world. During this delay, not all users will be able to see your website. The reason for the delay is as follows. Each DNS entry consists not only of the domain name and its IP address, and a TTL entry which is the amount of seconds a DNS server may hold this particular domain information in its cache before it must refresh the information from a higher-level server. Dynamic DNS providers usually set this expiration time to one minute or so. The DNS servers that ISPs use usually don't host any domains of their own, they're basically just giant caches. The first time the reader asks for the domain name the ISP server probably won't know it so it looks it up. The Dynamic DNS provider tells the ISP's server to only keep the domain information in its cache for 60 seconds. However, there are DNS servers that ignore TTL entries and the expiration times and decide on their own to cache domain information for a longer duration, even as much as a week. Furthermore, reader computers cache domain information for a fixed duration as well. In such situations, Dynamic DNS mapping takes time to propagate, and your home-hosted website can become intermittently inaccessible.
Although a solution based on Dynamic DNS does not require investment in a fixed IP, it can give intermittent problems, and is also beyond the expertise of most home users.