traceroute6 command may cause the ProxySG to restart

Solution

Overview

ProxySG restarts on traceroute6 for non-reachable hostnames

Workaround

1. Do not traceroute6 to a hostname that does not contain an IPv6 address
2. Do not traceroute6 to an invalid IPv6 address

Cause
Resolution

The restart occurs due to DNS resolution failure. In this case, for a host that does not have an IPv6 address, the DNS resolution returns a NULL pointer, which is then deferenced.

This is B#161610 and has been fixed in :

- SGOS 5.5.6.5

- SGOS 5.5.7.1 and newer SG 5.5.x versions

 

SGOS 6.x is not affected by this.

Workaround
Additional Information
Bug Number
InQuira Doc IdKB4643
Attachment

Article Feedback

Did this Article solve your issue?
Additional Comments:
 
Previous MonthNext Month
SunMonTueWedThuFriSat