Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 27 subscribers
  • Views 1253 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Created NAT rule, applied, and now, can no longer access firewall 192.168.1.1, though can Ping

jang430

I've tried using Putty to SSH into it, but also not working.  I know the last NAT Rule caused the problem.  How do I get rid of it when I cannot access the firewall?



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi   

    Could you please share more detail on the NAT rule that you configured before losing the firewall access.

    Did you configure the DNAT rule with the "Any" service?

    Thanks, 

  • 0 in reply to FormerMember

    Created a NAT rule:

     

    Original source: Any  Original destination:  Any  Original service:  Any

    Translated source (SNAT): Original Translated destination (DNAT): To a Host with 10.10.2.34 (for example only) Translated service (PAT)

    Created a Service called Deluge TCP, forwarded the TCP 1:65535 to 8112

Reply
  • 0 in reply to FormerMember

    Created a NAT rule:

     

    Original source: Any  Original destination:  Any  Original service:  Any

    Translated source (SNAT): Original Translated destination (DNAT): To a Host with 10.10.2.34 (for example only) Translated service (PAT)

    Created a Service called Deluge TCP, forwarded the TCP 1:65535 to 8112

Children