- #LOM MAC ADDRESS VS PASSTHROUGH MAC ADDRESS UPDATE#
- #LOM MAC ADDRESS VS PASSTHROUGH MAC ADDRESS MAC#
That might be useful, and it would certainly simplify things for you, but I don't know if that exists.
#LOM MAC ADDRESS VS PASSTHROUGH MAC ADDRESS MAC#
The USB3 to Ethernet dongle problem won't go away though, unless maybe you can find a Dell USB3 to Ethernet dongle that supports MAC Address Passthrough.
#LOM MAC ADDRESS VS PASSTHROUGH MAC ADDRESS UPDATE#
This sounds like a firmware bug, which means it might get fixed by a firmware update even if it's broken today, because it should work exactly the way you hope. Did you check that?Īgain, I don't think that the article you found applies to you. I asked if you were running the latest firmware on both the laptop and the dock. As a result, MAC Address Passthrough capability should definitely be working for you when using a Latitude 7400 and a WD19. Your systems are still configured to DHCP, and although they will always RECEIVE the same IP address whenever they are on a particular network segment, the system is still configured for DHCP. That article applies to static IP addresses, meaning an IP address configured directly within Windows. The other common scenario would be if you had network switches that only allowed specific MAC addresses to be on the network.īut if you're using DHCP reservations, then the article that you found and marked as the solution does NOT apply to you. Hey, Dell, please make SysAdmin life a little bit Ok, setting DHCP reservations based on MAC address is probably the most reason to have MAC Address Passthrough. That is why I am so interested in the MAC address pass-through feature. (but if the user forget to carry the dongle and try to use a borrowed one, he will no get the right IP address.) To make things worse, the Latitude 7400 does not come with a network port, they come with a USB 3 to ethernet dongle, so we are configuring the dongle MAC address to be transferred to the docking. The solution we found for this is to assign the MAC address of the notebook to the Realtek Gigabit controller of the docking, using the advanced properties of the controller, "network address" option. In the good old times when docking stations did not have its own ethernet adapter we did not have any problem, just a unique MAC address. These "time travelers" do not have an assigned office and may connect either to a docking station or a wall ethernet jack. In each location we configure a MAC address reservation in order to assign the notebook the same IP address (I mean, the same "x"). Lets say location A has an notebook IP segment address of 10.6.2.x, and location B: 10.5.2.x We do not have an integrated Active Directory but the domains are linked. We have roaming users that travel with their notebooks to different branches of our company.
![lom mac address vs passthrough mac address lom mac address vs passthrough mac address](https://ccna-200-301.online/wp-content/uploads/2020/04/Ethernet-MAC-Address.png)
![lom mac address vs passthrough mac address lom mac address vs passthrough mac address](https://i.ebayimg.com/images/g/sqsAAOSw-tZgFNKy/s-l1600.jpg)
(please ignore any grammar or syntax mistake, my native language is not English) I will try to explain why I need to have a known MAC address (and always the same) no matter in which docking or wall jack the notebook is connected. And having Thunderbolt boot support bypasses security for devices connected during boot, which again should only be enabled if you actually need to use Thunderbolt devices at boot, and the WD19 is not a Thunderbolt device.īut in terms of the original issue, just out of curiosity, are you running the latest firmware on both the system AND the you very much for your reply.
![lom mac address vs passthrough mac address lom mac address vs passthrough mac address](https://access.redhat.com/webassets/avalon/d/Red_Hat_Enterprise_Linux-7-Networking_Guide-en-US/images/befcf7a9fb973e1a9d0b38c4070c5609/Network_Configuration-NM-Bonding-Add_Connection.png)
The WD19 is a regular USB-C dock, not a Thunderbolt dock, so those settings will not make any difference on the WD19, but disabling Thunderbolt port security opens up significant security risks because Thunderbolt grants access to PCIe, which in trusn allows direct access to system memory, so if you disable the authorization requirement, someone can simply connect a device to that system's Thunderbolt port and dump the contents of system memory, which might include things like passwords, encryption keys, etc. In any case, I would strongly recommend that you switch the Thunderbolt security back to the default User Authorization and disable Thunderbolt boot support.
![lom mac address vs passthrough mac address lom mac address vs passthrough mac address](https://forums.fogproject.org/assets/uploads/files/1638379854194-fog-mac-same.jpg)
I'm not sure why an OS-level IP configuration would affect firmware-level MAC Address Passthrough behavior in the first place, though. Are you actually configuring your laptops with static IPs? Otherwise, I'm not sure that note applies, since it specifically mentions "docked static IP portables", which I would read to mean "docked systems that have a static IP configured".