Skip to content

Conversation

@rthakur33
Copy link
Contributor

In case of ipip6 tunnels, inherit the tos value in the ip6 header from the inner ip4 header as the default behaviour. Without this commit, the tos value in the ip6 header is hard coded to 0 which is wrong.

The ipip6 mode tunnels lack a tos uci option allowing the choice of either inheriting tos value or setting it as per uci config. I will push a change to address this separately, but, in the absense of such a config, the default behaviour should be inherit the tos value from the inner ip4 header and not to hard code it to 0. This commit fixes that.

In case of ipip6 tunnels, inherit the tos value in the ip6 header
from the inner ip4 header as the default behaviour. Without
this commit, the tos value in the ip6 header is hard coded to 0 which
is wrong.

The ipip6 mode tunnels lack a tos uci option allowing the choice of
either inheriting tos value or setting it as per uci config. I will
push a change to address this separately, but, in the absense of such
a config, the default behaviour should be inherit the tos value from
the inner ip4 header and not to hard code it to 0. This commit fixes
that.

Signed-off-by: Rahul Thakur <rahul.thakur@iopsys.eu>
@rthakur33 rthakur33 requested a review from jow- December 2, 2024 07:31
@Rondom
Copy link

Rondom commented Sep 3, 2025

@jow- Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants