Bug 1837966
| Summary: | RFE: Provide config option for route-table for dynamic ipv4 and ipv6 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Ales Musil <amusil> | ||||
| Component: | nmstate | Assignee: | Fernando F. Mancera <ferferna> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Mingyu Shi <mshi> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.1 | CC: | dholler, ferferna, fge, jiji, jishi, network-qe, till | ||||
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | 8.4 | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-05-18 15:16:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Hi Ales,
For defining route table in static route, you may use:
```yml
routes:
config:
- destination: 198.51.100.0/24
metric: 150
next-hop-address: 192.0.2.1
next-hop-interface: eth1
table-id: 254
```
The ipv4.route-table and ipv6.route-table is for routes learn from DHCP/Autconf.
Can you give me a use case why storing those dynamic routes in route table matters?
Hi Gris, the answer is simple, dynamic source routing. Now we have learn gateway from DHCP/Autoconf response and then configure it to routing table. With this we would require only to set the rules to use this table. As a bonus this approach does not require to check DHCP responses and search for gateways. Created attachment 1724697 [details]
verification
Verified with versions:
NetworkManager-1.28.0-0.1.el8.x86_64
nispor-0.6.1-2.el8.x86_64
nmstate-0.4.1-1.el8.noarch
DISTRO=RHEL-8.4.0-20201026.d.1
Linux hp-dl380pg8-12.rhts.eng.pek2.redhat.com 4.18.0-240.8.el8.x86_64 #1 SMP Sun Oct 25 16:56:23 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1748 |
Description of problem: NM provides connection option called ipv4.route-table and ipv6.route-table which decides in which table the route will configured. Provide config option in schema to configure this parameter. Something like: - name: veth1 type: ethernet state: up ipv4: dhcp: true enabled: true table-id: 500 ipv6: autoconf: true dhcp: true enabled: true table-id: 500