[opensuse] default routeS post-13.1
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
[13.2 and Tumbleweed, with Wicked; no wireless; 1 interface per host] Googling 'site:opensuse.org sdb: network" produces nothing containing string "wicked". 'site:opensuse.org sdb: network wicked' produces nothing containing string "sdb:". https://en.opensuse.org/Portal:Wicked contains nothing obviously about configuration in its few listed topics. Now that the old ways have been replaced with Wicked, search results are even harder to sift through, assuming one can get onto the web in the first place... Can more than one default route per interface be configured? If so, where? /etc/sysconfig/network/ifroute-<interface> ??? /etc/sysconfig/network/routes ??? elsewhere ??? If not, which file or files must be changed to contain the relevant GW IP? I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much? I tried this several hours ago. Getting/using an IP was no problem. Working DNS was no problem. Never could get a default route into a routing table. 'route add default gw <IP>' didn't do anything regardless of what I tried changing in /etc/sysconfig/network/. What else I tried I cannot remember. :-( Same machine I specially preconfigured before leaving here with an additional 13.1 with DHCP. So when I left here, I had 1 DHCP and 3 fixed IP openSUSE installations that worked. Routing worked there in 13.1 with DHCP initially (e.g. success to ping www.google.com), but never again after lost Dlink DIR-655 router password required doing a hard reset, which reset its IP to its default 192.168.0.1. Afterward, no matter what I booted, if ifconfig -a showed a properly configured interface, I could reach the router and login with Firefox, and I could ping the router, but I could not ping www.google.com ('no route to host', among other observed failures, such as no reaction at all, depending on which OS booted). I gave YaST2 a try in either 13.2 or TW, but it didn't give me a working GW either. :~( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
В Mon, 06 Apr 2015 20:31:13 -0400 Felix Miata <mrmazda@earthlink.net> пишет:
Can more than one default route per interface be configured?
How is it supposed to work? How should system select which route to use?
I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much?
Show fix IP you configured and IP of (default) router you want to use. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Andrei Borzenkov composed on 2015-04-07 06:22 (UTC+0300):
Felix Miata composed:
Can more than one default route per interface be configured?
I think I partially answered this by experiment. I booted TW to find default route 192.168.1.1 while using router with 192.168.0.1. I ran route add default gw 192.168.0.1 eth0 That produced: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 which is working, but I have no idea if this holds any potential problem.
How is it supposed to work?
I don't know.
How should system select which route to use?
Round robin? Pick fastest? First in list?
I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much?
Show fix IP you configured and IP of (default) router you want to use.
location 1 (router 1): 192.168.0.1 location 2 (router 2): 192.168.1.1 host: 192.168.0.121 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
В Mon, 06 Apr 2015 23:45:04 -0400 Felix Miata <mrmazda@earthlink.net> пишет:
Andrei Borzenkov composed on 2015-04-07 06:22 (UTC+0300):
Felix Miata composed:
Can more than one default route per interface be configured?
I think I partially answered this by experiment. I booted TW to find default route 192.168.1.1 while using router with 192.168.0.1. I ran
route add default gw 192.168.0.1 eth0
That produced:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
which is working, but I have no idea if this holds any potential problem.
Your system is using single router 192.168.0.1.
How is it supposed to work?
I don't know.
How should system select which route to use?
Round robin?
So half of the packets get lost?
Pick fastest?
Define fastest ...
First in list?
That is what it currently does. It will always use the first one. So having more than one effectively does nothing.
I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much?
Show fix IP you configured and IP of (default) router you want to use.
location 1 (router 1): 192.168.0.1
location 2 (router 2): 192.168.1.1
I assume default netmask ...
host: 192.168.0.121
Second one won't work. Gateway must be on locally attached network. It had always been this way. Even if you manage to fool your system in sending packets to this address, gateway won't know how to reply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/06/2015 11:53 PM, Andrei Borzenkov wrote:
Second one won't work. Gateway must be on locally attached network. It had always been this way.
Not quite. However, the route to the gateway must be known. So, if the gateway was on another lan, you'd need a connection and route to it. Generally, it's on the local lan though. It's also possible to specify just an interface and not an IP address for the gateway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
В Tue, 07 Apr 2015 07:51:49 -0400 James Knott <james.knott@rogers.com> пишет:
On 04/06/2015 11:53 PM, Andrei Borzenkov wrote:
Second one won't work. Gateway must be on locally attached network. It had always been this way.
Not quite. However, the route to the gateway must be known.
bor@opensuse:~> ip r l default via 192.168.1.1 dev wlan0 proto static metric 1024 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.46 bor@opensuse:~> sudo ip route add 1.2.3.4/24 via 2.3.4.5 dev wlan0 RTNETLINK answers: Invalid argument I'm curious how you create such route.
So, if the gateway was on another lan, you'd need a connection and route to it. Generally, it's on the local lan though. It's also possible to specify just an interface and not an IP address for the gateway.
Yes, interface-only routes are quite useful with point-to-point links to conserve address space. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 01:29 PM, Andrei Borzenkov wrote:
В Tue, 07 Apr 2015 07:51:49 -0400 James Knott <james.knott@rogers.com> пишет:
On 04/06/2015 11:53 PM, Andrei Borzenkov wrote:
Second one won't work. Gateway must be on locally attached network. It had always been this way. Not quite. However, the route to the gateway must be known. bor@opensuse:~> ip r l default via 192.168.1.1 dev wlan0 proto static metric 1024 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.46 bor@opensuse:~> sudo ip route add 1.2.3.4/24 via 2.3.4.5 dev wlan0 RTNETLINK answers: Invalid argument
I'm curious how you create such route.
I'm not sure with IP, but this is from the "route" man page: gw GW route packets via a gateway. NOTE: The specified gateway must be reachable first. This usually means that you have to set up a static route to the gateway beforehand. If you specify the address of one of your local interfaces, it will be used to decide about the interface to which the packets should be routed to. This is a BSDism compatibility hack." And: "route add default gw mango-gw adds a default route (which will be used if no other route matches). All packets using this route will be gatewayed through "mango-gw". The device which will actually be used for that route depends on how we can reach "mango-gw" - the static route to "mango-gw" will have to be set up before."
So, if the gateway was on another lan, you'd need a connection and route to it. Generally, it's on the local lan though. It's also possible to specify just an interface and not an IP address for the gateway.
Yes, interface-only routes are quite useful with point-to-point links to conserve address space.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
В Tue, 07 Apr 2015 20:43:08 -0400 James Knott <james.knott@rogers.com> пишет:
On 04/07/2015 01:29 PM, Andrei Borzenkov wrote:
В Tue, 07 Apr 2015 07:51:49 -0400 James Knott <james.knott@rogers.com> пишет:
On 04/06/2015 11:53 PM, Andrei Borzenkov wrote:
Second one won't work. Gateway must be on locally attached network. It had always been this way. Not quite. However, the route to the gateway must be known. bor@opensuse:~> ip r l default via 192.168.1.1 dev wlan0 proto static metric 1024 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.46 bor@opensuse:~> sudo ip route add 1.2.3.4/24 via 2.3.4.5 dev wlan0 RTNETLINK answers: Invalid argument
I'm curious how you create such route.
I'm not sure with IP, but this is from the "route" man page:
bor@opensuse:~> LC_ALL=C sudo route add -host 1.2.3.4 gw 2.3.4.5 SIOCADDRT: Network is unreachable
gw GW route packets via a gateway. NOTE: The specified gateway must be reachable first. This usually means that you have to set up a static route to the gateway beforehand. If you specify the address of one of your local interfaces, it will be used to decide about the interface to which the packets should be routed to. This is a BSDism compatibility hack."
And:
"route add default gw mango-gw adds a default route (which will be used if no other route matches). All packets using this route will be gatewayed through "mango-gw". The device which will actually be used for that route depends on how we can reach "mango-gw" - the static route to "mango-gw" will have to be set up before."
So, if the gateway was on another lan, you'd need a connection and route to it. Generally, it's on the local lan though. It's also possible to specify just an interface and not an IP address for the gateway.
Yes, interface-only routes are quite useful with point-to-point links to conserve address space.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
On Wed, Apr 8, 2015 at 2:54 PM, James Knott <james.knott@rogers.com> wrote:
On 04/07/2015 11:31 PM, Andrei Borzenkov wrote:
bor@opensuse:~> LC_ALL=C sudo route add -host 1.2.3.4 gw 2.3.4.5 Do you have a static route to 2.3.4.5?
No. I have default route so 2.3.4.5 is obviously accessible. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 01:29 PM, Andrei Borzenkov wrote:
So, if the
gateway was on another lan, you'd need a connection and route to it. Generally, it's on the local lan though. It's also possible to specify just an interface and not an IP address for the gateway.
Yes, interface-only routes are quite useful with point-to-point links to conserve address space.
With IPv6, the link local address is often used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/06/2015 11:45 PM, Felix Miata wrote:
That produced:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
which is working, but I have no idea if this holds any potential problem.
Fire up Wireshark to see where the packets are going, when you don't have a specific route. A default route is a route of last resort, when the computer/router doesn't know where else to send a packet. As such, you can only have one working default root. If you had those gateways on different interfaces, then the 2nd may be used when the first interface is down.
How should system select which route to use? Round robin?
Pick fastest?
First in list?
Routing is by longest address match. If there is no address match, then the default route is used. There is no round robin etc., unless load balancing is used. However, that requires it be supported at both ends. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
James Knott wrote:
Routing is by longest address match. If there is no address match, then the default route is used. There is no round robin etc., unless load balancing is used. However, that requires it be supported at both ends.
Slightly off-topic, but load balancing (or multi-path routing) is fairly easy to set up with "ip route nexthop": ip route add default nexthop via <path1> nexthop via <path2> The other end does not need to know. See e.g. http://lartc.org/howto/lartc.rpdb.multiple-links.html -- Per Jessen, Zürich (7.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 07:58 AM, Per Jessen wrote:
ip route add default nexthop via <path1> nexthop via <path2>
The other end does not need to know.
Now, how does incoming traffic get balanced? If you're running a protocol such as OSPF or EIGRP, you could balance traffic in both ways. You can also add redundancy protocols such VRRP or HSRP etc. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
James Knott wrote:
On 04/07/2015 07:58 AM, Per Jessen wrote:
ip route add default nexthop via <path1> nexthop via <path2>
The other end does not need to know.
Now, how does incoming traffic get balanced?
In my setup, with round-robin DNS. -- Per Jessen, Zürich (4.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 04:02 PM, Per Jessen wrote:
Now, how does incoming traffic get balanced? In my setup, with round-robin DNS.
How does DNS have anything to do with it? DNS is used to look up IP addresses. Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site? While that sort of thing is used by large servers, such as Google (anycast), I really don't see much need for small users. Also, with large servers, such as Google, it's used to balance geographically, not just what link is used to a single site. There are also load balancers that distribute incoming traffic, but again that has to be done at some other point, if you want multiple routes. For example, you might use a routing protocol, such as OSPF or EIGRP to load balance incoming traffic and a first hop redundancy protocol, such as GLBP, to balance over mulitple routers for outgoing. Etherway, you need something to load balance incoming and outgoing traffic. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-07 22:19, James Knott wrote:
On 04/07/2015 04:02 PM, Per Jessen wrote:
Now, how does incoming traffic get balanced? In my setup, with round-robin DNS.
How does DNS have anything to do with it? DNS is used to look up IP addresses. Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site?
Suse did just that some years ago. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUkQEQACgkQja8UbcUWM1zJyAD/R643exj550zy+aRwTc67VQ5o 95ofs7UYNP2rrZ6UtYwBAIceuLYPCOm5pTPlgWwXWNKNNnfXiEbYk9UBnulb1kW6 =0dwr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 04:38 PM, Carlos E. R. wrote:
How does DNS have anything to do with it? DNS is used to look up
IP addresses. Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site? Suse did just that some years ago.
As I mentioned in another note, large servers, such as Google will do that for geographically distributed servers, but I didn't think Per was doing that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-08 02:46, James Knott wrote:
On 04/07/2015 04:38 PM, Carlos E. R. wrote:
Suse did just that some years ago.
As I mentioned in another note, large servers, such as Google will do
Suse is not in the same size range as google. LOL. :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUkfCAACgkQja8UbcUWM1xoxQD/RvpBtWl1n7yXVjrqTeJVfFRu Eal6UPWDoBYfgkV5UFIA/RujFx55ZqG60h8KBHmHBzwWb+mXuEc7btMJJMxez6di =d9CF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/07/2015 08:53 PM, Carlos E. R. wrote:
Suse is not in the same size range as google. LOL. :-)
True, but balancing among servers is not the same thing as balancing over routes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
James Knott wrote:
On 04/07/2015 04:38 PM, Carlos E. R. wrote:
How does DNS have anything to do with it? DNS is used to look up
IP addresses. Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site? Suse did just that some years ago.
As I mentioned in another note, large servers, such as Google will do that for geographically distributed servers, but I didn't think Per was doing that.
No, I'm not - round-robin DNS isn't overly useful if you want geographical distribution. All I need is multipathing, and round-robin DNS is sufficient. -- Per Jessen, Zürich (2.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
James Knott wrote:
On 04/07/2015 04:02 PM, Per Jessen wrote:
Now, how does incoming traffic get balanced? In my setup, with round-robin DNS.
How does DNS have anything to do with it? DNS is used to look up IP addresses.
Correct. Inbound traffic is destined for a <service>. <service>.example.com is configured with two or more IP addresses, each belonging to one of the inbound paths.
Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site?
Correct. It's perfectly normal - see named.conf::rrset-order. Think any high-availability N+1 setup. Also, see getaddrinfo() and /etc/gai.conf for info on how IP addresses are returned (un)sorted.
While that sort of thing is used by large servers, such as Google (anycast), I really don't see much need for small users.
Nor me, nor is multipath much needed by small users. I did say my comment was slightly off-topic.
Also, with large servers, such as Google, it's used to balance geographically, not just what link is used to a single site. There are also load balancers that distribute incoming traffic, but again that has to be done at some other point, if you want multiple routes.
For internal load balancing over multiple servers, we use LVS.
For example, you might use a routing protocol, such as OSPF or EIGRP to load balance incoming traffic and a first hop redundancy protocol, such as GLBP, to balance over mulitple routers for outgoing. Etherway, you need something to load balance incoming and outgoing traffic.
Well, in my business, for inbound traffic I use DNS round-robin, for outbound traffic I use a simple 'ip route nexthop' setup. -- Per Jessen, Zürich (1.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/08/2015 02:22 AM, Per Jessen wrote:
Well, in my business, for inbound traffic I use DNS round-robin, for outbound traffic I use a simple 'ip route nexthop' setup.
What you're describing is load balancing over multiple servers, which is not what I though we were discussing, that is multiple default routes and load balancing of Internet connections. If you want to see how real load balancing works, you may want to read up on first hop redundancy protocols and particularly Cisco's Gateway Load Balancing Protocol. With GLBP, there is a virtual router that hands out different MAC addresses, in response to arp requests for the virtual router IP address. There are then multiple routers that respond to the virtual router IP & MAC addresses. This results in load balancing that's transparent to the devices on the local network. https://en.wikipedia.org/wiki/First-hop_redundancy_protocols https://en.wikipedia.org/wiki/Gateway_Load_Balancing_Protocol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
James Knott wrote:
On 04/08/2015 02:22 AM, Per Jessen wrote:
Well, in my business, for inbound traffic I use DNS round-robin, for outbound traffic I use a simple 'ip route nexthop' setup.
What you're describing is load balancing over multiple servers, which is not what I though we were discussing, that is multiple default routes and load balancing of Internet connections.
James, for load balancing of outbound internet connections, I started by explaining that an easy way would be to use a setup with "ip route nexthop", including a link to an article with more details. You followed up asking what I did to the inbound traffic, and I explained. That's all.
If you want to see how real load balancing works,
I don't, I have a working setup. -- Per Jessen, Zürich (14.5°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
Felix Miata wrote:
[13.2 and Tumbleweed, with Wicked; no wireless; 1 interface per host]
Googling 'site:opensuse.org sdb: network" produces nothing containing string "wicked". 'site:opensuse.org sdb: network wicked' produces nothing containing string "sdb:". https://en.opensuse.org/Portal:Wicked contains nothing obviously about configuration in its few listed topics. Now that the old ways have been replaced with Wicked, search results are even harder to sift through, assuming one can get onto the web in the first place...
Can more than one default route per interface be configured?
Yes, but only one will be used. Besides, default routes are defined per routing table, not per interface.
If so, where?
/etc/sysconfig/network/ifroute-<interface> ??? /etc/sysconfig/network/routes ???
For a fixed configuration, update /etc/sysconfig/network/routes. For immediate changes, use "ip route add|del default".
I configure my own installations with fixed IP. I want to be able to take any of them elsewhere, discover the IP of the relevant gateway/router, and using mcedit, change, or add, whatever is necessary, without starting any GUI, YaST, or any kind of "manager". Is this asking too much?
Nope, should work fine. You can alter your network interface setup dynamically using 'ip' or edit /etc/sysconfig/network/ifroute-<interface> and use ifup/ifdown to effect the changes.
I tried this several hours ago. Getting/using an IP was no problem. Working DNS was no problem. Never could get a default route into a routing table. 'route add default gw <IP>' didn't do anything
Maybe try "ip route add default via <ip>" instead and check what "ip route show" says. ('route add' should do the same to my knowledge, but I've stopped using that a while ago).
Same machine I specially preconfigured before leaving here with an additional 13.1 with DHCP. So when I left here, I had 1 DHCP and 3 fixed IP openSUSE installations that worked. Routing worked there in 13.1 with DHCP initially (e.g. success to ping www.google.com), but never again after lost Dlink DIR-655 router password required doing a hard reset, which reset its IP to its default 192.168.0.1. Afterward, no matter what I booted, if ifconfig -a showed a properly configured interface, I could reach the router and login with Firefox, and I could ping the router, but I could not ping www.google.com ('no route to host',
Lack of a default route, probably. You can verify with "ip route get <ip>". -- Per Jessen, Zürich (1.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/ba86f283d614d2cd9b6116140eaddded.jpg?s=120&d=mm&r=g)
On 04/06/2015 08:31 PM, Felix Miata wrote:
Can more than one default route per interface be configured?
No. In fact you can't have more than one default route per device. The default route is used when no other route is available. Also, if you have only one interface, you need only a default route as no other routes are possible. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov
-
Carlos E. R.
-
Felix Miata
-
James Knott
-
Per Jessen