Two hosts communication in the local area network (LAN) is an IP or a MAC-CodePudding

Ask a simple question:
I use a connection for three computers, switch IP configuration for 192.168.1.1 and 192.168.1.2 instead and 192.168.1.3
1.1 1.2 and 1.1 should be use IP + 1.2 port visit, so has the following problems:
Layer 2 switches don't know the IP, will receive 1.1 request packet, flood to 1.2 and 1.3
So 1.2 is through unpacked see to confirm is sent to the destination IP is own data?
Behind to send packets will contain 1.1 1.2 MAC? What is the MAC layer devices record in 1.1 the host?

CodePudding user response:

1.1 1.2, first check your 1.1 1.2 MAC address is had in the arp list, if not, just send broadcast an arp request packet ask 1.2 MAC address is what, after the switch to see this broadcast packets each port will send a out, after he received the broadcast packets 1.2 1.2 1.1 tell him to send arp reply to the corresponding MAC address is what, switches received 1.2 package to check their own CAM table, find the MAC address of the corresponding forwarding port after 1.1, is separate from the port to send every mouth, if you don't have to find 1.1 card to see the MAC address of the packet is for their own, will the package take the receiving data packets, and raise the interrupt told system protocol stack will collect package parsing and 1.2 MAC address written to the arp table, at the same time will access the package of 1.2 the purpose of the MAC address set ChengGangCai arp reply to come over to the address information of the package sent out...

CodePudding user response:

reference 1st floor kinkon007 response:

1.1 1.2, first check your 1.1 1.2 MAC address is had in the arp list, if not, just send broadcast an arp request packet ask 1.2 MAC address is what, after the switch to see this broadcast packets each port will send a out, after he received the broadcast packets 1.2 1.2 1.1 tell him to send arp reply to the corresponding MAC address is what, switches received the package to check their own CAM table 1.2, 1.1 find the MAC address of the corresponding forwarding port, is separate from the port to send every mouth, if you don't have to find a 1.1 nic to see the MAC address of the packet is for their own, will the package take the receiving data packets, and raise the interrupt told system protocol stack will collect package parsing and 1.2 MAC address written to the arp table, at the same time will access the package of 1.2 the purpose of the MAC address set ChengGangCai arp reply to come over to the address information of the package sent out...

1.2 after receiving this broadcast packets to send arp reply to 1.2 1.1 tell him what the corresponding MAC address is
1.2 is by IP confirm this package is sent to their own, since 1.3 can also received the request the packet

CodePudding user response:

refer to the second floor tuteng181 response:

Quote: refer to 1st floor kinkon007 response:
1.1, 1.2, 1.1 check yourself arp 1.2 MAC address is had in the list, if not, just send broadcast an arp request packet ask 1.2 MAC address is what, after the switch to see this broadcast packets each port will send a out, after he received the broadcast packets 1.2 1.2 1.1 tell him to send arp reply to the corresponding MAC address is what, switches received the package to check their own CAM table 1.2, 1.1 find the MAC address of the corresponding forwarding port, is separate from the port to send every mouth, if you don't have to find a 1.1 nic to see the MAC address of the packet is for their own, will the package take the receiving data packets, and raise the interrupt told system protocol stack will collect package parsing and 1.2 MAC address written to the arp table, at the same time will access the package of 1.2 the purpose of the MAC address set ChengGangCai arp reply to come over to the address information of the package sent out...

1.2 after receiving this broadcast packets to send arp reply to 1.2 1.1 tell him what the corresponding MAC address is
1.2 is confirmed that the package is sent to your via IP, since 1.3 can also received the request the packet

Yes, the request packet is a broadcast packets, each machine in the broadcast domain can be received, but only 1.2 IP can match, so 1.3 check to IP is not to own immediately lose the package,

CodePudding user response:

reference kinkon007 reply: 3/f

Quote: refer to the second floor tuteng181 response:

