On Sat, Nov 16, 2019 at 7:05 PM Sam Varshavchik wrote:
>
> I have a fixed IP address assigned via DHCP to a machine that I
> just updated to F31.
>
> After the update, I was slightly surprised when it didn't come up
> on its fixed IP address. After looking through the logs, the DHCP
> server is no
On Sat, 16 Nov 2019 14:18:17 -0500
Sam Varshavchik wrote:
> So, it's HWADDR in the ifcfg for the actual physical interface, and MACADDR
> for TYPE=Bridge?
Actually you can use MACADDR on a physical interface as well to
spoof a different mac. Anything that queries the mac is being
mediated by th
Tom Horsley writes:
On Sat, 16 Nov 2019 13:48:43 -0500
Tom Horsley wrote:
> You can make things normal again
> by adding the HWADDR="same mac as physical interface"
> parameter to the ifcfg- file.
Wups! I tell a lie. The parameter you need is
MACADDR, not HWADDR.
So, it's HWADDR in the ifcfg
On Sat, 16 Nov 2019 13:48:43 -0500
Tom Horsley wrote:
> You can make things normal again
> by adding the HWADDR="same mac as physical interface"
> parameter to the ifcfg- file.
Wups! I tell a lie. The parameter you need is
MACADDR, not HWADDR.
Here's my ifcfg-br0:
# Networking Interface
DEVICE=
On Sat, 16 Nov 2019 13:04:50 -0500
Sam Varshavchik wrote:
> DHCP server is now
> apparently getting a DHCP request from a different MAC address, apparently
> the bridge's MAC address.
Yep, for some reason (they are calling a "bug") the bridge no
longer gets the same MAC as the one physical in
I have a fixed IP address assigned via DHCP to a machine that I just
updated to F31.
After the update, I was slightly surprised when it didn't come up on its
fixed IP address. After looking through the logs, the DHCP server is now
apparently getting a DHCP request from a different MAC addre
