I've figured out the problem. I had `next hop self` in the configuration of
the ipv6 side of the session. Setting that equal to ipv4 address resolved
things. For posterity in case anyone else runs into this in the future,
here is my BIRD configuration (be sure to replace 00 with your ASN):
```
Hi Brooks,
We can certainly take this off list. The next step is to 100% confirm
that the IPv6 prefixes are landing onto pmacct. The fact a BGP dump does
not reveal IPv6 prefixes means this is not a mapping issue but either a
decoding one (super weird plus you would find tracks of this in the log
Thank you for the suggestion, Paolo. I went ahead and dumped the BGP table
but don't see any IPv6 routes in there (though it's quite large as it has
the V4 table from an IX). I can share this off list if it would be helpful.
To recap, my `/etc/pmacct/peering_agent.map` file is:
```
bgp_ip=1.1.1.1
Could we repeat the same troubleshooting as for the other issue: let's
enable dumping of BGP data to a file just to make sure data is making it
over. Even just to check the route is among those 74479 of 132180 routes
exported.
Paolo
On Sun, Oct 13, 2019 at 07:19:09PM -0400, Brooks Swinnerton wr
Hmph, no dice. It looks like BIRD is exporting IPv6 routes:
```
bird> show route export pmacctd46 count
173376 of 337458 routes for 173376 networks in table master4
74479 of 132180 routes for 74479 networks in table master6
Total: 247855 of 469638 routes for 247855 networks in 2 tables
```
But th
Super cool. It would remain the one-liner you have got at the moment:
bgp_ip=1.1.1.1 ip=0.0.0.0/0
Keep me posted.
Paolo
On Sun, Oct 13, 2019 at 04:21:21PM -0400, Brooks Swinnerton wrote:
> I’m actually already doing option 1 : ), what would the map look like for
> that?
>
> On Sun, Oct 13
I’m actually already doing option 1 : ), what would the map look like for
that?
On Sun, Oct 13, 2019 at 3:47 PM Paolo Lucente wrote:
>
> Hi Brooks,
>
> You are in an unsupported use-case, ie. same BGP Agent ID maped onto two
> different entries. You can get out of it in three different ways: 1)
Hi Brooks,
You are in an unsupported use-case, ie. same BGP Agent ID maped onto two
different entries. You can get out of it in three different ways: 1) my
top recommendation: travel both addrress families as part of the same BGP
session; 2) use two different BGP Agent ID for ipv4 and for ipv6;
Hello again!
I'm using pmacct with Kafka to stream flows. This is paired with the BGP
functionality to add the `src_as` and `dst_as`. This all works great for
IPv4, but I'm struggling to figure out how to do this for IPv6 as well.
Here is the current configuration:
```
!
! pmacctd configuration
