On 1/31/20 10:31 AM, Tom Hughes wrote:
> On 31/01/2020 15:29, Tom Hughes wrote:
>> On 31/01/2020 15:23, Steve Dickson wrote:
>>
I know there was a change with systemd-networkd in a recent release so
that it now creates a unique but persistent MAC for bridges and maybe
other systems
On 31/01/2020 15:29, Tom Hughes wrote:
On 31/01/2020 15:23, Steve Dickson wrote:
I know there was a change with systemd-networkd in a recent release so
that it now creates a unique but persistent MAC for bridges and maybe
other systems like NetworkManager have done the same?
Hmm... this seems
On 31/01/2020 15:23, Steve Dickson wrote:
I know there was a change with systemd-networkd in a recent release so
that it now creates a unique but persistent MAC for bridges and maybe
other systems like NetworkManager have done the same?
Hmm... this seems odd to me... any idea why this was done?
On 1/31/20 9:55 AM, Tom Hughes wrote:
> On 31/01/2020 14:28, Steve Dickson wrote:
>
>> I've recently updated my laptop to F31. Then I was no longer
>> able to ssh into it. After a little debugging... it turns
>> out my laptop was not getting the expected ip address
>> from DHCP. The reason for t
On 31/01/2020 14:28, Steve Dickson wrote:
I've recently updated my laptop to F31. Then I was no longer
able to ssh into it. After a little debugging... it turns
out my laptop was not getting the expected ip address
from DHCP. The reason for that was the MAC address it was
sending to dhcpd had ch
Hello,
I've recently updated my laptop to F31. Then I was no longer
able to ssh into it. After a little debugging... it turns
out my laptop was not getting the expected ip address
from DHCP. The reason for that was the MAC address it was
sending to dhcpd had change!!! Looking at the interfaces
