|
|
Use a DHCP client identifier
I've been doing this for a while, and I always inteded to write up a hint after some more testing.
Use a DHCP client identifier
Actually, what seems to happen is that MacOS X doesn't use the MAC address as a DHCP identifier. It generates another unique string from the DHCP Client ID and other information. The side effect of this is that if all interfaces have the same DHCP Client ID entered then all interfaces get the same IP address if they are talking to the same DHCP server. You can see this if you look at the DHCP server leases, for windows boxes they will show the MAC address. For MacOS X boxes it will show a much longer string.
Use a DHCP client identifier
My, that's very cool. I've had two IP addresses for my laptop, because I couldn't figure out how to give both the Ethernet and Airport the same one. It hasn't really been a big deal, since the connection would switch back and forth even though the IP was different, even for a chat client (amazing!), but it did make my DNS entries annoying. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|