Matthias Schiffer <mschif...@universe-factory.net> on Tue, 2014/07/01 07:08: > On 07/01/2014 05:56 AM, Christian Hesse wrote: > > Matthias Schiffer <mschif...@universe-factory.net> on Mon, 2014/06/30 > > 23:47: > >> On 06/24/2014 12:25 PM, Tom Gundersen wrote: > >>> On Tue, Jun 24, 2014 at 12:14 PM, Vasiliy Tolstov <v.tols...@selfip.ru> > >>> wrote: > >>>> Hi. I have very strange task: > >>> > >>> Not tested, but I would start with trying: > >>> > >>>> 1) Nedd modprobe dummy > >>> > >>> Use modules-load.d > >>> > >>>> 2) Assign specific mac address to it > >>> > >>> Possibly use .link files, or check if it is possible to spcify this as > >>> module options (didn't check). > >>> > >>>> 3) Bring up it > >>>> 4) Assign specific address to it > >>> > >>> Use a regular .network file... Should wokr. > >>> > >>> HTH, > >>> > >>> Tom > >> > >> I'm not sure if this has changed recently, but I think it is not > >> possible to use .link files to configure virtual network devices as > >> there is _nothing_ to match on. > > > > Sure. You have a name. That is what I tried first and it works perfectly. > > > > [Match] > > Name=dummy0 > > > > Or did I miss anything? > > > > No, Name= matches only work in .network units, not in .link units. A > link unit without any valid match option matches any interface though; > so if you have a .link unit with Name=dummy0 in its [Match] section, it > will actually be applied to dummy0... but also to all other interfaces, > which can be very confusing.
Of course you are right. I do have a dummy0.network unit.
Sorry for the noise.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
