Handle only one route unlike MOD_PATHS API. When the API returns an
uuid when a route is created. The uuid can be used to remove the route
later.
Signed-off-by: FUJITA Tomonori <[email protected]>
Session State Uptime #IPv4/IPv6 records
210.173.170.254:323 Up 00:01:39 17112/2517
141.22.28.222:8282 Up 00:01:39 17411/2604
Signed-off-by: FUJITA Tomonori <[email protected]>
gobgp rpki server <ip address> reset|softreset|enable
reset: close a tcp conneciton and retry to connect and send ResetQuery
softreset: send ResetQuery
enable: send SerialQuery
Signed-off-by: FUJITA Tomonori <[email protected]>
This fixes softresetout to send withdrawn updates for only routes in
adj-out.
Currently, softreset sends withdrawn updates for ALL routes rejected
by export policy. The problem is, even if export policy is configured
to rejecte any routes, softreset sends withdrawn updates.
Signed-off-by: FUJITA Tomonori <[email protected]>
Gobpg does not set AfiSafi if NeighborConfig is configured via gRPC, this issue causes error when Gobgp receives route from the Peer.
log of following when peer was down
```
DEBU[0009] received Key=192.168.100.2 Topic=Peer data=&{Header:{Marker:[] Len:19 Type:4} Body:0xe17ff0}
WARN[0010] malformed BGP update message Key=192.168.100.2 Topic=Peer error=Address-family rf 65537 not avalible for session
WARN[0010] sent notification Data=&{Header:{Marker:[] Len:21 Type:3} Body:0xc8200117a0} Key=192.168.100.2 State=BGP_FSM_ESTABLISHED Topic=Peer
INFO[0010] Peer Down Key=192.168.100.2 Reason=Peer closed the session State=BGP_FSM_ESTABLISHED Topic=Peer
DEBU[0010] state changed Key=192.168.100.2 Topic=Peer new=BGP_FSM_IDLE old=BGP_FSM_ESTABLISHED
```
Needs to use ID() for path's Filter and Filtered methods instead of
TableID(). We don't hit any bugs because:
- With a RS client, both methods returns the same.
- No IN POLICY support for non RS clients
Signed-off-by: FUJITA Tomonori <[email protected]>
$ gobgp global rib
Network Next Hop AS_PATH Age Attrs
*> 10.0.0.0/24 0.0.0.0 00:00:01 [{Origin: ?}]
$ gobgp global rib 10.0.0.0/20
Network not in table
$ gobgp global rib 10.0.0.0/20 longer-prefix
Network Next Hop AS_PATH Age Attrs
*> 10.0.0.0/24 0.0.0.0 00:00:01 [{Origin: ?}]
Signed-off-by: ISHIDA Wataru <[email protected]>
With this fix, the RPC API works like the following:
$ gobgp global rib
Network Next Hop AS_PATH Age Attrs
*> 210.173.160.0/19 210.173.172.65 65001 00:00:41 [{Origin: i}]
$ gobgp global rib 210.173.176.1
Network Next Hop AS_PATH Age Attrs
*> 210.173.160.0/19 210.173.172.65 65001 00:01:17 [{Origin: i}]
Signed-off-by: FUJITA Tomonori <[email protected]>
bgpd parse on-wire original update data to construct BGPMessage object
and serialize it. Sometimes the both data is not idential. For
example, the original data sets the extended length for attribute even
if the length is less than 256.
This commit fixes the above issue.
Signed-off-by: FUJITA Tomonori <[email protected]>
bgpd parse on-wire original update data to construct BGPMessage object
and serialize it. Sometimes the both data is not idential. For
example, the original data sets the extended length for attribute even
if the length is less than 256.
This commit fixes the above issue.
Signed-off-by: FUJITA Tomonori <[email protected]>
$ gobgp mrt update reset
create a new file or reopen the existing file and continue to write
update messages to it.
$ gobgp mrt update <filename>
rename the current logging file to <filename> and truncate the logging
file and continue to write update messages to it.
Signed-off-by: FUJITA Tomonori <[email protected]>
ISHIDA Wataru
FUJITA Tomonori
Naoto Hanaue