sqlnet inspection with TNS redirects

Unanswered Question
Apr 23rd, 2008


Running default sqlnet inspection on ASA 7.2(3) for a multithread oracle DB. When the DB issues redirects for the connecting client sqlnet inspection drops the packet (packet captures and show service-policy confirm this). On investigation the redirect contains the following data which includes a FQDN and not an IP.


Is it possible for the ASA to perform a lookup against a FQDN when it receives such a packet? I suspect this would result in too long a processing delay. If it can't then it can't dynamically open the access for the new client request.

My understanding is that the ASA expects the format to be as below containing an ip not a FQDN


Disabling sqlnet inspection and creating an acl gets round the problem. Interestingly in 6.3(5) it seems this condition is handled differently with the redirect packet being allowed through back to the client however there won't be the slot created so in a way pointless the client getting the redirect.

Anyone come across this before?

thanks in advance

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
bwilmoth Tue, 04/29/2008 - 11:07

sqlnet inspection simply NATs embedded IP addresses and opens embryonic connections for return traffic, it does not restrict sql commands.


This Discussion