README.susefirewall
1This is a patch against SuSEfirewall2-3.1-206 (SuSE 9.x and older)
2It fixes the depancy from the dns daemon name 'named'
3After appending the patch, the SuSEfirewall is again able to autodetect
4the dnsmasq named service.
5This is a very old bug in the SuSEfirewall script.
6The SuSE people think the name of the dns server will allways 'named'
7
8
9--- /sbin/SuSEfirewall2.orig 2004-01-23 13:30:09.000000000 +0100
10+++ /sbin/SuSEfirewall2 2004-01-23 13:31:56.000000000 +0100
11@@ -764,7 +764,7 @@
12 echo 'FW_ALLOW_INCOMING_HIGHPORTS_UDP should be set to yes, if you are running a DNS server!'
13
14 test "$FW_SERVICE_AUTODETECT" = yes -o "$FW_SERVICE_AUTODETECT" = dmz -o "$FW_SERVICE_AUTODETECT" = ext && {
15- test "$FW_SERVICE_DNS" = no -a '!' "$START_NAMED" = no && check_srv named && {
16+ test "$FW_SERVICE_DNS" = no -a '!' "$START_NAMED" = no && check_srv dnsmasq && {
17 echo -e 'Warning: detected activated named, enabling FW_SERVICE_DNS!
18 You still have to allow tcp/udp port 53 on internal, dmz and/or external.'
19 FW_SERVICE_DNS=$FW_SERVICE_AUTODETECT
20@@ -878,7 +878,7 @@
21 test -e /etc/resolv.conf || echo "Warning: /etc/resolv.conf not found"
22 # Get ports/IP bindings of NAMED/SQUID
23 test "$FW_SERVICE_DNS" = yes -o "$FW_SERVICE_DNS" = dmz -o "$FW_SERVICE_DNS" = ext -o "$START_NAMED" = yes && DNS_PORT=`$LSOF -i -n -P | \
24- $AWK -F: '/^named .* UDP / {print $2}'| $GREP -vw 53 | $SORT -un`
25+ $AWK -F: '/^dnsmasq .* UDP / {print $2}'| $GREP -vw 53 | $SORT -un`
26 test "$FW_SERVICE_SQUID" = yes -o "$FW_SERVICE_SQUID" = dmz -o "$FW_SERVICE_SQUID" = ext -o "$START_SQUID" = yes && SQUID_PORT=`$LSOF -i -n -P | \
27 $AWK -F: '/^squid .* UDP/ {print $2}'| $SORT -un`
28