Quote: refer to 1st floor kinkon007 response:
1.1 1.2, first check your 1.1 1.2 MAC address is had in the arp list, if not, just send broadcast an arp request packet ask 1.2 MAC address is what, after the switch to see this broadcast packets each port will send a out, after he received the broadcast packets 1.2 1.2 1.1 tell him to send arp reply to the corresponding MAC address is what, switches received the package to check their own CAM table 1.2, 1.1 find the MAC address of the corresponding forwarding port, is separate from the port to send every mouth, if you don't have to find a 1.1 nic to see the MAC address of the packet is for their own, will the package take the receiving data packets, and raise the interrupt told system protocol stack will collect package parsing and 1.2 MAC address written to the arp table, at the same time will access the package of 1.2 the purpose of the MAC address set ChengGangCai arp reply to come over to the address information of the package sent out...

1.2 after receiving this broadcast packets to send arp reply to 1.2 1.1 tell him what the corresponding MAC address is
1.2 is confirmed that the package is sent to your via IP, since 1.3 can also received the request the packet

Yes, the request packet is a broadcast packets, each machine in the broadcast domain can be received, but only 1.2 IP can match, so 1.3 check to IP is not give yourself immediately lose the package,

Arp list is switch record? Or local network card record? In addition if the Internet access will also record the MAC to a remote server?

CodePudding user response:

Tuteng181

reference 4 floor response:

Quote: refer to the third floor kinkon007 response:

Quote: refer to the second floor tuteng181 response:

Quote: refer to 1st floor kinkon007 response:
1.1 1.2, first check your 1.1 1.2 MAC address is had in the arp list, if not, just send broadcast an arp request packet ask 1.2 MAC address is what, after the switch to see this broadcast packets each port will send a out, after he received the broadcast packets 1.2 1.2 1.1 tell him to send arp reply to the corresponding MAC address is what, switches received the package to check their own CAM table 1.2, 1.1 find the MAC address of the corresponding forwarding port, is separate from the port to send every mouth, if you don't have to find a 1.1 nic to see the MAC address of the packet is for their own, will the package take the receiving data packets, and raise the interrupt told system protocol stack will collect package parsing and 1.2 MAC address written to the arp table, at the same time will access the package of 1.2 the purpose of the MAC address set ChengGangCai arp reply to come over to the address information of the package sent out...

1.2 after receiving this broadcast packets to send arp reply to 1.2 1.1 tell him what the corresponding MAC address is
1.2 is confirmed that the package is sent to your via IP, since 1.3 can also received the request the packet

Yes, the request packet is a broadcast packets, each machine in the broadcast domain can be received, but only 1.2 IP can match, so 1.3 check to IP is not give yourself immediately lose the package,

Arp list is switch record? Or local network card record? In addition if the Internet access will also record the MAC to a remote server?

Arp list is your native protocol stack to record table, to the local protocol stack and contract them out to find out, only record this period of machine of MAC, switches, CAM table, has its own maintenance in the remote server does not record in local, unless the server and the machine in the same network segment,

CodePudding user response:

The

refer to the original poster tuteng181 response:

ask a simple question:
I use a connection for three computers, switch IP configuration for 192.168.1.1 and 192.168.1.2 instead and 192.168.1.3
1.1 1.2 and 1.1 should be use IP + 1.2 port visit, so has the following problems:
Layer 2 switches don't know the IP, will receive 1.1 request packet, flood to 1.2 and 1.3
So 1.2 is through unpacked see to confirm is sent to the destination IP is own data?
Behind to send packets will contain 1.1 1.2 MAC? What is the MAC layer devices record in 1.1 the host?

of course, is to rely on the MAC, switches have ARP table,

CodePudding user response:

refer to 6th floor m0_46087520 response:

Quote: refer to the original poster tuteng181 response:

Ask a simple question:
I use a connection for three computers, switch IP configuration for 192.168.1.1 and 192.168.1.2 instead and 192.168.1.3
1.1 1.2 and 1.1 should be use IP + 1.2 port visit, so has the following problems:
Layer 2 switches don't know the IP, will receive 1.1 request packet, flood to 1.2 and 1.3
So 1.2 is through unpacked see to confirm is sent to the destination IP is own data?
Behind to send packets will contain 1.1 1.2 MAC? What is the MAC layer devices record in 1.1 the host?

of course, is to rely on the MAC, switches have ARP table,

The traditional switch is no ARP table, have a plenty of CAM table, it is a MAC switch interface mapping table, rather than a MAC and IP mapping, with the development of technology and the network requirements, some manageable switch will have ARP table, used to implement more features,

CodePudding user response:

MAC table is enough to communicatenullnullnullnullnullnull