Bug 2218491 - [DDF] The route rule here looks confused. The traffice sourced from IPIP tunnel and destined to Network B
Summary: [DDF] The route rule here looks confused. The traffice sourced from IPIP tunn...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Documentation
Version: 8.0
Hardware: All
OS: All
high
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-29 10:59 UTC by Direct Docs Feedback
Modified: 2023-06-29 13:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-29 13:05:40 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-161166 0 None None None 2023-06-29 11:05:21 UTC

Description Direct Docs Feedback 2023-06-29 10:59:14 UTC
The route rule here looks confused. The traffice sourced from IPIP tunnel and destined to Network B (172.16.0.0/24) should be route via the gateway 172.16.0.1 on interface 'enp1s0', instead of tunnel local IP (10.0.1.2).

Reported by: jet.jiang

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-ip-tunnels_configuring-and-managing-networking#annotations:8fa375ba-1e38-4219-b580-a0cd9179c1aa

Comment 3 Jiri Benc 2023-06-29 12:57:23 UTC
(In reply to Direct Docs Feedback from comment #0)
> The route rule here looks confused. The traffice sourced from IPIP tunnel
> and destined to Network B (172.16.0.0/24) should be route via the gateway
> 172.16.0.1 on interface 'enp1s0', instead of tunnel local IP (10.0.1.2).

It's important to realize that the rule in question is configured on Router A (scroll up just below the "Procedure" header to see that), not on Router B. There are words "to the tunnel IP on router B" just above the rule, which I guess confused you. But they refer to where the rule is going to send the packets; they do not refer to where the rule is configured.

On Router B, we indeed need a rule sending 172.16.0.0/24 to enp1s0 (though not via 172.16.0.1, since the network is local, but that's not that important). However, that rule does not have to configured manually, since it is implicit.


Note You need to log in before you can comment on or make changes to this bug.