| 2021-04-13 09:06:19 |
Rodolfo Alonso |
description |
The router namespace routes for other segment CIDRs, should have the "via" parameter to the gateway IP address.
The environment I'm using has HA routers; I didn't test yet with DVR or legacy routers.
For example, in my env [1]:
- Network: public
- Subnets:
(s1) aebc3fc1-d984-40aa-8405-db51df03f60d: 10.46.54.0/26, gwip: 10.46.54.62
(s2) 55a66c34-3643-49ba-ab8c-326ee76e5f35: 10.46.54.64/26, gwip: 10.46.54.126
- Router namespace:
[root@controller-0 ~]# ip netns exec $r ip r
default via 10.46.54.62 dev qg-7847fd00-72 proto 112
default via 10.46.54.62 dev qg-7847fd00-72 proto static
10.1.0.0/16 dev qr-d224ca69-77 proto kernel scope link src 10.1.0.1
10.46.54.0/26 dev qg-7847fd00-72 proto kernel scope link src 10.46.54.34
10.46.54.64/26 dev qg-7847fd00-72 proto 112 scope link
10.46.54.64/26 dev qg-7847fd00-72 proto static scope link
169.254.0.0/24 dev ha-91b6c056-57 proto kernel scope link src 169.254.0.233
169.254.192.0/18 dev ha-91b6c056-57 proto kernel scope link src 169.254.193.151
This router is attached to the segment of the subnet aebc3fc1-d984-40aa-8405-db51df03f60d (s1).
The route to 10.46.54.64/26 (the other subnet/segment this router is NOT attached to), should have the gateway IP address of the subnet that belongs to the segment the router is attached to; in this case, as commented, (s1).
[1]http://paste.openstack.org/show/804429/ |
The router namespace routes for other segment CIDRs, should have the "via" parameter to the gateway IP address.
The environment I'm using has HA routers; I didn't test yet with DVR or legacy routers.
For example, in my env [1]:
- Network: public
- Subnets:
(s1) aebc3fc1-d984-40aa-8405-db51df03f60d: 10.46.54.0/26, gwip: 10.46.54.62
(s2) 55a66c34-3643-49ba-ab8c-326ee76e5f35: 10.46.54.64/26, gwip: 10.46.54.126
- Router namespace:
[root@controller-0 ~]# ip netns exec $r ip r
default via 10.46.54.62 dev qg-7847fd00-72 proto 112
default via 10.46.54.62 dev qg-7847fd00-72 proto static
10.1.0.0/16 dev qr-d224ca69-77 proto kernel scope link src 10.1.0.1
10.46.54.0/26 dev qg-7847fd00-72 proto kernel scope link src 10.46.54.34
10.46.54.64/26 dev qg-7847fd00-72 proto 112 scope link
10.46.54.64/26 dev qg-7847fd00-72 proto static scope link
169.254.0.0/24 dev ha-91b6c056-57 proto kernel scope link src 169.254.0.233
169.254.192.0/18 dev ha-91b6c056-57 proto kernel scope link src 169.254.193.151
This router is attached to the segment of the subnet aebc3fc1-d984-40aa-8405-db51df03f60d (s1).
The route to 10.46.54.64/26 (the other subnet/segment this router is NOT attached to), should have the gateway IP address of the subnet that belongs to the segment the router is attached to; in this case, as commented, (s1).
[1]http://paste.openstack.org/show/804429/
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945061 |
|
