등록일 1999.04.10 압축파일 (zip) | 무료


Subnetting is not only an organizational benefit, it is frequently a natural consequence of hardware boundaries. The viewpoint of a host on a given physical network, such as an Ethe
et, is a very limited one: the only hosts it is able to talk to directly are those of the network it is on. All other hosts can be accessed only through so-called gateways. A gateway is a host that is connected to two or more physical networks simultaneously and is configured to switch packets between them.
For IP to be able to easily recognize if a host is on a local physical network, different physical networks have to belong to different IP-networks. For example the network number is reserved for hosts on the mathematics LAN. When sending a datagram to quark, the network software on erdos immediately sees from the IP-address,, that the destination host is on a different physical network, and therefore can be reached only through a gateway (sophus by default).

sophus itself is connected to two distinct subnets: the Mathematics Department, and the campus backbone. It accesses each through a different interface, eth0 and fddi0, respectively. Now, what IP-address do we assign it? Should we give it one on subnet, or on

The answer is: both. When talking to a host on the Maths LAN, sophus should use an IP-address of, and when talking to a host on the backbone, it should use

Thus, a gateway is assigned one IP-address per network it is on. These addresses--- along with the corresponding netmask--- are tied to the interface the subnet is accessed through. Thus, the mapping of interfaces and addresses for sophus would look like this:


      최근 구매한 회원 학교정보 보기
      1. 최근 2주간 다운받은 회원수와 학교정보이며
         구매한 본인의 구매정보도 함께 표시됩니다.
      2. 매시 정각마다 업데이트 됩니다. (02:00 ~ 21:00)
      3. 구매자의 학교정보가 없는 경우 기타로 표시됩니다.
      최근 본 자료더보기