Bug 862252

Summary: [PATCH] Squid doesn't reload on VPN up/down, or network down
Product: [Fedora] Fedora Reporter: Matthew Booth <mbooth>
Component: squidAssignee: Michal Luscon <mluscon>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: henrik, jonathansteffan, mluscon, thozza
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-14 11:34:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix network manager dispatcher none

Description Matthew Booth 2012-10-02 13:02:52 UTC
Created attachment 620276 [details]
Fix network manager dispatcher

Description of problem:
I use squid to reverse proxy some sites for a local network, some of which are only available over a VPN. If I start squid first, then the VPN, in that order, squid will not be able to access sites over the VPN. However, if I then cause squid to reconfigure it can access sites over the VPN. I assume squid is doing something with DNS caching, but haven't investigated.

I notice squid already has a network manager dispatcher script, but it appears a little unloved. Firstly it still uses /sbin/service. Secondly it only reloads on the "up" event.

The following works for me:

case "$2" in
        up|down|vpn-up|vpn-down)
                /bin/systemctl reload squid.service || :
                ;;
esac

I've attached a patched against rawhide git. This bug is applicable at least to F17, F18 and rawhide.

Version-Release number of selected component (if applicable):
squid-3.2.0.16-1.fc17.x86_64

Comment 1 Michal Luscon 2012-10-03 07:59:05 UTC
Thank you for your report and patch Matthew.

Comment 2 Fedora Update System 2012-10-26 15:15:48 UTC
squid-3.2.3-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc18

Comment 3 Fedora Update System 2012-10-26 19:42:30 UTC
Package squid-3.2.3-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing squid-3.2.3-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16962/squid-3.2.3-2.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-11-20 13:18:37 UTC
squid-3.2.3-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc17

Comment 5 Fedora Update System 2012-11-20 15:28:53 UTC
squid-3.2.3-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc16

Comment 6 Fedora Update System 2012-12-01 08:31:36 UTC
squid-3.2.3-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2012-12-01 08:42:56 UTC
squid-3.2.3-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.