On Sun 24 Apr 2022 at 17:06:48 (+0200), Hans wrote:
> Am Sonntag, 24. April 2022, 16:53:49 CEST schrieb David Wright:
> Hi David,
> > So what are the contents of /etc/default/macchanger (after all,
> > putting ENABLE_ON_POST_UP_DOWN=YES would be interpreted as the
> > default, ENABLE_ON_POST_UP_DOWN=false), and what's getting logged
> > in /var/log/macchanger.log?
> > 
> 
> It is set =YES

Then I don't understand your problem. AFAICT, setting
ENABLE_ON_POST_UP_DOWN=YES
in /etc/default/macchanger will prevent ifupdown from running
macchanger. Then where's the bug?

I'm not in front of the machine, of course, so I can't choose
to look at anything I would like to. So, in the absence of
being told what's logged, I guess I'll draw the conversation
to a close.

> > It might be worth checking when macchanger is attempting to make its
> > change and see how this compares with when systemd is changing the
> > name of the relevant interface.
> > 
> It can be changed, whenever I set the interface to down (so that it is not in 
> use), thus telling me, macchanger is generally working.
> > BTW, looking at the package, the last entry in
> > /usr/share/doc/macchanger/changelog.gz is dated 2004-05-10 and the
> > last in /usr/share/doc/macchanger/changelog.Debian.gz 17 Jun 2018.
> 
> Hmm, there are some similar bugreports related to this issue, too.
> Let us hope, the mainatiner does fix them. 
> > 
> > As you're running systemd, any reason you're avoiding using its
> > own method?
> > 
> 
> Yes, because it does not work!

Systemd, or macchanger? In case I was unclear, systemd's own method
is to put MACAddressPolicy=random into a .link file. I wondered why
you don't use systemd's (sole, individual, unaided) method. Or does
that not work?

OTOH are you saying that the /combination/ of systemd driving macchanger
does not work? (That's why I asked about the timings earlier.)

As an example, it's well known that systemd and iwd, both set up to
perform "natively", create a race condition, mitigated by a systemd
.link file.

Now, I don't know how macchanger deals with any such possibility
(and, quite frankly, I don't really care either), but I'm not going
to figure it out remotely, am I. So while macchanger is apparently
configured not to run, as I said, I'll leave.

> However, for me personally I can fix it by 
> editing those files myself. But I am thinking of all the other people, who 
> want software, that is working. 
> 
> For myself, I will often find a solution, but I know a lot of people, who are 
> much less experienced than myself - those are in my mind (and are in the 
> devlopers, too, I hope).

Experienced bug reporters post the facts, rather than their
interpretation of those facts.

Cheers,
David.

Reply via email to