New answers tagged port-forwarding
Can you validate the cpu usage and mem usage of the asa when that happen ? Its easy to make a asa drop packets on high load with big WAN link
You could let one SSH server listen on a non-standard port (e.g. 51234) and then SSH to it by passing the "-p 51234" option to your SSH client. Man page for linux SSH client: http://www.freebsd.org/cgi/man.cgi?query=ssh
Configure the NAS and Hummingboard's SSH daemons to listen on different ports. For example, you could use port 22 for your NAS box and 2222 for the Hummingboard.
From your description, it could be a number of issues. With more details I might be able to help more. Here's what I would check out: Make sure your DNS entries are correct/haven't expired Make sure your SSL certs are installed correctly, cover all the subdomains in question, and are valid. Since you mentioned https, you should make sure you are also ...
That's not possible. Packets generated by local processes are not involved in the forwarding plan. As a consequence you won't be able to use PREROUTING and FORWARD chains in the tables locally generated packets will go through, but only OUTPUT (in raw/mangle/nat/filter tables) and POSTROUTING (in mangle/nat tables) chains while the routing decision is ...
I had a feeling this was simple, but perhaps this will help someone. I just needed to add an exception to my security group (ie my firewall) through my AWS console. I have come across this exact scenario several times before, after spending an hour plus checking my server's firewall. So I hope this will be a reminder to myself and others to check other ...
Top 50 recent answers are included