connection interrupt

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

connection interrupt

L6 Presenter

Hi,

An internal application is used for databese.It's default port is 5520

when we saw this behaviour we wrote an application override rule for that tcp port and named a new application.

after that we saw issue behaviour not changed(user is disconnectet from application sometimes, not everytime) but from logs we saw 2 applications match this traffic.

that was strange.if byte is big it is seen other app.

if it is small it see our app id which we created.

any ideas ? thanks.

1 REPLY 1

L4 Transporter

It's a known bug in using application overrides - I ran into it recently myself.

Rather than use an application override, just create a custom port and allow that in your rule.

Something like this

unreal.jpg

In this rule, the service ports "unreal_tcp1" and "unreal_tcp2" refer to the two specific ports used by this application, and are defined as services objects. The rest of the rule simply locks down source and destination as required.

If you need other applications on the same server, then make a *separate* rule for them. You need to keep this rule on its own because you need to restrict the custom service ports (otherwise, other applications would be blocked because they didn't match the ports defined as "unreal_tcp1" and "unreal_tcp2").

cheers.

  • 1383 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!