Which I know, all the Mac addresses going through the packets are in packets. It is because each packet is Goes in a certain path, should also return it in the same path. So, if the server's router knows about the client's MAC address (all of them), then why not for the information on server pages (like ASPX)?
Please, clarify. (Just tell me I'm wrong).
If I understand it correctly, then the client sends a packet that has a MAC address. When the packet goes through a proxy (such as a client router), the proxy address is also added to the packet and so on.
About the TCP / IP data line layer is a snippet from Wikipedia:
The data link layer is used to move the packet in the middle The Internet Layer interface of two different hosts on the same link, the process of transmitting and receiving packets on a given link can be controlled with the software device driver for the network card as well as the firmware or special chipset. Is combed. These work like adding a packet header to create data link functions such as for transmission, then actually broadcast the frames on a physical medium. TCP / IP models include specifications for transporting network addressing methods used in Internet Protocol to Data Link Addressing such as Media Access Control (MAC), although all the aspects below that level are considered existing in the link layer. , But are not clearly defined.
Actually, the MAC address is stored in the packet Packet's
turns at every hop of the journeyMac is a short story for media access control, in the context of the media local communication media. While the source and destination IP addresses remain the same for travel (and used for long distance routing decisions), source and destination MAC-addresses only indicate the next hop.
For this reason, the mac-address stored in the packet received by your server should be your presence-router, or the MAC address of your provider's device.
You may want to take a look at OSI Layer Model and
Comments
Post a Comment