About FloridaGAL

FloridaGAL · 02-12-2016

I have a server inside my network that I want users to be able to access from the outside. To this end, I have setup a static nat between my internal address for this server (10.7.64.27) and one of the public ip addresses I have available (public2)....

FloridaGAL · 02-09-2016

Here's my setup 3 Networks across 3 switches (3x C3650) 10.7.64.1.x/24 (Vlan 7) 10.10.10.x/24 (Vlan 20) 192.168.1.x/24 (Vlan 15) The switches are all connected to each other, with Switch one have a connection to an ASA and the outside world. My go...

FloridaGAL · 02-12-2016

Well, my appliance can now ping out, which is positive. When I go to Public 2 on port 443, I get a tomcat webserver page. I'm wondering if there is a configuration problem on the appliance side now. I'll have to check with my coworker who set thi...

FloridaGAL · 02-12-2016

I'll clean it up once I confirm that I have everything working.

FloridaGAL · 02-12-2016

Sounds like you have it. Public 1 and Public 2 are on the same subnet. So... should be as simple as putting the correct ACL in place in the right location. I'll give that a try and see what happens.

FloridaGAL · 02-12-2016

In our ASA, the default route points all traffic to public 1. However, for the appliance inside the network users will be accessing it via public 2. I have created a static nat between the appliance private address and public 2. You are saying tha...

FloridaGAL · 02-12-2016

Our ASA uses 8.25. The default route in the box points to public1, that is why I feel I need a route to ensure that appliance box I have will send traffic to public2, which is the ip the users would go to to use this appliance. As to the ACL I can ...

Member Since	‎02-09-2016 05:10 AM
Date Last Visited	‎08-18-2017 03:54 AM
Posts	10

User Statistics

User Activity

Firewall Static NAT Issue

VLAN routing issue

Well, my appliance can now

I'll clean it up once I

Sounds like you have it.

In our ASA, the default route

Our ASA uses 8.25.