Edit host netgroups

A "host netgroup" (hence "netgroup") can be compared to a guest list when you are inviting somebody to a party. You have made the guest list to avoid unwanted guests, for instance crooks. In a computer network, the guests are a bit different. They are "Internet hosts", e.g. printers, thin client servers or workstations. If these hosts are on the guest list, they are welcome to do their task on the network. If they are not, they are automaticly kept out by the door-keeper.

A netgroup thus keeps track of the guests, or "hosts" in "Internet lingo". It can also keep track of other netgroups, and this adds to simplified administration of e.g. access to the Internet or to a file server. It is much easier to administrate groups of hosts than stating every single host everywhere.

You have to use netgroups correctly to avoid extra administration. It is useless to have for example a netgroup named "workstation-hosts" with 250 different hosts in it. It is better to use sub groups. The workstations could be grouped into "computerlab01-hosts", "computerlab02-hosts" and "teachers-hosts", and these could be subgroups to another netgroup named "workstation-hosts".

In the future, will probably use netgroups for other various tasks. Today they are used to prevent unwanted guests to the file server.

The netgroup module

To edit netgroups, you have to use Webmin. The module is named "Edit host netgroups" and is found under the "System"-tab.

On a newly installed -tjener, the following netgroups are added:


All the thin client servers in the network.


All the printers in the network.


All the servers in the network. This is primarily "tjener", but if you move e.g. the backup service to another host, add that host here.


All the groups containing workstations, or all the workstations in a small network.


This group contains no hosts, but all other netgroups.

Naming conventions: Note how all the netgroup names end with "-hosts". This is to make it easier to distinct netgroups from other groups where it should become necessary. We suggest you use the same naming convention.