Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2020-06-11 Thread Igor Scheller
Hi, On 12.06.18 14:32, Samuel Thibault wrote: > Ok, then netcfg-static needs to be improved to do that. > [...] >> let's just flag the Debian IPv6 implementation as broken on this point >> and move on. > And let it stay broken at vitam æternam?... > > It's a matter of someone fixing the code. It

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Samuel Thibault
Bjørn Mork, le mar. 12 juin 2018 15:19:25 +0200, a ecrit: > Samuel Thibault writes: > > > It's a matter of someone fixing the code. It seems Igor Scheller is > > happy to work on it, he just needs a way forward, not being only told > > that what is currently there is nonsense. > > Well, using

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Samuel Thibault
Bjørn Mork, le mar. 12 juin 2018 14:12:28 +0200, a ecrit: > Samuel Thibault writes: > > Bjørn Mork, le mar. 12 juin 2018 13:30:39 +0200, a ecrit: > >> But this will: > >> > >> frtest3:~# ip route add 2001:db8:f00::1/128 dev eth1 > > > > So this is a route, which can be checked for. > > No, it

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Samuel Thibault
Bjørn Mork, le mar. 12 juin 2018 13:30:39 +0200, a ecrit: > But this will: > > frtest3:~# ip route add 2001:db8:f00::1/128 dev eth1 So this is a route, which can be checked for. > > which is the point of the test AIUI. > > The test is pointless. There is absolutely no requirement that the >

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Samuel Thibault
Igor Scheller, le mar. 12 juin 2018 11:28:58 +0200, a ecrit: > Imho it could be a better option to just configure the interface and > test if something is reachable? "something" is the problem. We do test for reachability of the mirror anyway. But again, checking that there actually is a route

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Samuel Thibault
Bjørn Mork, le mar. 12 juin 2018 10:52:30 +0200, a ecrit: > Huh? What is this? There is no "gateway must be in subnet" requirement > in IPv6. The gateway must only be reachable, which means that you must > be able to resolve the L2 address using ND. Before that, you need a route, which is the

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Igor Scheller
On 12.06.2018 10:52, Bjørn Mork wrote: > Igor Scheller writes: > > From 6bff2dee11a8d5493f87ec541f854e3897ef6a9a Mon Sep 17 00:00:00 2001 >> From: Igor Scheller >> Date: Mon, 11 Jun 2018 23:52:37 +0200 >> Subject: [PATCH] Added support for fe80 addresses as gateway >> >> --- >> netcfg-common.c

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-12 Thread Bjørn Mork
Igor Scheller writes: From 6bff2dee11a8d5493f87ec541f854e3897ef6a9a Mon Sep 17 00:00:00 2001 > From: Igor Scheller > Date: Mon, 11 Jun 2018 23:52:37 +0200 > Subject: [PATCH] Added support for fe80 addresses as gateway > > --- > netcfg-common.c | 5 - > static.c

Re: Bug#901255: netcfg-static: Unable to configure fe80::1 as a gateway

2018-06-11 Thread Igor Scheller
Hi, I created a merge request [1] for that, Improvements welcome ;) Greets, Igor Scheller [1] https://salsa.debian.org/installer-team/netcfg/merge_requests/3/diffs On 10.06.2018 22:33, Philipp Kern wrote: > On 6/10/18 7:25 PM, Samuel Thibault wrote: >> Igor Scheller, le dim. 10 juin 2018