- Name: Zhu devout
- Student ID: 201821121021
- Class: calculated 1811
Network Topology
The network is a simple network, a pc with a machine servers.
Configuration parameters
ip address of the pc and the server are: 192.168.1.254,192.168.1.21.
Ethereal details and analysis of captured packets
HTTP REQUEST details:
HTTP Data:Accept-Language: en-us Accept: */* Connection: close Host: 192.168.1.21
The first line "HTTP Data: Accept-Language: en-us" request line, wherein: "HTTP" is a method of operation, "Data: Accept-Language: en-us" to receive a text version.
After the third acts of the header line, where "Accept", "Connection", "Host", led by the Ministry of field names, their corresponding meanings are clients willing to accept the type of data, a proxy server, the client specifies the http server they want to access domain name / IP address and port number.
"Accept: * / *" represents receiving any data type: The document "Connection close" to tell the server after sending a request can release link. "Host: 192.168.1.21" specify the http server they want to access the client domain name / IP address and port number.
By generating new questions and answers about the experiment
One question, when the same pc client and server ip, can normally access the server
Upon examination, the effect is as shown:
After the end of the original ip 192.168.1.254 for the pc changed 192.168.1.21, web access ip192.168.1.21 by our original configuration of the pc-ip address is automatically cleared, and did not send packets to the server. Description, the same network, the same ip address two instruments can not be directly linked.
Second question, when you change the network address and subnet address, but also whether the normal link
Upon examination, the effect is as shown:
Ip is accessed through the original web after ip192.168.1.21 192.168.1.254 to 172.24.97.1, discovery request packet is not issued, indicating that the network address for the subnet address can not be accessed simply by ip.
References:
[1] binding Wireshark packet capture depth understanding of the TCP / IP stack
[2] binding Wireshark packet capture depth understanding of the TCP / IP protocol stack of HTTP