Changing default ip rule priority for main table
Clash Royale CLAN TAG#URR8PPP
Please, suggest how to add ip rule right after main rule.
I have the following configuration and it needed to be restored on boot.
32766: from all lookup main
32766: from all lookup upstream01
32766: from all lookup upstream02
32767: from all lookup default
The challenge is to add rules for tables upstream 01 & 02 in correct order right after main. The priority for main & default don't have any gap to inject rules between them. I can only use the same priority of rule to main table to add it as I show above.
So, I see multiple options:
a. change default priority rule for main table to make a gap between rules to have ability define a priority in required order. But I don't know how to do this.
b. Found a way how to inject rules between "main" and "upstream01".
linux networking ip route iproute
add a comment |
Please, suggest how to add ip rule right after main rule.
I have the following configuration and it needed to be restored on boot.
32766: from all lookup main
32766: from all lookup upstream01
32766: from all lookup upstream02
32767: from all lookup default
The challenge is to add rules for tables upstream 01 & 02 in correct order right after main. The priority for main & default don't have any gap to inject rules between them. I can only use the same priority of rule to main table to add it as I show above.
So, I see multiple options:
a. change default priority rule for main table to make a gap between rules to have ability define a priority in required order. But I don't know how to do this.
b. Found a way how to inject rules between "main" and "upstream01".
linux networking ip route iproute
add a comment |
Please, suggest how to add ip rule right after main rule.
I have the following configuration and it needed to be restored on boot.
32766: from all lookup main
32766: from all lookup upstream01
32766: from all lookup upstream02
32767: from all lookup default
The challenge is to add rules for tables upstream 01 & 02 in correct order right after main. The priority for main & default don't have any gap to inject rules between them. I can only use the same priority of rule to main table to add it as I show above.
So, I see multiple options:
a. change default priority rule for main table to make a gap between rules to have ability define a priority in required order. But I don't know how to do this.
b. Found a way how to inject rules between "main" and "upstream01".
linux networking ip route iproute
Please, suggest how to add ip rule right after main rule.
I have the following configuration and it needed to be restored on boot.
32766: from all lookup main
32766: from all lookup upstream01
32766: from all lookup upstream02
32767: from all lookup default
The challenge is to add rules for tables upstream 01 & 02 in correct order right after main. The priority for main & default don't have any gap to inject rules between them. I can only use the same priority of rule to main table to add it as I show above.
So, I see multiple options:
a. change default priority rule for main table to make a gap between rules to have ability define a priority in required order. But I don't know how to do this.
b. Found a way how to inject rules between "main" and "upstream01".
linux networking ip route iproute
linux networking ip route iproute
edited Dec 17 at 15:39
red0ct
1279
1279
asked Feb 15 at 8:50
Dmitriy Sosunov
1033
1033
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The pref
keyword allows to override the priority.
ip rule add pref 32000 from all lookup main
ip rule del pref 32766 from all lookup main
ip rule add pref 32010 from all lookup upstream01
ip rule add pref 32020 from all lookup upstream02
add a comment |
You can delete the existing "default" rule and replace it with rules that suit your situation:
# delete the existing default rule
ip rule del from all lookup default priority 32767
# add your custom rules
ip rule add from all lookup upstream01 priority 32767
ip rule add from all lookup upstream02 priority 32768
# replace the "default" rule
ip rule add from all lookup default priority 32769
The result should look like this:
0: from all lookup local
32766: from all lookup main
32767: from all lookup upstream01
32768: from all lookup upstream02
32769: from all lookup default
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424314%2fchanging-default-ip-rule-priority-for-main-table%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The pref
keyword allows to override the priority.
ip rule add pref 32000 from all lookup main
ip rule del pref 32766 from all lookup main
ip rule add pref 32010 from all lookup upstream01
ip rule add pref 32020 from all lookup upstream02
add a comment |
The pref
keyword allows to override the priority.
ip rule add pref 32000 from all lookup main
ip rule del pref 32766 from all lookup main
ip rule add pref 32010 from all lookup upstream01
ip rule add pref 32020 from all lookup upstream02
add a comment |
The pref
keyword allows to override the priority.
ip rule add pref 32000 from all lookup main
ip rule del pref 32766 from all lookup main
ip rule add pref 32010 from all lookup upstream01
ip rule add pref 32020 from all lookup upstream02
The pref
keyword allows to override the priority.
ip rule add pref 32000 from all lookup main
ip rule del pref 32766 from all lookup main
ip rule add pref 32010 from all lookup upstream01
ip rule add pref 32020 from all lookup upstream02
answered Mar 6 at 0:55
A.B
3,9971724
3,9971724
add a comment |
add a comment |
You can delete the existing "default" rule and replace it with rules that suit your situation:
# delete the existing default rule
ip rule del from all lookup default priority 32767
# add your custom rules
ip rule add from all lookup upstream01 priority 32767
ip rule add from all lookup upstream02 priority 32768
# replace the "default" rule
ip rule add from all lookup default priority 32769
The result should look like this:
0: from all lookup local
32766: from all lookup main
32767: from all lookup upstream01
32768: from all lookup upstream02
32769: from all lookup default
add a comment |
You can delete the existing "default" rule and replace it with rules that suit your situation:
# delete the existing default rule
ip rule del from all lookup default priority 32767
# add your custom rules
ip rule add from all lookup upstream01 priority 32767
ip rule add from all lookup upstream02 priority 32768
# replace the "default" rule
ip rule add from all lookup default priority 32769
The result should look like this:
0: from all lookup local
32766: from all lookup main
32767: from all lookup upstream01
32768: from all lookup upstream02
32769: from all lookup default
add a comment |
You can delete the existing "default" rule and replace it with rules that suit your situation:
# delete the existing default rule
ip rule del from all lookup default priority 32767
# add your custom rules
ip rule add from all lookup upstream01 priority 32767
ip rule add from all lookup upstream02 priority 32768
# replace the "default" rule
ip rule add from all lookup default priority 32769
The result should look like this:
0: from all lookup local
32766: from all lookup main
32767: from all lookup upstream01
32768: from all lookup upstream02
32769: from all lookup default
You can delete the existing "default" rule and replace it with rules that suit your situation:
# delete the existing default rule
ip rule del from all lookup default priority 32767
# add your custom rules
ip rule add from all lookup upstream01 priority 32767
ip rule add from all lookup upstream02 priority 32768
# replace the "default" rule
ip rule add from all lookup default priority 32769
The result should look like this:
0: from all lookup local
32766: from all lookup main
32767: from all lookup upstream01
32768: from all lookup upstream02
32769: from all lookup default
answered May 6 at 2:59
PolicyRouteGuy
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424314%2fchanging-default-ip-rule-priority-for-main-table%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown