Cisco CTC software

rtcanathan · 07-26-2011, 07:21 AM

This may not be a protocol control issue, so if its not I'll repost in the correct forum.

A few of our staff connect to a Cisco sonet, via the Cisco CTC software, which is java based (ballpark ver 1.5.0-x, more current versions of java do not work).

With the Untangle VM running, we can browse to any of the shelves, launch the application, but during its discovery process, it hangs. Now, if I stop the Untangle VM, the CTC software works fine. I look in the Protocol Control event log, and see nothing related to this being blocked. Same goes for Intrusion Detection, firewall, or even Web Filter.

I'm kind of scratching my head about which part of Untangle is knocking down the CTC software. Could it see the older version of Java as a vulnerability? I'm not really for sure where to look, since I see nothing related to it in any of the event logs.

hlarsen · 07-26-2011, 08:11 AM

have you tried it with a Bypass Rule?

rtcanathan · 07-26-2011, 09:19 AM

Could you be a little more specific? I'm still fairly new.

hlarsen · 07-26-2011, 09:28 AM

at Config > Networking > Advanced > Bypass Rules, you can add rules that basically exempt traffic from being scanned. sometimes traffic of certain types just doesn't like being scanned at all; if you don't see blocks from within any apps then this may be the case.

a quick thing to try is setting a bypass rule up with one qualifier - Source Address: (internalIP), then try testing the software from the machine you specify.

rtcanathan · 07-26-2011, 09:56 AM

That seems to have fixed. I created a bypass for each shelf, and although it would throw an error when logging into the application, everything is fully functional. I'll review that error, it may be something specific to Cisco.

07-26-2011, 07:21 AM	#1 (permalink)
rtcanathan Newbie Join Date: May 2011 Posts: 9	Cisco CTC software This may not be a protocol control issue, so if its not I'll repost in the correct forum. A few of our staff connect to a Cisco sonet, via the Cisco CTC software, which is java based (ballpark ver 1.5.0-x, more current versions of java do not work). With the Untangle VM running, we can browse to any of the shelves, launch the application, but during its discovery process, it hangs. Now, if I stop the Untangle VM, the CTC software works fine. I look in the Protocol Control event log, and see nothing related to this being blocked. Same goes for Intrusion Detection, firewall, or even Web Filter. I'm kind of scratching my head about which part of Untangle is knocking down the CTC software. Could it see the older version of Java as a vulnerability? I'm not really for sure where to look, since I see nothing related to it in any of the event logs.

07-26-2011, 08:11 AM	#2 (permalink)
hlarsen Join Date: Jul 2010 Location: sfba URLs submitted: 1 Posts: 1,139	have you tried it with a Bypass Rule? __________________ Attention: Support on the Untangle Forums is provided by volunteers and community members. If you need official Untangle support please call or email support@untangle.com.

07-26-2011, 09:28 AM	#4 (permalink)
hlarsen Join Date: Jul 2010 Location: sfba URLs submitted: 1 Posts: 1,139	at Config > Networking > Advanced > Bypass Rules, you can add rules that basically exempt traffic from being scanned. sometimes traffic of certain types just doesn't like being scanned at all; if you don't see blocks from within any apps then this may be the case. a quick thing to try is setting a bypass rule up with one qualifier - Source Address: (internalIP), then try testing the software from the machine you specify. __________________ Attention: Support on the Untangle Forums is provided by volunteers and community members. If you need official Untangle support please call or email support@untangle.com.

Protect

Filter

Perform

Connect

Manage

Add-Ons

07-26-2011, 09:19 AM	#3 (permalink)
rtcanathan Newbie Join Date: May 2011 Posts: 9	Could you be a little more specific? I'm still fairly new.

07-26-2011, 09:56 AM	#5 (permalink)
rtcanathan Newbie Join Date: May 2011 Posts: 9	That seems to have fixed. I created a bypass for each shelf, and although it would throw an error when logging into the application, everything is fully functional. I'll review that error, it may be something specific to Cisco.