Nell Jerram

Here is a review of our current BIRD code changes, and the filter config that we use in conjunction with those: ``` +--------+ [1] [2] +---------+ [4] +----------+ [5] |...

(In addition to the points above where code is actually doing things, there are these infrastructure changes, between upstream and our fork, to facilitate the above: ``` - filter.c: Add...

Other useful input is from the PR at https://github.com/projectcalico/bird/pull/21. The contributor was proposing to update the iface for a tunnel route in the BIRD routing table, instead of only when...

Putting all of that together, it now seems to me that - maybe - - we don’t need the orig_gw field, because the same information is available as the BA_NEXT_HOP...

The first step of the above plan - removing the orig_gw field and using BA_NEXT_HOP instead - has been done by https://github.com/projectcalico/bird/pull/75 and https://github.com/projectcalico/node/pull/380. Tigera themselves have no current schedule...

Thanks @rcarpa . It would take a bit of work for us to update from our current code based on 1.6.8, but we certainly might do that in future, and...

@kavana-14 https://github.com/projectcalico/bird.git is currently still based on BIRD v1.6.8, and the BIRD config format changed between 1.6.x and 2.x. So that explains your observations. I'm not sure it was a...

In current Calico the v4 and v6 BIRD processing are independent of each other. - ipv4 processing is done by a `bird` process, with config that should refer only to...

Great. So is there a remaining problem at the moment?

Yes, as the error says, Calico BIRD doesn't support forwarding to an IPv4 prefix via an IPv6 gateway.