On Jul 10, 2015 11:04 PM, "Stephen Crowley" wrote:
>
> 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.
Ugh. Is there any way to switch off that featur
> resolvconf is not putting the tun0 resolvers
> below that of eth* even though tun* is supposed to take precedence
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
2 matches
Mail list logo
