Skip to content

Conversation

@taitov
Copy link

@taitov taitov commented Feb 10, 2025

Example:

$ gobgp neighbor
Peer          Group     AS      Up/Down State       |#Received  Accepted
127.0.0.1 reflector 123456 16d 11:56:29 Establ      |   195075    195075
127.0.0.2 reflector 123456 16d 11:55:46 Establ      |   195075    195075
127.0.0.3 reflector 123456 16d 11:56:04 Establ      |   195075    195075
127.0.3.1    group2 123456 16d 11:53:09 Establ      |     5166      5166

@fujita
Copy link
Member

fujita commented Feb 24, 2025

How about the output of peers not in a peer group?

@taitov
Copy link
Author

taitov commented May 19, 2025

How about the output of peers not in a peer group?

$ ./gobgp neig
Peer           Group     AS      Up/Down State       |#Received  Accepted
127.0.2.1     group1  12345 18d 23:31:55 Establ      |       66        66
127.0.3.1     group2  12345 18d 23:31:53 Establ      |        1         1
127.0.0.1            212345        never Active      |        0         0
127.0.0.2  reflector 212345        never Active      |        0         0
127.0.0.3  reflector 212345        never Active      |        0         0

and without any groups:

$ ./gobgp neig
Peer      Group     AS Up/Down State       |#Received  Accepted
127.0.0.1       212345   never Active      |        0         0
127.0.0.2       212345   never Active      |        0         0
127.0.0.3       212345   never Active      |        0         0

@fujita
Copy link
Member

fujita commented May 20, 2025

Assuming that PeerGroup is often unused, the output doesn’t look good. How about adding an option to enable showing this? If other BGP CLIs (like Cisco, Juniper, etc) works in this way by default, it should be ok though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants