On Tue, Jul 15, 2014 at 6:33 PM, poma wrote:
> On 15.07.2014 09:01, poma wrote:
>>
>>
>> This sometimes works, sometimes not. :)
>> https://bugzilla.redhat.com/show_bug.cgi?id=1119481
>>
>
> Resolved.
> https://bugzilla.redhat.com/attachment.cgi?id=918197
> https://bugzilla.redhat.com/attachment.c
On 15.07.2014 09:01, poma wrote:
This sometimes works, sometimes not. :)
https://bugzilla.redhat.com/show_bug.cgi?id=1119481
Resolved.
https://bugzilla.redhat.com/attachment.cgi?id=918197
https://bugzilla.redhat.com/attachment.cgi?id=918198
poma
This sometimes works, sometimes not. :)
https://bugzilla.redhat.com/show_bug.cgi?id=1119481
poma
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 06/16/2014 03:09 PM, Tom Gundersen wrote:
Hi poma,
So do I understand correctly that it all works as expected for you now?
Cheers,
Tom
Yep!
poma
man: networkd - netdev MAC addition
diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml
index c17ae9e..931d806 100644
--- a/man/sy
Hi poma,
So do I understand correctly that it all works as expected for you now?
Cheers,
Tom
On Mon, Jun 16, 2014 at 3:05 PM, poma wrote:
>
> MACA ddress in addition to
> /etc/systemd/network/bridge0.netdev:
> [NetDev]
> Name=bridge0
> Kind=bridge
> MACAddress=00:12:34:56:78:90
>
> The rest is
MACA ddress in addition to
/etc/systemd/network/bridge0.netdev:
[NetDev]
Name=bridge0
Kind=bridge
MACAddress=00:12:34:56:78:90
The rest is here:
https://bugzilla.redhat.com/attachment.cgi?id=881142
journal-sd-networkd-214-2.git4997cb9.20140615-3.16.0-0.rc:
[ 16.629830] sd[1]: Starting Network
Whether predictable EHA may be applicable to bonding also?
To remind myself without caffeine, heh.
https://www.kernel.org/doc/Documentation/networking/bonding.txt
15. Frequently Asked Questions
8. Where does a bonding device get its MAC address from?
When using slave devices that
On 05.06.2014 12:05, Tom Gundersen wrote:
Thanks for the reminder. I'll revert the revert :)
We grew some more features since it was first introduced, so will have
to check out how it all works with tunnels, veth devices etc, but
should definitely have this back for 314.
Cheers,
Tom
Predicta
Thanks for the reminder. I'll revert the revert :)
We grew some more features since it was first introduced, so will have
to check out how it all works with tunnels, veth devices etc, but
should definitely have this back for 314.
Cheers,
Tom
On Thu, Jun 5, 2014 at 12:00 PM, poma wrote:
>
> Bri
Bridgetto is in the stable 3.14.5 kernel.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=4a68caa
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.5
.
commit 4a68caa1b3d3f382bde56a6a3d3430bcb53ecf7f
Author: Toshiaki Makita
Date: Fri Apr 25 17:01:18 2
On 12.05.2014 20:53, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 7:44 PM, poma wrote:
>> Why am I seeing this commit on git/stable,
>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/net/bridge/br_netlink.c?id=30313a3
>> but not in stable complete tarball,
>> https:/
On Mon, May 12, 2014 at 7:44 PM, poma wrote:
> Why am I seeing this commit on git/stable,
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/net/bridge/br_netlink.c?id=30313a3
> but not in stable complete tarball,
> https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.14
On 05/12/2014 05:45 PM, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 5:27 PM, poma wrote:
>> On 12.05.2014 12:22, Tom Gundersen wrote:
>>> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
>>> wrote:
>>> This should really be added as AFAICT there is currently no way to match
>>> on v
On Mon, May 12, 2014 at 5:27 PM, poma wrote:
> On 12.05.2014 12:22, Tom Gundersen wrote:
>> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
>> wrote:
>> This should really be added as AFAICT there is currently no way to match
>> on virtual devices like briges, TAP devices, batman-adv
On 12.05.2014 12:22, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
> wrote:
> This should really be added as AFAICT there is currently no way to match
> on virtual devices like briges, TAP devices, batman-adv devices, etc...
> which have neither a persisten
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
wrote:
This should really be added as AFAICT there is currently no way to match
on virtual devices like briges, TAP devices, batman-adv devices, etc...
which have neither a persistent MAC address nor an ID_PATH to match on.
>>>
>>>
>>> This should really be added as AFAICT there is currently no way to match
>>> on virtual devices like briges, TAP devices, batman-adv devices, etc...
>>> which have neither a persistent MAC address nor an ID_PATH to match on.
>>
>> So I think what we should do here is to allow MAC address (and o
On 04/22/2014 04:07 PM, Tom Gundersen wrote:
> Hi Matthias,
>
> On Fri, Apr 18, 2014 at 1:08 AM, Matthias Schiffer
> wrote:
>> On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
>>> On 04/17/2014 11:28 PM, Dave Reisner wrote:
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
>
Hi Matthias,
On Fri, Apr 18, 2014 at 1:08 AM, Matthias Schiffer
wrote:
> On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
>> On 04/17/2014 11:28 PM, Dave Reisner wrote:
>>> On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
Hi,
I'd like to configure the MAC address of a
On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
> On 04/17/2014 11:28 PM, Dave Reisner wrote:
>> On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
>>> Hi,
>>> I'd like to configure the MAC address of a bridge device statically (as
>>> bridges tend to change their MAC address depen
On 04/17/2014 11:28 PM, Dave Reisner wrote:
> On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
>> Hi,
>> I'd like to configure the MAC address of a bridge device statically (as
>> bridges tend to change their MAC address depending on the order the
>> ports are added on Linux other
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
> Hi,
> I'd like to configure the MAC address of a bridge device statically (as
> bridges tend to change their MAC address depending on the order the
> ports are added on Linux otherwise), but there doesn't seem to be a way
> to mat
Hi,
I'd like to configure the MAC address of a bridge device statically (as
bridges tend to change their MAC address depending on the order the
ports are added on Linux otherwise), but there doesn't seem to be a way
to match for a bridge in a .link unit. This would be very useful for
macvlans as we
23 matches
Mail list logo
