create new tag
, view all tags
The network related pages on WikiLearn (those that exist, plus those that are yet to be created) need to be better organized. This page is an attempt to start that effort.

The typical formatted search approach that I've used elsewhere is just not going to be sufficient, AFAICT, so, although I will include a formatted search (on the word "network" anywhere in the name of a page), I will also experiment with something different, perhaps a list of terminology which needs to be understood and a list of tasks which might be performed, with links to individual (?) wiki pages for each.

Disclaimer: It is not my intent to write about all aspects of networking, only those that I need to deal with. Others are welcome to add information (pages) to WikiLearn to cover things that I do not cover. On this page I may include links to pages that I may not create in the near future (or ever), I think creating the links will help create an outline that is ready for coverage of those topics.

Aside: Should this page be named:

  • NetworkingTOC
  • NetworkTOC
  • ??




The *nix "based on networking" vs. the Microsoft "networking added on" [philosophy | evolution | concept | ??]

Is it relevant to touch on the same point re databases? Is it the same point?

Some good introductory resources — arranged in an appropriate reading order (from elementary to advanced). BTW, link 3 deals uses the old style networking commands, link 4 uses the new style (iproute2), IIUC:

  1. Linux Networking-concepts HOWTO; Rusty Russell; R: 1.13; 2001/07/29 — "This document describes what a network (such as the Internet) is, and the very basics of how it works." — An excellent introduction, even though he calls it an "unreliable-guide"
  2. Linux Networking HOWTO; Joshua Drake; v1.7.1; © — I'm tempted to tell you to skip ahead and start your reading at chapter 4. — I'm just having trouble reading this one, for a number of reasons: frames, too much introductory material, konquerors handling of font size increases and decreases (not wrapping to the width of the page when I get a font size large enough to read), the $2.50 solicitation on every page (well, I won't go back and confirm that, but it seems that way — annoying through the first three introductory chapters especially), the residual HTML entities [ [ ... — But, I'm still trying to read it.
  3. Linux Advanced Routing & Traffic Control HOWTO; Bert Hubert, et. al.; Rev. 1.12; 2002/07/20 — seems useful to me so far, working through it and issuing the ip commands on one or more of my systems. It seems quite good, but at a certain point it seemed to make a quantum jump (around the discussion of the example (one LAN through two providers to the Internet (?) — it doesn't match exactly what I want to do, and it uses a lot of variables, so I have to do a lot of interpolation to figure out what I need. Probably better to print some of those pages, and markup as I read.
  4. The Network Administrators' Guide; Olaf Kirch — I haven't started reading this, might be fairly old — the first date I see is in 1996.

Some others that might be useful:

Hmm, I used to not like to read the HOWTOs, now (some of them) seem OK. (I used to look for more [simplified | Window-fied | modern ] (magazine type) articles.) Why the change? Maybe I understand more of the terminology now? (host, etc., etc., etc.) Maybe I'm focused on specific HOWTOs (instead of simply trying to read the HOWTOs, by going to a list of them and trying to pick out some that seem interesting or appropriate (~"the mind works better as a treasure hunter than a vacuum cleaner"?). Anyway, they are not all as bad as I once thought they were. Maybe they and I are changing?


Should I put them in alphabetic order, or attempt some sort of logical order? Or, put them in a table in my attempt at a logical order, and rely on the table sort mechanism to allow them to be sorted (temporarily) into alphabetic order if desired by the reader? The latter sounds like it's at least worth a try. (The next attempt could use the "comma" approach, e.g., "domain name, fully qualified".

domain name
fully qualified domain name
public network
private network
routing table

The unusual services




Same decision as above? I'll try it.

For some tasks that might be done differently for a public vs. a private network, I'm going to try including prefixes (or suffixes?) as follows:

  • Pun — public network
  • Prn — private network

Or, maybe I should cover both in two sections on the same page? I want to aim for: understandability (provide the necessary background info, either on the same page or in a link), clarity (clear, easy to understand language, avoid off-topic meanderings, etc.), focus (let somebody find exactly what they need, without a bunch of explanation or meandering that might not be what they need), but let them find the explanation easily if they need it, ???

Hmm, clearly some of these tasks are bigger than others. Setting a multihomed host up as a router is a much bigger task / topic than Pun Picking an IP Address — maybe I need a hierarchy of pages (and an index) — a page like Network Names and Addresses with the pages like Pun Picking an IP Address as subpages? Similarly, maybe move the lists of terms and commands to their own pages? Boy do I wish TWiki (or some editor compatible with TWiki) had Word style collapsible outlines — I'm getting tempted to move this page offline to Word for construction, then bring it back later — I guess (but will have to check) that I could incorporate the appropriate markup (---++ for Level 2 heading, etc.) in customized Word styles — and of course Word lets me define keyboard macros. Boy, it sounds tempting. But, IIRC, I moved some editing to Word once before and I'm not sure I ever moved it back. Anyway, not today.

Aside: Need to check the "official" (canonical) definition of "multihomed" — if I have a host (oh, no, I'm using Unix terminology, I think I'm going to hate myself in the morning) with multiple NICs but all with the same IP address, is that considered "multihomed"?

Pun Picking an IP Address
Prn Picking an IP Address
Pun Picking a Hostname
Prn Picking a Hostname
Pun Picking a Domain Name
Prn Picking a Domain Name
Setting the IP Address
Setting the Host Name
Setting the Domain Name
Not Setting an IP Address DHCP
Install and Configure a Modem
Install and Configure a Nic
Multihomed Host as Router
Setting up a Web Server
Setting up an Email Server
Setting up a Telnet Server
Setting up an SSH Server
Setting up a Samba Server
Setting up a Server
Setting up a Server
Setting up a Server
Setting up a Server
Setting up a Server
Setting up a Web Client
Setting up an Email Client
Setting up a Telnet Client
Setting up an SSH Client
Setting up a Samba Client
Setting up a Client
Setting up a Client
Setting up a Client
Setting up a Client
Setting up a Client
Setting up a Tunnel

List of Network Related Pages

To add additional network related pages, simply create a new page using a name prefixed with "Network"nn...

  • Page Title: Summary

  • BltTermsLinuxNetworkingAndRemoteAccess: See BLT . Linux Networking and Remote access, Stefan Waidele IP Address DNS /etc/hosts /etc/resolv.conf localhost Client process Server process...

  • BltTermsLinuxTelecommunicationsAndNetworking: See BLT . Linux Telecommunications and Networking, Henry White Netscape archie finger ftp gopher pine ping...

  • ConfiguringANetwork: This page is turning into a random discussion of how to go about presenting networking on WikiLearn. I originally intended this page to be more about how to configure...

  • IRulu_Networking: iRulu 10.1` Model AX105 with Android 4.2 Networking Starting a rewrite There are a variety of reasons to connect your iRulu to your home network (LAN): you...

  • IRulu_NetworkingAnomalies: iRulu 10.1` Model AX105 with Android 4.2 Networking Anomalies I`m currently rewriting the page Networking and expect that, when that page is complete, everything...

  • LinuxWindowsNetworkTerms: Some translations between Linux and Windows for networking terms (commands, files, etc.). (Because I`m forgetting windows stuff.) See AboutThesePages. Contents...

  • ManagingNetworkBandwidth: Collecting resources about managing network bandwidth quotas and similar. See AboutThesePages. Contents Notes Resources See ResourceRecommendations. Feel...

  • NFSNetworking: Integrated into NFS .

  • NetworkBridging: Notes and resources on creating a network bridge in a Linux box. See: AboutThesePages Contents Notes Resources See ResourceRecommendations. Feel free to...

  • NetworkDHCP: DHCP (Dynamic Host Configuration Protocol) is a client / server technology to automatically (dynamically) assign TCP/IP addresses to computers on a network. See:...

  • NetworkDesignResources: Collecting resources on network design issues. See AboutThesePages. Contents Notes Resources See ResourceRecommendations. Feel free to add additional resources...

  • NetworkInterfaceCardsNICs: NICs (Network Interface Cards) are the cards that interface between a computer and a network (Ethernet, Token Ring, ArcNet, ???). See NICs for cards with a dedicated...

  • NetworkNat: Notes and resources on doing NAT (Network Address Translation) in a Linux box (to create a network gateway). Double checking, do I already have a page started on...

  • NetworkRouting: See also: NetworkNat Gateway Iproute NetworkBridging Not sure if this is really a different topic than the first three above, possibly...

  • NetworkTunneling: (Network) Tunneling is a way to (securely??) access another network (possibly your employers) over an insecure network, like the Internet. Re `(securely??)` could...

  • NetworkWithApplicationServerAndXTerminals: Making notes from the excellent series of articles by Colin Mattoon: How to create a Linux based network of computers for peanuts. I think the title of the article...

  • NetworkingHandlingManyClients: Handling many clients (maybe 10,000 to be exact) ; ) saw the first resource here and skimmed part of it looks like it should be useful if you have the need to...

  • NetworkingHostname: Notes and resources on setting the hostname in Linux, and to some extent, its use in Postfix. See also some of the pages on Postfix somewhere I learned (and recorded...

  • NetworkingNotes: This page is intended to document what might be considered networking notes or anomalies things that make sense in the context of networking, but are somewhat strange...

  • NetworkingResources: See AboutThesePages. Contents Notes Resources See ResourceRecommendations. Feel free to add additional resources to these lists, but please follow the guidelines...

  • NetworkingTOC: The network related pages on WikiLearn (those that exist, plus those that are yet to be created) need to be better organized. This page is an attempt to start that...

  • SlashEtcSlashNetworkSlashInterfaces: /etc/network/interfaces clearly has something to do with starting up the network interfaces, presumably runs at boot time, and probably only if the runlevel calls...

  • WirelessNetworking: Resources and notes for wireless networking. Because: I`m at least 22,000 feet from my central telephone office, DSL is not an option, my cable company...


  • () RandyKramer - 26 May 2003
  • If you edit this page: add your name here; move this to the next line; and if you've used a comment marker (your initials in parenthesis), include it before your WikiName.

Page Ratings

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2003-05-26 - RandyKramer
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding WikiLearn? WebBottomBar">Send feedback
See TWiki's New Look