Citeren James Knott <james.knott@rogers.com>:
On 04/04/2018 09:57 AM, Arjen de Korte wrote:
Citeren James Knott <james.knott@rogers.com>:
On 04/04/2018 08:30 AM, Carlos E. R. wrote:
In fact, I try to set up the same IP on Windows for both interfaces, and it fails: the eth does not accept 192.168.1.50 and goes instead to 169.254.4.71, and WiFi reactivates.
People usually use DHCP these days, so you'd never see the same address assigned to the 2 interfaces.
With DHCPv4 that may be the case, but DHCPv6 will usually assign by DUID (https://tools.ietf.org/html/rfc3315#section-9). Only fairly recently it has become feasible to use MAC addresses in DHCPv6 (https://tools.ietf.org/html/rfc6939).
As long as I make sure WiFi and (wired) ethernet are not connected at the same time, the address they receive from my DHCPv6 server will be the same.
What happens if you have both interfaces active on the same network?
That is where the Duplicate Address Detection (DAD) kicks in. The DHCPv6 server will offer the same address on both interfaces, but the client will reject one when it sees it is already in use. In which case it depends on the server configuration if another address if offered or not. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org