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