Re: [chrony-dev] Re: chrony 3.4+ on multihomed machines forces wrong interface |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Re: chrony 3.4+ on multihomed machines forces wrong interface
- From: Arkadiusz Miśkiewicz <arekm@xxxxxxxx>
- Date: Tue, 28 Apr 2020 13:01:59 +0200
- Autocrypt: addr=arekm@xxxxxxxx; keydata= xsDiBDeGM8wRBACW2q58aSCXXgb1PSVOGSFAiQkh0J8mZO+eSawdkogv/J0W8fNWhtNuEYob czQUMZBe7GRD9KkeDROQx34agK7qWAhs3U5U1sPlczrxbwrsD0DbfKzCflEVxWL3QNy9IWZU ydHaoDSELvj55kIim+sVo1A2JeO1gZXDqYHOuZdTRwCg2u70NYS27Vks8MFroCHht6oeSo0D /02tBomjVzEluOQjGVG+Rg43y8vaMET8mHdc/aF4YMAv8VOgPQM6ztq68l2ze2t9Cx2g6klR laAFtECw8XtNlsZ3PH0ORfjqnNJ0gmMqUAcBVuZiTKh1E6J9aQVgf1ea6LPtu+YSKvLYTuYe YhQzVOsisYwT0eEMXfU5ywN8AQRnBACI7athvJ5mCyb10S/LoWguM7qIc2GxiDbKO+LCDIYr kIBDn6ElQUgBnBUeHoyMNWBQjR1JLY54gTj7SiOREAEmhS25edDuRmSjQQmWVFoMPzzfenHE CE36uBKVKG+PJitWfxNApSiaAWcKfOEiqfU8GQvMzflin/VB5MVJI4+SNs0lQXJrYWRpdXN6 IE1pc2tpZXdpY3ogPGFyZWttQG1hdmVuLnBsPsJgBBMRAgAgBQJHDIO6AhsDBgsJCAcDAgQV AggDBBYCAwECHgECF4AACgkQDKKLJD2xm71zowCgritIRHeLNGhqaEuOhfOXbpRGwLMAn2Se yUO91zgcK9Cr+bD4hYAL6OjyzsNNBEcMn/EQEAClMXJwoqfmUGD4uxv81dbgpIYbArGCsEfZ 7guiFI35HPcKNohtfttwywulHmM9i04yUAylBLuAq8HN08zJ2s4SP86MCrofs6YdLh2jM1qP R8cgKqV2JGmJ10C+Ez5PHsOaZQk4lXJFsVnYgexFANpylDYSpIXyx3nacHTfhJXLwP6djtV5 WJ2JoT8N6WBH6ISYVlp33c8E3j538xuqR4OisJhoXOgjWz/gJTu6igIdE8S7NntFR+9uH5ZI drtHsQ9K9E62Vv6XWdizu4+/sXeE46OfUjz6vqxn2Qk3LfnyYJd9F4ZDz9pUVMQ4BQCzp1I8 wKHUaKyPLNkm9MQTOSqwZwL0dZFL7giMDS0I7muaJ1XcOfw1Nb6E9ULSLR9KGDgAa8eHop5w mUKa09l4UwykeuR9ozI9FnCkrdZGaFZ/FRKOIEu9/bdwL8JYHwSD/2TbSky+cKIBcVrzynU1 BjAJ5TeKqY1dGtroVtzDjtq3iumql4GUr2gz341CgGykwiM7/0veXohESrpDjna66oZs8A0b zUwMEAiBpf8rJQO3VokKhK6juIkyETubLItnKwUWJ2PDROux1q+G4klSAXjKDOnWixliK17C lWCpIKUsgFF1JvkTheJN0UXD6VQPwXNZusLFj3ff06UmVbVsDf88tzHaTX9++dqTK0u7FKKR DwADBQ/7BeAibYcDHoPNQjQvhyeQ4+AFWlOBkGxGvU5JSaxvC3oYDhnsFiaCI/5EKQvwd5tJ KdhI33OqpbKpS/sXRfccsibpmYAU9JHrHRRFRpnI11W7cPE73ZRVe0IiI8RkEgshgrkVcShx 8l23GPc0UGULg5LcJzQHCwrUEG84aW4NuGsdQBCtg9U3dI8rBdOdrrU4jOXwDLfpwV4tv7bV ptlGIXaxnZljVNHSVgXXAOoBsuh5z+eG1VsPiWmIE/SO3+6vB0aUMoZVm457ZgW60Ar0ronb QItPWxObpn/V+yVYqGKAlli1kZoA5L9VBEw4hGHP0Wiz8gGjqjQhd6l+DQ2XIOfs0mSFNUl+ rSgYOxnOxHunTUIGOj4N4MdODuJKo+IhcsdgGl9Z0fS7uS6uES4k6ERw5mUOLdFKEwLfAIgr oi6Fqrhac7NSKJQgLdt40BkVJlbU+Tk/muWQMbTTeT+wbYnKscy5O2ErHAA308thjsth4AH9 3W72+L7vGJuAEcyG2d+s8pV6y2qVD6NIa7vCAMmcfqmF/Q1bzuhnUqt021agMfq4FihrKRfS z99SsNIFV8L209GMiWxeaQ6tWsA5nq1iizjmevpAsuM6V1Taxz4XNXd+uDkoS1gvUf7Nns2b 4bmT4a/mWWx1HgBp8L2T+0FJcnSZz9slWL1LjAt3DJPCSQQYEQIACQUCRwyf8QIbDAAKCRAM ooskPbGbveW8AKCg16mRAW7pWxVNifB32ebrtfrbOwCcCN1QEiO9ipQVIGQPN0UJdZvzvzQ=
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maven.pl; s=maven; h=to:references:from:autocrypt:subject:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=LrLyZDjFMdv5LZMyQv+3mVguZGpRW/o6coclF5SXTn4=; b=h12DuqyTm6UmuIK9Ht2cQOJUIteZyd/tk1f7nM5I8O2IcwaPmkFQXOILV6C3qogVEJ gtrrq3C7Ik3gyRIZ4REwR9D7j/rJcFuPXcK3LUmTb/QJWuqaRvUOf5VcYx2Xl0bbmzrr Jqozi633Ued0oep3d+JlYy79to1IFSgPSebEg=
On 28/04/2020 12:23, Miroslav Lichvar wrote:
> On Tue, Apr 28, 2020 at 11:57:31AM +0200, Arkadiusz Miśkiewicz wrote:
>> On 28/04/2020 11:43, Arkadiusz Miśkiewicz wrote:
>>
>>> Now why kernel discards such sendmsg() without immediate error - no idea.
>>
>> This is about similar problem and explains things
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781732
>
> The difference with NTP is that responding from the same interface is
> preferred for best accuracy. In DNS it doesn't matter.
>
>> Anyway forcing interface index looks to be wrong (bypasses routing
>> table) solution to problem which that commit tried to fix.
>
> Do you have a suggestion for a different fix?
What was the original problem that
5fc7674e366fa1bfda162bdaba57243cff0a55a7 tried to fix?