|
|
What actually makes this work?
Any one got any ideas how to do with with other routers? I've got a Linksys WRT54G, and I'm I would like to replicate this neat trick. As far I was aware DHCP allocates IP address per MAC address on a lease basis, and since the AipPort and Eth adaptor have a different MAC they get given different IP addresses? What is it in this hint that allows it to work? Surely when you disconnect the LAN cable there is no time to release the lease on IP, so how is that IP still free to be reallocated to the AirPort. I have a linux server I could use as a DHCP server, and I believe my router has bridging capabilies (although I've not tried them). Any one got any ideas for me to try? Thanks, Dave
What actually makes this work?
The key to the initial post is this phrase "configured my own DHCP server". Most DHCP servers (e.g., that you'd run on a server running Linux or BSD and not on a wireless router) allow for the setting of mappings from specific MAC addresses to specific IP addresses. The WRT54G does not offer this capability.
What actually makes this work?
Since it's YOUR LAN, why not just set up a network location for your LAN and assign a static IP address to each interface that's the same (not using DCHP at all)? Sounds like it would do the same thing but without the DHCP challenge.
What actually makes this work?
Right, I'm running my own DHCP server on my LAN, but if you're not running a DHCP server, you should be able to set the IP address manually in the Network System Preferences.
It's not as complicated as you think...
I don't think you actually need to do any configuration on the DHCP server at all. I've been using the same setup (moving from lan to wireless without dropping connections) for a while now. The secret is to set your DHCP Client ID to the same on both interfaces. As an aside, if you set it to the same as in your Sharing control panel and make it a single word with just letters and numbers (no spaces), the DHCP server will record your client name and correctly configure dyndns (if you have it setup).
It's not as complicated as you think...
It depends on the situation. I tend to prefer making changes on my DHCP server so I don't have to mess around with each client machine's settings :-)
It's not as complicated as you think...
Well, I prefer to change my iBook setup, rather than all the DHCP servers I come in contact with in a normal work day :) |
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.06 seconds |
|