Le 2017-10-13 21:30, Paolo Lucente a écrit :
> Hi Fabien,
>
> There was no progress on the OP (that is, choose an IPv4 and an IPv6
> address to listen to; but you can choose an IPv6 or an IPv6 address).
>
> Any chance you can make a tcpdump of the BGP session and send it over
> via unicast
Hi Fabien,
There was no progress on the OP (that is, choose an IPv4 and an IPv6
address to listen to; but you can choose an IPv6 or an IPv6 address).
Any chance you can make a tcpdump of the BGP session and send it over
via unicast email? I have the scenario working perfectly for me (that
is,
Hi List ;)
Paolo any news on this request ? Checking with IPv4/IPv6 AFI 1/2 over
IPv4 BGP session, but seems next hop are not well populated (almost ::
value)
I'm wondering if this a bug (git version for fwdstatus patch) or if it's
related to the fact we have AFI2/IPv6 over IPv4 BGP sessions.
Hi Fabien,
Yes, that is more clear, thanks for elaborating. In short, that is not
currently possible. But the dev of the feature does not appear to be a
biggie either, i've put it on my todo list. The only workaround that
comes to mind, i know i'm saying the obvious, is to pick a transport
Hi Paolo,
Le 2016-12-07 17:54, Paolo Lucente a écrit :
Hi Fabien,
One step back on your question: you refer to the flow records or to the
transport protocol here? You can travel v4 and v6 records within the
same, say, v4 NetFlow/IPFIX/sFlow transport. This is what all exporters
basically do;
Hi Fabien,
One step back on your question: you refer to the flow records or to the
transport protocol here? You can travel v4 and v6 records within the
same, say, v4 NetFlow/IPFIX/sFlow transport. This is what all exporters
basically do; are you working with an exporter that is behaving in a
Dear list,
Any help on how to configure sfacctd and nfacctd on dual stack ?
I mean having both IPv4 and IPv6 running on sfacctd, with collector
enabled on both protocols ?
I've seen the trick for bgp_daemon_ip, but don't know how to bind to
specific ip4 and ip6 on my server the sfacctd bgp
