Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2218491

Summary:	[DDF] The route rule here looks confused. The traffice sourced from IPIP tunnel and destined to Network B
Product:	Red Hat Enterprise Linux 8	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Marc Muehlfeld <mmuehlfe>
Documentation sub component:	DDF	QA Contact:
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	unspecified
Priority:	high	CC:	jbenc, rhel-docs
Version:	8.0	Keywords:	Documentation
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-29 13:05:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.