There are almost no private corporate networks that consists of a single LAN, and many domestic environments have multiple networks. So the question of "why private addresses rather than MAC address" assumes that all non-public networks are simple single flat networks. However, a MAC address is a layer 2 address, and by definition only allows communication between items on the local network. When an IP packet arrives at your router and the NAT table shows that it is destined for your private address 192.168.1.10, the router will do a look up to see what the MAC address of 192.168.1.10 is, and send the packet to that MAC address. Ultimately, all packets are delivered to a MAC address. It is also totally possible to wrap other networking protocol data (that is not an IP packet) in an Ethernet frame for transmission. And applications should not have to care so as long as the destination IP address is reachable. Note: it is totally possible for IP packets to be delivered in another data link protocol other than Ethernet (guess what, your dial-up or DSL modem is not connected to your ISP via an Ethernet cable). The router retrieves the IP packet from the frame, looks at the address and determines the next node (and its MAC address) to pass it along, and sends it that direction in another Ethernet frame. If remote network, look for MAC address of default gateway router to send the IP packet, also within an Ethernet frame.If local network, look for MAC address corresponding to that IP address and send the IP packet direct, which is in an Ethernet frame. It is the operating system's networking stack that determines if the IP address is local or remote: That way applications just define the destination IP address in the IP packet, fill it with data (which is actually packed into a TCP/UDP segment), and send it along the way without having to worry how the underlying layers deal with the actual transmission. So regardless of whether the remote computer/node you wish to communicate with is in your local network or in some other network halfway round the globe, that logical link is established with TCP/IP. To check this, run the following command in the Terminal and verify the network adapter for which you want to change the MAC address.The answer is your software applications and operating system are designed to communicate using TCP/IP, not directly with Ethernet MAC addressing. Some Macs may use "en1" instead of "en0".Make sure to use an administrator account to perform the procedure.It might be a good idea to note down your existing MAC addresses in case something goes wrong. If you still experience problems, just reboot your Mac to reset the MAC address. If you're experiencing network issues after changing the MAC address, restart your router and try connecting to it again.Thankfully, most Macs are low-maintenance and won't need rebooting often. It also means there's no way to permanently change the MAC address on a Mac. To restore your original MAC address, simply reboot your Mac.To verify your MAC address has changed successfully, just recheck it using the procedure we discussed at the beginning.Here are some additional tips to help you through the process: Additional Tips While Changing Your Mac's MAC Address
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |