#Blacklist mac address on switch Pc#
#Blacklist mac address on switch mac#

If you could determine the MAC, that would be a pretty big privacy violation. (There may be, but then it will be acting as a switch or hub, not as router.) But this is probably not the scenario you had in mind. The packet will still contain the destination IP, but there is no router between the two.

#Blacklist mac address on switch mac#

The client will broadcast a message on the LAN, asking for the MAC belonging to the server's IP, and then send it to that MAC. As I mentioned, the client first compares the IP subnet of itself and the destination. One exception to this is when the client is inside the same LAN as the server. (When a reply packet comes back at R1, other things make sure the packet finds its way to the client.) If you want to know why not all communication is simply MAC-based, have a look at this question on serverfault. For the communication to work, that's all it needs to know besides the original IP from R1. In the end, the server will only be able to see the MAC address from R3.

Moving forward, R2 will not tamper with any of the IPs like R1 did because it is not a NAT router (like most consumers have). Source MAC: 02:01:01:02:02:02 (belongs to: R1)Дestination MAC: 03:01:01:02:02:02 (belongs to: R2)ДЄs you can see, the destination IP doesn't change, but the MAC addresses changes every time it gets forwarded (by a router) based on which router it is forwarded to and which router it came from. The packet now contains: Source IP: 172.16.1.1 (public IP from R1) It changes the source IP to the public IP (so that the server can send a packet back), and forwards it to R2. Then R1 is like 'Oh, that IP is somewhere on the internet'. The packet contains: Source IP: 192.168.1.100 (belongs to: Client)Дestination IP: 10.1.1.1 (belongs to: Server)

The client then sends it to their router, R1, in the hope that it will be able to forward it to the destination. Nope, the server has a 10.x IP, and the client an IP.

If the client wants to send a packet to the server, it first checks whether the server is in the same subnet. To understand why, you must know a thing or two about how the internet works.Д¬ommunication between devices is commonly done via the Ethernet protocol (wiki), and despite the source and destination being identified by IP, actual communication is done per MAC. Therefore, configuring MAC filter rules effectively controls the Internet service access rights of PCs in a LAN.In short, the answer is no, you usually can't block based on MAC address.

#Blacklist mac address on switch Pc#

A PC may have more than one IP addresses but a unique MAC address. Configuring MAC filter rules enables the PCs that conform to the rules to access the Internet service or disables the PCs that do not conform to the rules to access the Internet service. The MAC address lists of PCs in the network are saved on the ONT. On the dialog box that is displayed, configure the MAC filter rule for the PC to access the Internet. In the pane on the right, after enabling MAC filter and selecting the filter mode, click New.

(1) Click Advanced Configuration > Security Configuration tab, and choose MAC Address Filtering in the navigation tree on the left. The following describes the two scenarios respectively. Huawei ONTs support MAC address filtering for wired and wireless networks. By setting MAC address filtering, you can allow only your own device to access the network (whitelist), or do not allow unauthorized devices to access the network (blacklist), effectively preventing unauthorized network access.