How do I force ssh to use a second interface with higher metric?
up vote
8
down vote
favorite
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
asked Oct 14 '13 at 1:58
mirimir
2231413
add a comment |
up vote
8
down vote
favorite
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
asked Oct 14 '13 at 1:58
mirimir
2231413
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
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
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
asked Oct 14 '13 at 1:58
mirimir
2231413
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
ssh crunchbang interface bonding
asked Oct 14 '13 at 1:58
mirimir
2231413
asked Oct 14 '13 at 1:58
mirimir
2231413
edited Oct 14 '13 at 9:50
asked Oct 14 '13 at 1:58
mirimir
2231413
asked Oct 14 '13 at 1:58
mirimir
2231413
asked Oct 14 '13 at 1:58
mirimir
2231413
2231413
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
add a comment |
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
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
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.
answered Jul 13 at 19:09
hargut
2564
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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.
answered Jul 13 at 19:09
hargut
2564
add a comment |
up vote
0
down vote
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.
answered Jul 13 at 19:09
hargut
2564
add a comment |
up vote
0
down vote
up vote
0
down vote
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.
answered Jul 13 at 19:09
hargut
2564
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.
answered Jul 13 at 19:09
hargut
2564
answered Jul 13 at 19:09
hargut
2564
answered Jul 13 at 19:09
hargut
2564
answered Jul 13 at 19:09
hargut
2564
2564
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%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
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
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