No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


USG5300 cannot telnet

Publication Date:  2019-07-11 Views:  436 Downloads:  0

Issue Description

 Now there are two USG5300 running on the network and the main equipment cannot telnet .But when we undo default packet filtering , it can telnet .If we don’t undo default packet filtering ,we cannot telnet by using ACL to make packet filtering .

Alarm Information


Handling Process

 Checking the trouble bases on the reasons above ,we check ACL first ,find the ACL configuration is :
  ACL 3000
rule permit ip source destination is the loopback address of firewall .There is no problem between untrust and local by using ACL , so we can remove the question of ACL .
  On the host computer which IP address is using the way of tracert to run after the route path of which IP address is .We can find that the ping packet pass USG5000 untrust interface straight to reach backup firewall ,then it reaches loopback address from trust .we know client choose OSPF to take routing , the shortest path automatism accounted by OSPF get through firewall at first ,allowing client take the ACL control form trust to local and shutting default packet filtering ,the telnet will be normal .

Root Cause

There are some possible reasons:
A、 The ACL configuration is wrong.
B、 Route question ,it can induce that the path is not coming from untrust to local.
The example is question 2 , the route question induces that the path doesn’t pass the ACL configured domain.