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

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

0 FormerMember over 5 years ago

Hi jang430

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,
Cancel
Vote Up 0 Vote Down

Cancel
0 jang430 over 5 years ago 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
Cancel
Vote Up 0 Vote Down

Cancel
0 jang430 over 5 years ago in reply to jang430

Any way to recover from this?
Cancel
Vote Up 0 Vote Down

Cancel
0 rfcat_vk over 5 years ago in reply to jang430

Hi,

connect a keyboard and monitor to the XG, log on to the console and follow the CLI commands as shown in the CLI KBA on the righthand side of the forums.

Ian
Cancel
Vote Up 0 Vote Down

Cancel
0 jang430 over 5 years ago in reply to rfcat_vk

Is this where I should pay attention? nat-policy?

nat-policy

application-server

failover

mail-notification

Displays the nat policy settings, enabled or disabled, for the protected application servers.
Cancel
Vote Up 0 Vote Down

Cancel
0 jang430 over 5 years ago in reply to jang430

I went to Device Console, and run set advanced_firewall sys-traffic-nat delete 192.168.1.1xx (this being the IP address of the host). Didn't work.
Cancel
Vote Up 0 Vote Down

Cancel
0 rfcat_vk over 5 years ago in reply to jang430

Hi,

that would suggest there is another configuration error causing the issue.

Look at things like the network configuration using the console.

Ian
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 rfcat_vk over 5 years ago in reply to jang430

Hi,

that would suggest there is another configuration error causing the issue.

Look at things like the network configuration using the console.

Ian
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 jang430 over 5 years ago in reply to rfcat_vk

Hahaha, I'm about to give up. Very tempted to do a reset to factory default.

The good thing about putting the rules there on my own means I know what each of them do, or at least, I know how to recreate it.

Let me think if I still want to bear another day without a working firewall.
Cancel
Vote Up 0 Vote Down

Cancel