How do I force ssh to use a second interface with higher metric?How to force ssh client to use only password...

A question regarding using the definite article

"ne paelici suspectaretur" (Tacitus)

Examples of non trivial equivalence relations , I mean equivalence relations without the expression " same ... as" in their definition?

Was it really necessary for the Lunar Module to have 2 stages?

What does "rf" mean in "rfkill"?

How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?

Modify locally tikzset

Is GOCE a satellite or aircraft?

Pulling the rope with one hand is as heavy as with two hands?

Does jamais mean always or never in this context?

What's the polite way to say "I need to urinate"?

Phrase for the opposite of "foolproof"

Can fracking help reduce CO2?

How to figure out whether the data is sample data or population data apart from the client's information?

How to back up a running remote server?

Minimum value of 4 digit number divided by sum of its digits

In gnome-terminal only 2 out of 3 zoom keys work

Why do TACANs not have a symbol for compulsory reporting?

Stark VS Thanos

You look catfish vs You look like a catfish

What is the range of this combined function?

Please, smoke with good manners

Pressure to defend the relevance of one's area of mathematics

Why do computer-science majors learn calculus?



How do I force ssh to use a second interface with higher metric?


How to force ssh client to use only password auth?Use ssh with a specific network interfaceHow to use ifconfig to show active interface onlyForce ssh to always use SSH_ASKPASSAWS VPC NAT | ssh_exchange_identification: read: Connection reset by peerUse a bond interface like a bridgeHow to use sshpass to supply a password on the second ssh hopHow to create/setup vpn using only SSH?Add a SSH key for second useriptables - 2 Internetprovider - routing






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







9















I have a Crunchbang VM with two interfaces, eth0 and eth1, each
of which connects to an OpenWRT VM (eth0 being 10.232.64.20 and
eth1 being 10.232.65.20). I'm using Network Manager and DHCP. My overall goal is having multiple ssh connections, and bonding them with ifenslave.



By default, eth1 (for some reason) is the default gateway:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


I added a route for eth0:



user@crunchbang:~$ sudo ip route add default via 10.232.64.1 dev eth0  proto static metric 1


Then I have two routes:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
default via 10.232.64.1 dev eth0 proto static metric 1
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


However, ssh only gets out via eth1:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


After changing the eth0 metric I have:



user@crunchbang:~$ ip ro
default via 10.232.64.1 dev eth0 proto static metric 1
default via 10.232.65.1 dev eth1 proto static metric 2
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


And now ssh only gets out via eth0:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out


How do I force ssh to use an interface with a higher metric?



Edit



I have implemented and tested the configuration in the 4.2. Routing for multiple uplinks/providers section of the Linux Advanced Routing & Traffic Control HOWTO. Given that the configuration is simple, and that I didn't encounter errors, I'll just show code and results, with minimal explanation.



root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20 table T0
root@crunchbang:~# ip route add default via 10.232.64.1 table T0
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20 table T1
root@crunchbang:~# ip route add default via 10.232.65.1 table T1
root@crunchbang:~# ip route flush table main
root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20
root@crunchbang:~# ip rule add from 10.232.64.20 table T0
root@crunchbang:~# ip rule add from 10.232.65.20 table T1
root@crunchbang:~# ip route add default scope global nexthop via 10.232.64.1 dev eth0 weight 1 nexthop via 10.232.65.1 dev eth1 weight 1


Here are the routing tables generated:



root@crunchbang:~# ip route show table T0
default via 10.232.64.1 dev eth0
10.232.64.0/24 dev eth0 scope link src 10.232.64.20

root@crunchbang:~# ip route show table T1
default via 10.232.65.1 dev eth1
10.232.65.0/24 dev eth1 scope link src 10.232.65.20

root@crunchbang:~# ip ro
default
nexthop via 10.232.64.1 dev eth0 weight 1
nexthop via 10.232.65.1 dev eth1 weight 1
10.232.64.0/24 dev eth0 scope link src 10.232.64.20
10.232.65.0/24 dev eth1 scope link src 10.232.65.20


With that configuration, ssh connects via both interfaces:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


However, it does appear that I need to lose Network Manager. If anyone could explain why that's a bad idea, or warn of pitfalls, I would appreciate it.



