|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
Hi Everyone,
Who fills files in etc directory such as /etc/protocols, /etc/services and /etc/networks Can anybody please give me sample of /etc/networks I do not have /etc/networks in my linux system. Thanks, Datha Datha |
|
#2
|
|||
|
|||
|
Datha ha scritto:
> Hi Everyone, > Who fills files in etc directory such as /etc/protocols, /etc/services > and /etc/networks > Can anybody please give me sample of /etc/networks > I do not have /etc/networks in my linux system. > Thanks, > Datha > man network, man services, man protocols |
|
#3
|
|||
|
|||
|
On 3 Jan 2006 22:02:42 -0800, Datha
<(E-Mail Removed)> wrote: > Hi Everyone, > Who fills files in etc directory such as /etc/protocols, /etc/services > and /etc/networks > Can anybody please give me sample of /etc/networks > I do not have /etc/networks in my linux system. > Thanks, > Datha > man 5 protocols man 5 services man 5 networks (These man pages exist in Debian or Ubuntu. YMMV with other distros.) Each of these is a plain ascii file that shows the translation between numbers (protocol, port, or network IP address) and human-readable names. Some Linux distros may use /etc/sysconfig/networks instead of /etc/networks. The /etc(/sysconfig)/networks file, like /etc/hosts, is maintained by the local sysadmin. Unlike /etc/hosts, I don't think /etc/networks is required for network operation. The other two files are part of the basic OS distribution (the netbase package in Debian or Debian-based distros). On my system, the /etc/protocols ane /etc/services files begin with comments which contain URLs to www.iana.org. -- There is no comfort without pain; thus we define salvation through suffering. -- Cato |
|
#4
|
|||
|
|||
|
>Each of these is a plain ascii file that shows the translation between
>numbers (protocol, port, or network IP address) and human-readable >names. Some Linux distros may use /etc/sysconfig/networks instead of >/etc/networks. The /etc(/sysconfig)/networks file, like /etc/hosts, is >maintained by the local sysadmin. Unlike /etc/hosts, I don't think >/etc/networks is required for network operation. Correct, but you can use it to alias your networks, making administration easier. |
|
#5
|
|||
|
|||
|
Here is an example of ane /etc/networks file where the local network is
192.168.1. and all the hosts are on that subnet. (This the linksys router default) loopback 127.0.0.0 homenet 192.168.1.0 |
![]() |
| Tags |
| files, fills, or etc or networks, or etc or protocols, or etc or services |
| Thread Tools | |
| Display Modes | |
|
|