From bc3bf205e69f9528e72d1b2470631c2b9f8ff110 Mon Sep 17 00:00:00 2001 From: Michael Prokop Date: Wed, 17 Aug 2022 13:51:55 +0200 Subject: [PATCH] Fix iprange usage when configuring DHCP clients This seems to have been broken ever since it was integrated and nobody bothered to look into it since then :-/ --- grml-terminalserver-config | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/grml-terminalserver-config b/grml-terminalserver-config index 5f2f3fd..2140d69 100755 --- a/grml-terminalserver-config +++ b/grml-terminalserver-config @@ -168,10 +168,10 @@ for addresses from 192.168.0.101 to (and including) 192.168.0.200. IPRANGE_FROM_=`execute "ipcalc -nb $IP_/$NETMASK_" warn |awk '/HostMin/{print $2}'` # if we have x.x.x.1 as starting range address provide - # x.x.x.10 instead so we avoid possible conflicts with + # x.x.x.100 instead so we avoid possible conflicts with # default gateway - if echo $IPFROM | grep -c '\.1$' ; then - IPFROM="${IPFROM%%\.1}.10" + if echo "$IPRANGE_FROM_" | grep -q '\.1$' ; then + IPRANGE_FROM_="${IPRANGE_FROM_%%\.1}.100" fi IPRANGE_TO_=`execute "ipcalc -nb $IP_/$NETMASK_" warn |awk '/HostMax/{print $2}'` NETWORK_=`execute "ipcalc -nb $IP_/$NETMASK_" warn |awk '/Network:/{print $2}'` -- 2.1.4