Edit2



Removing Network Manager went well. I have just one last question. What is the current standard way to load the configuration at boot?










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

    – mirimir
    Oct 14 '13 at 4:34











  • It worked, so I'll update my question.

    – mirimir
    Oct 14 '13 at 6:52













  • I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

    – mirimir
    Oct 15 '13 at 2:56


















9















I have a Crunchbang VM with two interfaces, eth0 and eth1, each
of which connects to an OpenWRT VM (eth0 being 10.232.64.20 and
eth1 being 10.232.65.20). I'm using Network Manager and DHCP. My overall goal is having multiple ssh connections, and bonding them with ifenslave.



By default, eth1 (for some reason) is the default gateway:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


I added a route for eth0:



user@crunchbang:~$ sudo ip route add default via 10.232.64.1 dev eth0  proto static metric 1


Then I have two routes:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
default via 10.232.64.1 dev eth0 proto static metric 1
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


However, ssh only gets out via eth1:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


After changing the eth0 metric I have:



user@crunchbang:~$ ip ro
default via 10.232.64.1 dev eth0 proto static metric 1
default via 10.232.65.1 dev eth1 proto static metric 2
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


And now ssh only gets out via eth0:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out


How do I force ssh to use an interface with a higher metric?



Edit



I have implemented and tested the configuration in the 4.2. Routing for multiple uplinks/providers section of the Linux Advanced Routing & Traffic Control HOWTO. Given that the configuration is simple, and that I didn't encounter errors, I'll just show code and results, with minimal explanation.



root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20 table T0
root@crunchbang:~# ip route add default via 10.232.64.1 table T0
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20 table T1
root@crunchbang:~# ip route add default via 10.232.65.1 table T1
root@crunchbang:~# ip route flush table main
root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20
root@crunchbang:~# ip rule add from 10.232.64.20 table T0
root@crunchbang:~# ip rule add from 10.232.65.20 table T1
root@crunchbang:~# ip route add default scope global nexthop via 10.232.64.1 dev eth0 weight 1 nexthop via 10.232.65.1 dev eth1 weight 1


Here are the routing tables generated:



root@crunchbang:~# ip route show table T0
default via 10.232.64.1 dev eth0
10.232.64.0/24 dev eth0 scope link src 10.232.64.20

root@crunchbang:~# ip route show table T1
default via 10.232.65.1 dev eth1
10.232.65.0/24 dev eth1 scope link src 10.232.65.20

root@crunchbang:~# ip ro
default
nexthop via 10.232.64.1 dev eth0 weight 1
nexthop via 10.232.65.1 dev eth1 weight 1
10.232.64.0/24 dev eth0 scope link src 10.232.64.20
10.232.65.0/24 dev eth1 scope link src 10.232.65.20


With that configuration, ssh connects via both interfaces:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


However, it does appear that I need to lose Network Manager. If anyone could explain why that's a bad idea, or warn of pitfalls, I would appreciate it.



Edit2



Removing Network Manager went well. I have just one last question. What is the current standard way to load the configuration at boot?










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

    – mirimir
    Oct 14 '13 at 4:34











  • It worked, so I'll update my question.

    – mirimir
    Oct 14 '13 at 6:52













  • I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

    – mirimir
    Oct 15 '13 at 2:56














9












9








9


1






I have a Crunchbang VM with two interfaces, eth0 and eth1, each
of which connects to an OpenWRT VM (eth0 being 10.232.64.20 and
eth1 being 10.232.65.20). I'm using Network Manager and DHCP. My overall goal is having multiple ssh connections, and bonding them with ifenslave.



By default, eth1 (for some reason) is the default gateway:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


I added a route for eth0:



user@crunchbang:~$ sudo ip route add default via 10.232.64.1 dev eth0  proto static metric 1


Then I have two routes:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
default via 10.232.64.1 dev eth0 proto static metric 1
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


However, ssh only gets out via eth1:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


After changing the eth0 metric I have:



user@crunchbang:~$ ip ro
default via 10.232.64.1 dev eth0 proto static metric 1
default via 10.232.65.1 dev eth1 proto static metric 2
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


And now ssh only gets out via eth0:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out


How do I force ssh to use an interface with a higher metric?



