Indeed, ping does work if I ping the "fe80::1%lo1" on FIB 1, which is
correct.
My script was getting the address from the routing table output (F1)
which is returning "%lo0" instead of the correct loopback number (lo6 in
my case) and as a result it was failing.
The routing table should retur
> On Jul 19, 2024, at 12:11 AM, Santiago Martinez wrote:
>
> Interesting, I'm running 14.1p2.
>
>
Yes, I'm running exactly the same version with you.
> how does your routing table looks for fib1 ?
>
>
```
# netstat -6rnF 1
Routing tables (fib: 1)
Internet6:
Destination
Interesting, I'm running 14.1p2.
how does your routing table looks for fib1 ?
Santi
On 7/18/24 18:09, Zhenlei Huang wrote:
On Jul 13, 2024, at 1:06 AM, Santiago Martinez
wrote:
Hi Everyone.
While adding -F ( fib as used in netstat ) to ping and ping6 I have
found something that from m
> On Jul 13, 2024, at 1:06 AM, Santiago Martinez wrote:
>
> Hi Everyone.
>
> While adding -F ( fib as used in netstat ) to ping and ping6 I have found
> something that from my understanding is not correct.
> Please can you advise?
> I have the following setup :
>
> -- two fibs (0 and 1)
> -
Hi everyone,
Did anyone had the chance to take a look?
For me it’s a bug but before filling the PR want to know what’s your view or if
it’s a limitation or bug by design.
Br
Santi
> On 12 Jul 2024, at 19:06, Santiago Martinez wrote:
>
>
> Hi Everyone.
>
> While adding -F ( fib as used in ne
Hi Everyone.
While adding -F ( fib as used in netstat ) to ping and ping6 I have
found something that from my understanding is not correct.
Please can you advise?
I have the following setup :
-- two fibs (0 and 1)
-- two loop-backs (lo0 and lo1).
-- Lo1 has been assigned to fib1
--net.add_ad
