#791978 F5 client does not play nicely with resolvconf

#791978#5
Date:
2015-07-09 18:30:06 UTC
From:
To:
for some bizarre reason resolvconf is not putting the tun0 resolvers
below that of eth* even though tun* is supposed to take precedence

crow@ts:~$ ll /etc/resolv.conf
lrwxrwxrwx 1 root root 31 Jun  4 15:55 /etc/resolv.conf ->
/etc/resolvconf/run/resolv.conf
crow@ts:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
nameserver 10.10.10.21
nameserver 10.10.10.20
search canaccord.com
----------------------------------------------------------------------
This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or subject to copyright. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The information contained in this e-mail is drawn from sources believed to be reliable, but the accuracy and completeness of the information is not guaranteed, nor in providing it does Canaccord Genuity Corp. or its subsidiaries, or affiliated companies, "The Firm" assume any liability.

Canaccord Genuity Corp., its subsidiaries or affiliated companies, disclaims all responsibility and accepts no liability (including negligence) for the consequences for any person acting, or refraining from acting, on such information. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. As a solicitation, this e-mail was intended for distribution in those jurisdictions where The Firm is registered as advisors or dealers in securities. Any unauthorized use, disclosure, distribution or copying of this communication by anyone other than the intended recipient is strictly prohibited.

When addressed to our clients, any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing Canaccord Genuity Corp., its subsidiaries or affiliated companies' client agreements.  If you have received this message in error, please notify us immediately by return email and destroy and delete the message from your computer.  (Disclaimer)

#791978#10
Date:
2015-07-09 18:54:01 UTC
From:
To:
----------------------------------------------------------------------
This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or subject to copyright. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The information contained in this e-mail is drawn from sources believed to be reliable, but the accuracy and completeness of the information is not guaranteed, nor in providing it does Canaccord Genuity Corp. or its subsidiaries, or affiliated companies, "The Firm" assume any liability.

Canaccord Genuity Corp., its subsidiaries or affiliated companies, disclaims all responsibility and accepts no liability (including negligence) for the consequences for any person acting, or refraining from acting, on such information. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. As a solicitation, this e-mail was intended for distribution in those jurisdictions where The Firm is registered as advisors or dealers in securities. Any unauthorized use, disclosure, distribution or copying of this communication by anyone other than the intended recipient is strictly prohibited.

When addressed to our clients, any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing Canaccord Genuity Corp., its subsidiaries or affiliated companies' client agreements.  If you have received this message in error, please notify us immediately by return email and destroy and delete the message from your computer.  (Disclaimer)

#791978#15
Date:
2015-07-10 08:42:07 UTC
From:
To:
Hi and thanks for the report.

Please run this command

    /usr/share/resolvconf/dump-debug-info

when you are experiencing the problem and post the output here.

#791978#18
Date:
2015-07-10 08:42:07 UTC
From:
To:
Hi and thanks for the report.

Please run this command

    /usr/share/resolvconf/dump-debug-info

when you are experiencing the problem and post the output here.

#791978#23
Date:
2015-07-10 16:39:00 UTC
From:
To:
Here ya go

thx for the quick reply!
---------------------------------------------------------------------- This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or subject to copyright. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The information contained in this e-mail is drawn from sources believed to be reliable, but the accuracy and completeness of the information is not guaranteed, nor in providing it does Canaccord Genuity Corp. or its subsidiaries, or affiliated companies, "The Firm" assume any liability. Canaccord Genuity Corp., its subsidiaries or affiliated companies, disclaims all responsibility and accepts no liability (including negligence) for the consequences for any person acting, or refraining from acting, on such information. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. As a solicitation, this e-mail was intended for distribution in those jurisdictions where The Firm is registered as advisors or dealers in securities. Any unauthorized use, disclosure, distribution or copying of this communication by anyone other than the intended recipient is strictly prohibited. When addressed to our clients, any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing Canaccord Genuity Corp., its subsidiaries or affiliated companies' client agreements. If you have received this message in error, please notify us immediately by return email and destroy and delete the message from your computer. (Disclaimer)
#791978#28
Date:
2015-07-10 20:50:04 UTC
From:
To:
I don't understand this. If tun* is supposed to take precedence over eth*
then resolvconf *shouldn't* put the tun0 resolver addresses *below* those
of eth* in resolv.conf; resolvconf should put the tun0 resolver addresses
*above* those of eth*.