Edit



I have implemented and tested the configuration in the 4.2. Routing for multiple uplinks/providers section of the Linux Advanced Routing & Traffic Control HOWTO. Given that the configuration is simple, and that I didn't encounter errors, I'll just show code and results, with minimal explanation.



root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20 table T0
root@crunchbang:~# ip route add default via 10.232.64.1 table T0
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20 table T1
root@crunchbang:~# ip route add default via 10.232.65.1 table T1
root@crunchbang:~# ip route flush table main
root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20
root@crunchbang:~# ip rule add from 10.232.64.20 table T0
root@crunchbang:~# ip rule add from 10.232.65.20 table T1
root@crunchbang:~# ip route add default scope global nexthop via 10.232.64.1 dev eth0 weight 1 nexthop via 10.232.65.1 dev eth1 weight 1


Here are the routing tables generated:



root@crunchbang:~# ip route show table T0
default via 10.232.64.1 dev eth0
10.232.64.0/24 dev eth0 scope link src 10.232.64.20

root@crunchbang:~# ip route show table T1
default via 10.232.65.1 dev eth1
10.232.65.0/24 dev eth1 scope link src 10.232.65.20

root@crunchbang:~# ip ro
default
nexthop via 10.232.64.1 dev eth0 weight 1
nexthop via 10.232.65.1 dev eth1 weight 1
10.232.64.0/24 dev eth0 scope link src 10.232.64.20
10.232.65.0/24 dev eth1 scope link src 10.232.65.20


With that configuration, ssh connects via both interfaces:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


However, it does appear that I need to lose Network Manager. If anyone could explain why that's a bad idea, or warn of pitfalls, I would appreciate it.



Edit2



Removing Network Manager went well. I have just one last question. What is the current standard way to load the configuration at boot?










share|improve this question
















I have a Crunchbang VM with two interfaces, eth0 and eth1, each
of which connects to an OpenWRT VM (eth0 being 10.232.64.20 and
eth1 being 10.232.65.20). I'm using Network Manager and DHCP. My overall goal is having multiple ssh connections, and bonding them with ifenslave.



By default, eth1 (for some reason) is the default gateway:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


I added a route for eth0:



user@crunchbang:~$ sudo ip route add default via 10.232.64.1 dev eth0  proto static metric 1


Then I have two routes:



user@crunchbang:~$ ip ro
default via 10.232.65.1 dev eth1 proto static
default via 10.232.64.1 dev eth0 proto static metric 1
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


However, ssh only gets out via eth1:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


After changing the eth0 metric I have:



user@crunchbang:~$ ip ro
default via 10.232.64.1 dev eth0 proto static metric 1
default via 10.232.65.1 dev eth1 proto static metric 2
10.232.64.0/24 dev eth0 proto kernel scope link src 10.232.64.20
10.232.65.0/24 dev eth1 proto kernel scope link src 10.232.65.20


And now ssh only gets out via eth0:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
ssh: connect to host 1.2.3.4 port 22: Connection timed out


How do I force ssh to use an interface with a higher metric?



Edit



I have implemented and tested the configuration in the 4.2. Routing for multiple uplinks/providers section of the Linux Advanced Routing & Traffic Control HOWTO. Given that the configuration is simple, and that I didn't encounter errors, I'll just show code and results, with minimal explanation.



root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20 table T0
root@crunchbang:~# ip route add default via 10.232.64.1 table T0
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20 table T1
root@crunchbang:~# ip route add default via 10.232.65.1 table T1
root@crunchbang:~# ip route flush table main
root@crunchbang:~# ip route add 10.232.64.0/24 dev eth0 src 10.232.64.20
root@crunchbang:~# ip route add 10.232.65.0/24 dev eth1 src 10.232.65.20
root@crunchbang:~# ip rule add from 10.232.64.20 table T0
root@crunchbang:~# ip rule add from 10.232.65.20 table T1
root@crunchbang:~# ip route add default scope global nexthop via 10.232.64.1 dev eth0 weight 1 nexthop via 10.232.65.1 dev eth1 weight 1


Here are the routing tables generated:



root@crunchbang:~# ip route show table T0
default via 10.232.64.1 dev eth0
10.232.64.0/24 dev eth0 scope link src 10.232.64.20

