exoscale-setup: Fixes bug12763

- This ensures that all ip route and ip rule commands are redirected to null if the output
   is not used to feed into a variable.
- This will prevent any error messages related to empty iproute tables being displayed
   during boot if an empty table is accessed.

Fixes: Bug#12763
Tested-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>

diff --git a/src/initscripts/helper/exoscale-setup b/src/initscripts/helper/exoscale-setup
index 02fdda2a355d1e5c95cc55785cc91a7614e0a966..acf5e4e4b951b0f025c1d3b6fb7f2ed830348c77 100644 (file)
--- a/src/initscripts/helper/exoscale-setup
+++ b/src/initscripts/helper/exoscale-setup
@@ -227,7 +227,7 @@ case "${reason}" in
                ip addr add "${new_ip_address}/${new_subnet_mask}" dev "${interface}"
 
                # Add the default route
-               ip route add default via "${new_routers}"
+               ip route add default via "${new_routers}" >/dev/null 2>&1
 
                # Setup DNS
                for domain_name_server in ${new_domain_name_servers}; do