Suse linux route add

Suse /etc/sysconfig/network/routes file

Yast allows you to specify a default router in the format that you used to configure an interface. This is fine for a leaf node in a simple network. However, if the network has more than one router, or you actually want to set up a router, you’ll need need to specify a routing table. It can be done via Yast or by editing configuration files (which can be overwritten by Yast).

The routing table is set up in SUSE via the configuration files /etc/sysconfig/network/routes and /etc/sysconfig/network/ifroute-*.

All the static routes required by the various system tasks can be entered in the /etc/sysconfig/network/routes file: routes to a host, routes to a host via a gateway, and routes to a network.

For each interface that needs individual routing, define an additional configuration file: /etc/sysconfig/network/ifroute-*.

Replace * with the name of the interface.

The file routes contains a routing table, which will be set up by the script /sbin/init.d/route whenever a networking runlevel (by default runlevels two and three) is reached.

Routes are made permanent in Suse by adding routes in Yast

Yast -> Network Devices -> Network card -> Edit -> Routing

Editing /etc/sysconfig/network/routes directly

Or you can edit edit /etc/sysconfig/network/routes if you prefer the CLI.

The routing table is set up in SUSE LINUX via the configuration files /etc/sysconfig/network/routes and /etc/sysconfig/network/ifroute-*.

All the static routes required by the various system tasks can be entered in the /etc/sysconfig/network/routes file: routes to a host, routes to a host via a gateway, and routes to a network.

For each interface that needs individual routing, define an additional configuration file: /etc/sysconfig/network/ifroute-*. Replace * with the name of the interface.

The file routes contains a routing table, which will be set up by the script /sbin/init.d/route whenever a networking runlevel (by default runlevels two and three) is reached. For example:

10.29.9.100 10.29.129.1 255.255.255.255 - 10.4.33.238 10.29.129.1 255.255.255.255 - 10.29.2.13 10.29.129.1 255.255.255.255 - 10.29.2.18 10.29.129.1 255.255.255.255 - 10.29.7.0 10.29.129.1 255.255.255.0 - 10.192.0.0 10.29.129.1 255.192.0.0 - default 10.29.129.3 - -

The structure of the /etc/sysconfig/network/routes file

1. The first column specifies a destination. This can be either a network address, a host address, or the string default for the default gateway. Whether the given address is a host or a network is determined by the netmask given in the third column. The network mask for a host is always 255.255.255.255. Everything else specifies a network route. Network route means a route to a network, whereas a host route is a route to a single host.
2. The second column gives either the IP address of the router, which should be used to reach the destination given in the first column, or the special value 0.0.0.0, which means that all traffic headed to the destination will be given to1 the device specified in the last column. If a gateway address is given, the device specification is optional.
3. The third column contains netmask.

Your browser does not support iframes.

NEWS CONTENTS

Old News 😉

How to setup persistent Static Routes in openSUSE 11.0 SUSE & openSUSE

In openSUSE 11.0, the network setup is by default controller by «NetworkManager» and this is different from the traditional netcontrol. With NetworkManager, users control the Network Interfaces. To confirm this, in GNOME from Computer � Yast � Network Devices � Network Settings, check for option «User Controlled with Network Manager» under Network Setup Method. Or, check for the line ‘NETWORKMANAGER=»yes»‘ in /etc/sysconfig/network/config file.

This may not be a viable option to use on SUSE enterprise Desktop as in a enterprise environment you wouldn’t want the user to modify or control network settings.

Network Manager setup in openSUSE

To setup persistent Statis Routes in openSUSE 11.0 when network settings are controlled by NetworkManager, then try the following:

1. Create a ifroute- file for each interface

For every network interface on the system which needs individual persisten static routing table create a «ifroute-» file in the /etc/sysconfig/network/ directory.

where is the name of the interface

For instance, on my system the interface name is eth0 and hence I create a file called

/etc/sysconfig/network/ifroute-eth0

This file should have the static route entries for the hosts or networks in any of the following format:

DESTINATION GATEWAY NETMASK INTERFACE [ TYPE ] [ OPTIONS ]
Example
192.168.1.1 192.168.233.2 255.255.255.255 eth0

