AUTHOR'S MAIN SITE  »  OVERVIEW: client/ server work

WIPA / LIPA: IP Addresses

"IP (Internet Protocol) Address" is a widely used term.

WIPA and LIPA are "my" terms. They stand for...

"WAN IP Address" and "LAN IP Address", "WAN" being another way of saying "Wide Area Network", i.e. "the internet".


A typical LAN IP address (LIPA) starts 192.168. That's followed by two more numbers, both less than 256, separated by periods ("full stops"). So, the following is an example of a full LIPA:

A WIPA also consists of four numbers, each less than 256, separated by periods.


A device on a LAN will have a LIPA. That may be "static", and determined by setting inside the device. Or it may be "assigned to it" by the LAN's DHCP server. If your LAN has some devices configured to use static LIPAs, your LAN's DHCP server needs to have had some blocks of LIPAs set aside for those devices. In other words, the DHCP needs to "know" not to use any of the addresses used by devices which do not ask the DHCP for a LIPA.

"Things" connected to the internet have WIPAs. For the home user, this will fundamentally be their router; it will have a WIPA. And that WIPA will have been assigned to it by the user's internet service provider.

Servers which the home users set up on their LANs may (if everything has been set up properly. (Or if there's been a lapse in setting security high enough!) be accessible from outside the LAN, over the internet.

The visitor from outside the LAN will "see" the server on the LAN as being "at" the router's WIPA.

Routers are Very Clever Bits Of Kit. They take care of passing messages back and forth between users outside the LAN and devices connected locally to the LAN. How does the router know which local device to pass a message to? If the request to connect comes with an explicit statement of the port the outside user wants to connect over, then the router will have been told: "Things arriving for port xx should go to the device at LIPA yy". In some cases, the system can "fall back" to "the usual". For instance, if something "ordinary" comes in from a web browser out there on the internet, the router, absent any other instructions, will send it to the LIPA where it thinks there is a web server, or where it knows there is something set up to handle things arriving for port 80, the default HTTP port. Things for FTP servers default to port 21. But you will often want or need to be explicit about ports, and will sometimes want to set things up to use ports other than the default port for a given service.

Subnet masks

In the work these pages are meant to facilitate, you are sometimes asked to provice a "sub-net mask". I tend to use That seems to take care of my needs without giving rise to problems.

Sundry general points

Please remember the material is copyright, TK Boyd, 2013 and later. There is more on this on the footers of "higher" pages.

Ad from page's editor: Yes.. I do enjoy compiling these things for you... I hope they are helpful. However.. this doesn't pay my bills!!! If you find this stuff useful, (and you run an MS-DOS or Windows PC) please visit my freeware and shareware page, download something, and circulate it for me? Links on your page to this page would also be appreciated!

PLEASE >>> Click here to visit editor's Sheepdog Software (tm) freeware, shareware pages <<< PLEASE

Editor's email address. Suggestions welcomed!     - - -    Want a site hosted, or email? I like 1&1's services.

Test for valid HTML Page has been tested for compliance with INDUSTRY (not MS-only) standards, using the free, publicly accessible validator at It passes in some important ways, but still needs work to fully meet HTML 5 expectations. (If your browser hides your history, you may have to put the page's URL into the validator by hand. Check what page the validator looked at before becoming alarmed by a "not found" or "wrong doctype".)

AND passes... Test for valid CSS

. . . . . P a g e . . . E n d s . . . . .