Bird 2.0.7 Route Server IPv4 and IPv6 Session and Route issue. #94

Open
opened 2022-06-13 18:45:20 +08:00 by securebitag · 3 comments
securebitag commented 2022-06-13 18:45:20 +08:00 (Migrated from github.com)

Hi

We are using alice-lg and birdwatcher for our Bird Route Servers since years. Since we updated our Route Servers to Bird Version 2, all of our Route Server Sections (IPv4 and IPv6) show all Sessions (IPv4 and IPv6).

Example:
https://as58057.net/routeservers/sbix-rs1-v4
This is SBIX RS1 (IPv4) and should show only all IPv4 Sessions and Routes. IPv4 work as expected, but it also show all IPv6 Sessions and 0 Routes for all IPv6 Sessions.
The question is now, how to solve this issue?

We saw that there is a new Birdwatcher Version and we deployed the new version. But still got the same result.
When accessing the birdwatcher on /protocols/bgp we saw that there are also the tables visible and changed our alice config from single-table to
type = multi_table main_table = master4 peer_table_prefix = T pipe_protocol_prefix = M
But still see ipv4 and ipv6 sessions on all route servers.

Does anyone have fixed this issue?
Or know what else we can try here?

Hi We are using alice-lg and birdwatcher for our Bird Route Servers since years. Since we updated our Route Servers to Bird Version 2, all of our Route Server Sections (IPv4 and IPv6) show all Sessions (IPv4 and IPv6). Example: https://as58057.net/routeservers/sbix-rs1-v4 This is SBIX RS1 (IPv4) and should show only all IPv4 Sessions and Routes. IPv4 work as expected, but it also show all IPv6 Sessions and 0 Routes for all IPv6 Sessions. The question is now, how to solve this issue? We saw that there is a new Birdwatcher Version and we deployed the new version. But still got the same result. When accessing the birdwatcher on /protocols/bgp we saw that there are also the tables visible and changed our alice config from single-table to ` type = multi_table main_table = master4 peer_table_prefix = T pipe_protocol_prefix = M ` But still see ipv4 and ipv6 sessions on all route servers. Does anyone have fixed this issue? Or know what else we can try here?
bluikko commented 2022-10-17 15:47:42 +08:00 (Migrated from github.com)

Sounds like the same issue I have mentioned in the last point of #71. There is a reply in https://github.com/alice-lg/alice-lg/issues/71#issuecomment-874219176 but it did not lead anywhere.

Sounds like the same issue I have mentioned in the last point of #71. There is a reply in https://github.com/alice-lg/alice-lg/issues/71#issuecomment-874219176 but it did not lead anywhere.
securebitag commented 2022-10-17 16:32:12 +08:00 (Migrated from github.com)

Hi

Thanks for sharing this. Lets hope, somebody can help us to fix this.

Hi Thanks for sharing this. Lets hope, somebody can help us to fix this.
moshivji commented 2023-10-26 20:04:15 +08:00 (Migrated from github.com)

Hi
Did you fix this issue as I seem to the same problem ?

Hi Did you fix this issue as I seem to the same problem ?
Sign in to join this conversation.
No description provided.