root@crunchbang:~# ip route show table T1
default via 10.232.65.1 dev eth1
10.232.65.0/24 dev eth1 scope link src 10.232.65.20

root@crunchbang:~# ip ro
default
nexthop via 10.232.64.1 dev eth0 weight 1
nexthop via 10.232.65.1 dev eth1 weight 1
10.232.64.0/24 dev eth0 scope link src 10.232.64.20
10.232.65.0/24 dev eth1 scope link src 10.232.65.20


With that configuration, ssh connects via both interfaces:



user@crunchbang:~$ ssh -b 10.232.64.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':

user@crunchbang:~$ ssh -b 10.232.65.20 user@1.2.3.4
Enter passphrase for key '/home/user/.ssh/id_rsa':


However, it does appear that I need to lose Network Manager. If anyone could explain why that's a bad idea, or warn of pitfalls, I would appreciate it.



Edit2



Removing Network Manager went well. I have just one last question. What is the current standard way to load the configuration at boot?







ssh crunchbang interface bonding






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 14 '13 at 9:50







mirimir

















asked Oct 14 '13 at 1:58









mirimirmirimir

2281413




2281413





bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

    – mirimir
    Oct 14 '13 at 4:34











  • It worked, so I'll update my question.

    – mirimir
    Oct 14 '13 at 6:52













  • I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

    – mirimir
    Oct 15 '13 at 2:56



















  • I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

    – mirimir
    Oct 14 '13 at 4:34











  • It worked, so I'll update my question.

    – mirimir
    Oct 14 '13 at 6:52













  • I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

    – mirimir
    Oct 15 '13 at 2:56

















I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

– mirimir
Oct 14 '13 at 4:34





I just discovered 4.2. Routing for multiple uplinks/providers. I'll update the question pending implementation.

– mirimir
Oct 14 '13 at 4:34













It worked, so I'll update my question.

– mirimir
Oct 14 '13 at 6:52







It worked, so I'll update my question.

– mirimir
Oct 14 '13 at 6:52















I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

– mirimir
Oct 15 '13 at 2:56





I don't get how to load the routing at boot, because that requires root rights. Doing it with a script works fine, but I'd rather be able to reboot without setup.

– mirimir
Oct 15 '13 at 2:56










1 Answer
1






active

oldest

votes


















0














First, your solution for the problem is good.
Second, it depends on the OS. Crunchbag is debian based so this solutions could do the job:



https://serverfault.com/questions/487939/permanently-adding-source-policy-routing-rules



On RHEL based systems there is also the possibility to add <ifname>-rule and <ifname>-route.






share|improve this answer
























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f95934%2fhow-do-i-force-ssh-to-use-a-second-interface-with-higher-metric%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    First, your solution for the problem is good.
    Second, it depends on the OS. Crunchbag is debian based so this solutions could do the job:



    https://serverfault.com/questions/487939/permanently-adding-source-policy-routing-rules



    On RHEL based systems there is also the possibility to add <ifname>-rule and <ifname>-route.






    share|improve this answer




























      0














      First, your solution for the problem is good.
      Second, it depends on the OS. Crunchbag is debian based so this solutions could do the job:



      https://serverfault.com/questions/487939/permanently-adding-source-policy-routing-rules



      On RHEL based systems there is also the possibility to add <ifname>-rule and <ifname>-route.






      share|improve this answer


























        0












        0








        0







        First, your solution for the problem is good.
        Second, it depends on the OS. Crunchbag is debian based so this solutions could do the job:



        https://serverfault.com/questions/487939/permanently-adding-source-policy-routing-rules



        On RHEL based systems there is also the possibility to add <ifname>-rule and <ifname>-route.






        share|improve this answer













        First, your solution for the problem is good.
        Second, it depends on the OS. Crunchbag is debian based so this solutions could do the job:



        https://serverfault.com/questions/487939/permanently-adding-source-policy-routing-rules



        On RHEL based systems there is also the possibility to add <ifname>-rule and <ifname>-route.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jul 13 '18 at 19:09









        harguthargut

        2738




        2738






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f95934%2fhow-do-i-force-ssh-to-use-a-second-interface-with-higher-metric%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...