And resolvconf does what it should do. According to interface-order, tun*
is listed before eth*. The record /run/resolvconf/interface/tun0.f5
contains

    nameserver 192.168.1.1
    nameserver 10.10.10.21
    nameserver 10.10.10.20
    search canaccord.com

whereas the record /run/resolvconf/interface/eth0.f5 contains

    search canaccord.com
    nameserver 10.10.10.21
    nameserver 10.10.10.20

and the record /run/resolvconf/interface/eth3.dhclient contains the
following.

    nameserver 192.168.1.1

The information from tun0.f5 should take precedence. And that is what we
see in resolv.conf.


    # Dynamic resolv.conf(5) file for glibc resolver(3) ...
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES ...
    nameserver 192.168.1.1
    nameserver 10.10.10.21
    nameserver 10.10.10.20
    search canaccord.com


If there is a problem then the problem is with the contents of the
record  /run/resolvconf/interface/tun0.f5 which comes from the program
that calls resolvconf to create that record. Which interface
configuration utility writes that record? What is "f5"?

#791978#31
Date:
2015-07-10 20:50:04 UTC
From:
To:
I don't understand this. If tun* is supposed to take precedence over eth*
then resolvconf *shouldn't* put the tun0 resolver addresses *below* those
of eth* in resolv.conf; resolvconf should put the tun0 resolver addresses
*above* those of eth*.

And resolvconf does what it should do. According to interface-order, tun*
is listed before eth*. The record /run/resolvconf/interface/tun0.f5
contains

    nameserver 192.168.1.1
    nameserver 10.10.10.21
    nameserver 10.10.10.20
    search canaccord.com

whereas the record /run/resolvconf/interface/eth0.f5 contains

    search canaccord.com
    nameserver 10.10.10.21
    nameserver 10.10.10.20

and the record /run/resolvconf/interface/eth3.dhclient contains the
following.

    nameserver 192.168.1.1

The information from tun0.f5 should take precedence. And that is what we
see in resolv.conf.


    # Dynamic resolv.conf(5) file for glibc resolver(3) ...
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES ...
    nameserver 192.168.1.1
    nameserver 10.10.10.21
    nameserver 10.10.10.20
    search canaccord.com


If there is a problem then the problem is with the contents of the
record  /run/resolvconf/interface/tun0.f5 which comes from the program
that calls resolvconf to create that record. Which interface
configuration utility writes that record? What is "f5"?

#791978#36
Date:
2015-07-10 21:03:46 UTC
From:
To:
I think I might know what the problem is... the proprietary f5 client
has some thread that sits in the background and monitors for changes
to resolv.conf and routing tables and "fixes" them. This is really a
side effect of paranoid corporate control freaks. I apologize for the
false bug report.

On the other hand, it would be really nice if Debian provided a way to
protect against draconian junk joisted upon innocent users.

I'd like to create a fakeroot fork lets the control-freak software
*think* its doing what it wants to the files, but the fakeroot program
would intercept and make inert these ridiculous attempts at "control"
---------------------------------------------------------------------- This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential or subject to copyright. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The information contained in this e-mail is drawn from sources believed to be reliable, but the accuracy and completeness of the information is not guaranteed, nor in providing it does Canaccord Genuity Corp. or its subsidiaries, or affiliated companies, "The Firm" assume any liability. Canaccord Genuity Corp., its subsidiaries or affiliated companies, disclaims all responsibility and accepts no liability (including negligence) for the consequences for any person acting, or refraining from acting, on such information. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. As a solicitation, this e-mail was intended for distribution in those jurisdictions where The Firm is registered as advisors or dealers in securities. Any unauthorized use, disclosure, distribution or copying of this communication by anyone other than the intended recipient is strictly prohibited. When addressed to our clients, any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing Canaccord Genuity Corp., its subsidiaries or affiliated companies' client agreements. If you have received this message in error, please notify us immediately by return email and destroy and delete the message from your computer. (Disclaimer)
#791978#41
Date:
2015-07-11 11:19:57 UTC
From:
To:
Ugh. Is there any way to switch off that feature?

No need to apologize, it's good to alert me and others to a package that
doesn't play nicely with resolvconf.

Let us know here if you find a good solution.

#791978#44
Date:
2015-07-11 11:19:57 UTC
From:
To:
Ugh. Is there any way to switch off that feature?

No need to apologize, it's good to alert me and others to a package that
doesn't play nicely with resolvconf.

Let us know here if you find a good solution.