DESTINATION GATEWAY PREFIXLEN INTERFACE [ TYPE ] [ OPTIONS ]
Example
10.1.1.0 192.168.233.2 24

DESTINATION/PREFIXLEN GATEWAY — INTERFACE [ TYPE ] [ OPTIONS ]
10.1.1.0/24 192.168.233.2 —

In the above each of the field is seperated by a TAB. [TYPE][OPTIONS] are optional.

If you not in the above, Example 2 & 3 mean exactly the same. Only represented in different formats.

So, I created a file as follows on my system

SAIBABA:~ # cat /etc/sysconfig/network/ifroute-eth0
10.1.1.1 192.168.233.2 255.255.255.255 eth0
10.10.10.0 192.168.233.2 24 eth0
172.20.1.0/24 192.168.233.2 � eth0

2. NetworkManager POST_UP Script

With NetworkManager, the POST_UP scripts are fetched from /etc/sysconfig/network/if-up.d/ directory and is set to ‘yes’ (enabled) by default. In simple terms, any script that you want to run once the Network interface up and active, simply drop them into this directory or create a symbolic link to the script file in this directory.

In SUSE and openSUSE, there are the following scripts in /etc/sysconfig/network/scripts/ directory which assist in bring up/down Interface routes and to check the status

ifup-route

To bring up static routes. This reads the file /etc/sysconfig/network/ifroute-* file.

ifdown-route

To clear the static routes loaded

ifstatus-route

To check the current status of the routes

SAIBABA:~ # /etc/sysconfig/network/scripts/ifstatus-route eth0
Configured routes for interface eth0:
169.254.0.0 � 255.255.0.0 eth0
10.1.1.1 192.168.233.2 255.255.255.255 eth0
10.10.10.0 192.168.233.2 24 eth0
172.20.1.0/24 192.168.233.2 � eth0
Active routes for interface eth0:
10.1.1.1 via 192.168.233.2
172.20.1.0/24 via 192.168.233.2
192.168.233.0/24 proto kernel scope link src 192.168.233.128
10.10.10.0/24 via 192.168.233.2
169.254.0.0/16 scope link
default via 192.168.233.2 proto static
3 of 4 configured routes for interface eth0 up

3. Create a Symbolic File for ifup-route

In the POST_UP directory for NetworkManager i.e, /etc/sysconfig/network/if-up.d/ create a Symbolic link as follows to the ifup-route script as follows:

SAIBABA:~ # ln -s /etc/sysconfig/network/scripts/ifup-route /etc/sysconfig/network/if-up.d/ifup-route

Thats it. You can either restart your system or simply restart your Network service for the change to take effect.

SAIBABA:~ # /etc/init.d/network restart
Shutting down the NetworkManager done
Shutting down network interfaces:
eth0 device: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) done
Shutting down service network . . . . . . . . . . . . . done.
Starting the NetworkManager done

Thats it! We are done.

Источник

OpenSuse Leap 15 iproute2 basics

In modern OS such as OpenSuse Leap 15, backward compatibility for older net-tools commands such as ifconfig, route, etc. has been removed. Hence it is necessary to use ‘ip‘ commands for most of the network tasks.

Contents

Check current ip addresses

to list all interfaces and all addresses assigned to various interfaces. Note that each interface can have multiple addresses (IPv4, IPv6) associated with it.

Assign ip address

To assign ip address instead of using ‘ifconfig / ‘ use:

For example, ip addr add 10.0.0.1/24 dev eth1

Use ‘del‘ in place of ‘add‘ to remove the address

See routing table

To see routing table instead of using ‘route -n‘ use:

Set default gateway

To set default gateway instead of using ‘route add default gw []‘ use:

ip route add default via dev

For example, ip route add default via 192.168.1.2 dev eth0

Add static route

To add static route instead of using ‘route add -net / gw [dev ]‘ use:

For example, ip route add 172.16.32.0/24 via 192.168.1.1 dev eth0

See network state information

To see network state information instead of using ‘netstat -l‘ use:

See arp table

To see arp table instead of using ‘arp -a -n‘ use:

Bring interface up

If in «ip addr show» output interface is showing down, adding just IP via «ip addr add» may not be enough to bring it up. To bring interface up use:

Источник