Protocol Control Breaking Internet Traffic

hs-admin · 10-07-2011, 09:30 AM

I had a random issue with Protocol Control this morning. I have a primary network that is has a subnet mask of 248 with each subnet having its own rack. This morning the internet stopped working on the rack with 172.16.6.x subnet and protocol control installed. All ip/gateway/dns was being received properly from UT. All other subnets/networks working fine with protocol control installed. I disabled the modules in the rack and found protocol to be breaking the traffic. It has no block configurations except the Nimba & Code Red. It does have logs for P2P traffic and IM protocols but no blocks.
Any ideas what would cause this? Yesterday evening I installed Ad Blocker. This was the only change to the rack and removed it when trouble shooting the issue earlier this morning. It doesn't seem like this would have affected protocol control though.

dmorris · 10-07-2011, 09:33 AM

I doubt its protocol control. Its probably just that by turning off protocol control you reset all the sessions and forced new ones to be created which made things appear to start working without protocol control.

I would uncheck block on all the signatures and see if things work. (relevent: http://forums.untangle.com/protocol-...l-control.html)

If you have live support - give them a call.

hs-admin · 10-07-2011, 09:51 AM

When I originally turned it off and found things to be working again I tried reenabling it and traffic immediately shut down. Its currently off for that rack.
The only options that have been set to blcok in Protocol Control are the last two (Nimba & Code Red) These were also disabled during testing. The only other things "configured" in Protocol Control are set as "log" for P2P and IM.

hs-admin · 10-07-2011, 09:59 AM

I just rebooted the UT box and re-enabled protocol control on that subnet rack. Everything seems to be working fine now. Not sure of the reason but at least its working.

10-07-2011, 09:30 AM	#1 (permalink)
hs-admin Untangler Join Date: Oct 2009 Location: N. AZ Posts: 66	Protocol Control Breaking Internet Traffic I had a random issue with Protocol Control this morning. I have a primary network that is has a subnet mask of 248 with each subnet having its own rack. This morning the internet stopped working on the rack with 172.16.6.x subnet and protocol control installed. All ip/gateway/dns was being received properly from UT. All other subnets/networks working fine with protocol control installed. I disabled the modules in the rack and found protocol to be breaking the traffic. It has no block configurations except the Nimba & Code Red. It does have logs for P2P traffic and IM protocols but no blocks. Any ideas what would cause this? Yesterday evening I installed Ad Blocker. This was the only change to the rack and removed it when trouble shooting the issue earlier this morning. It doesn't seem like this would have affected protocol control though.

10-07-2011, 09:33 AM	#2 (permalink)
dmorris Untangle Junkie Join Date: Nov 2006 Location: San Mateo, CA URLs submitted: 10 Posts: 10,613	I doubt its protocol control. Its probably just that by turning off protocol control you reset all the sessions and forced new ones to be created which made things appear to start working without protocol control. I would uncheck block on all the signatures and see if things work. (relevent: http://forums.untangle.com/protocol-...l-control.html) If you have live support - give them a call. __________________ Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com

Protect

Filter

Perform

Connect

Manage

Add-Ons

10-07-2011, 09:51 AM	#3 (permalink)
hs-admin Untangler Join Date: Oct 2009 Location: N. AZ Posts: 66	When I originally turned it off and found things to be working again I tried reenabling it and traffic immediately shut down. Its currently off for that rack. The only options that have been set to blcok in Protocol Control are the last two (Nimba & Code Red) These were also disabled during testing. The only other things "configured" in Protocol Control are set as "log" for P2P and IM.

10-07-2011, 09:59 AM	#4 (permalink)
hs-admin Untangler Join Date: Oct 2009 Location: N. AZ Posts: 66	I just rebooted the UT box and re-enabled protocol control on that subnet rack. Everything seems to be working fine now. Not sure of the reason but at least its working.