If you see those logs, iptables is letting the traffic through.
You need to modify the config file though. The default one has no way of knowing what is your local subnet, and who should squid proxy for - you do not want to be an open proxy, allowing connections from everyone.
Code:
# 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 localnet src 192.168.0.0/16 # RFC1918 possible internal network
....
# 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 home
Uncomment the relevant localnet entry, and the last but one line. If your local network is 192.168.123.0 then it should look like this:
Code:
# 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 localnet src 192.168.0.0/16 # RFC1918 possible internal network
....
# 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 home
Or you can ber more specific and say 'acl localnet src 192.168.123.0/24', or specify multiple access-list entries
acl localnet src x.x.x.x/aa
acl guest1 src y.y.y.y/bb
http_access allow localnet
http_access allow guest1