One IP for several Interfaces

Sten Carlsen stenc at s-carlsen.dk
Fri Feb 20 14:38:04 UTC 2015


I have been using this setup for years with MACs, no issue with
duplicated IPs.

I have given up on fixed addresses except for servers and use DDNS into
local server. Everything then has a name and I don't have to remember IPs.

Your problem as mentioned before is in your PC. It's a general
networking issue.


On 20/02/15 15:19, Simon Hobson wrote:
> Daniel Thielking <Daniel.Thielking at ias.rwth-aachen.de> wrote:
> 
>> host laptop-2-lan {
>>   hardware ethernet 18:03:73:7a:61:dd;
>>   fixed-address laptop-2.my.domain;
>> }
>>
>> host laptop-2-wireless {
>>   hardware ethernet 38:59:F9:0F:1D:ED;
>>   fixed-address laptop-2.my.domain;
>> }
>>
>> behind the laptop-2.my.domain DNS-Name ist one ip(192.168.1.32) configured in bind.
>>
>> Now to the problem:
>>
>> If I use laptop-2 in wireless mode everything works fine. If I want to use a cable both Interfaces are getting the same address. It manifests itself in a ip address conflict. How can I configure DHCPd to avoid this? But I do not want to use more than one address. 
> 
> OK, firstly it's not really "a DHCP problem".
> The only way to completely fix it is to ensure that only one interface is active at any time - that's easier said than done. However, I've (in the past) done exactly the same thing and it's worked just fine - client is Apple laptop running OS X. AFAICT OS X doesn't complain if you configure the same IP on two interfaces - it just uses the one that's configured to be higher up the list.
> 
> What is the client in your case ?
> 
> 
> 
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
> 

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"


More information about the dhcp-users mailing list