Squid config not responding or am I stupid?

Question

Squid

There is a Squid config. There are a lot of cluckers connected via LAN to a computer with an octopus. Purpose: to deny access to the Internet to all IPs from 192.168.0.233 to 192.168.0.254.
When you try to do this, the config is reloaded without any warnings, but these computers still have access. Help me, such a dumbass.

squid config

#	WELCOME TO SQUID 3.1.20
#	----------------------------
#	
#	This is the documentation for the Squid configuration file.
#	This documentation can also be found online at:
#		http://www.squid-cache.org/Doc/config/
#	
#	You may wish to look at the Squid home page and wiki for the
#	FAQ and other documentation:
#		http://www.squid-cache.org/
#		http://wiki.squid-cache.org/SquidFaq
#		http://wiki.squid-cache.org/ConfigExamples
#	

acl manager proto cache_object
#acl localhost src 127.0.0.1/32 ::1
#acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
#acl localnet src 10.0.0.0/8	# RFC1918 possible internal network
#acl localnet src 172.16.0.0/12	# RFC1918 possible internal network

acl badboys src 192.168.0.233-192.168.0.254
acl localnet src 192.168.0.2-192.168.0.232

#acl localnet src 192.168.0.0/24	# RFC1918 possible internal network
#acl localnet src fc00::/7       # RFC 4193 local private network range
#acl localnet src fe80::/10      # RFC 4291 link-local (directly plugged) machines

acl SSL_ports port 443
acl Safe_ports port 80		# http
acl Safe_ports port 554 	#test port
acl Safe_ports port 1119	# blizzard ports
acl Safe_ports port 1120	# blizzard ports
acl Safe_ports port 3724	# blizzard ports
acl Safe_ports port 4000	# blizzard ports
acl Safe_ports port 6112	# blizzard ports
acl Safe_ports port 6113	# blizzard ports
acl Safe_ports port 6114	# blizzard ports
acl Safe_ports port 8000	# tcp
acl Safe_ports port 8001	# udp 
acl Safe_ports port 21		# ftp
acl Safe_ports port 443		# https
acl Safe_ports port 70		# gopher
acl Safe_ports port 210		# wais
acl Safe_ports port 1025-65535	# unregistered ports
acl Safe_ports port 280		# http-mgmt
acl Safe_ports port 488		# gss-http
acl Safe_ports port 591		# filemaker
acl Safe_ports port 777		# multiling http
acl CONNECT method CONNECT
http_access allow Safe_ports

# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost
http_access deny badboys

# And finally deny all other access to this proxy
http_access deny all


# Squid normally listens to port 3128
http_port 8080

# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid3

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp:		1440	20%	10080
refresh_pattern ^gopher:	1440	0%	1440
refresh_pattern -i (/cgi-bin/|\?) 0	0%	0
refresh_pattern (Release|Packages(.gz)*)$      0       20%     2880
# example lin deb packages
#refresh_pattern (\.deb|\.udeb)$   129600 100% 129600
refresh_pattern .		0	20%	4320

Answer 1

And where did you get the idea that you can specify a range of addresses like that?

acl badboys1 src 192.168.0.233/32
acl badboys2 src 192.168.0.234/31
acl badboys3 src 192.168.0.236/30
acl badboys4 src 192.168.0.240/28
acl localnet src 192.168.0.0/24

http_access deny badboys1
http_access deny badboys2
http_access deny badboys3
http_access deny badboys4
http_access allow localnet

Answer 2

As I said above, rewrite ACL's like this:
acl badboys src 192.168.0.233-192.168.0.254/24
acl localnet src 192.168.0.2-192.168.0.232/24
put deny badboys BEFORE allow localnet in the config.
And more - you do not forget to reload a squid, after a config change? :-)