11-21-2013 07:32 PM - edited 03-11-2019 08:08 PM
Ok so I'm making this more complex than it needs to be and can't see the forest for the trees. I'm setting up an ASA 5510 with multiple contexts. I'm working with my main internal context for my internal traffic. I have created interfaces on this context as follows:
interface Ethernet0/0.1
description outside interface
nameif outside
security-level 0
ip address 1.1.1.2 255.255.255.252
interface Ethernet0/1.1
description inside interface for internal context
nameif inside
security-level 100
ip address 10.10.50.150 255.255.0.0
same-security-traffic permit intra-interface
route outside 0.0.0.0 0.0.0.0 1.1.1.1
NOTE: Also has ssh configuration but can't document that here.
My workstation has an IP 10.10.30.20 255.255.0.0 with a default gateway that points to my core switch (10.10.50.151).
When I try to access the inside interface of the ASA via ssh from my workstation I can't connect. I tried to ping the inside interface IP address of the ASA from my workstation and it doesn't reply. I can however ping anything on my internal network from the ASA through the inside interface. What am I missing on this?
Thanks.
11-21-2013 07:36 PM
enable
config t
route inside 10.10.30.0 255.255.255.0 10.10.50.151
That should do it
Value our effort and rate the assistance!
11-21-2013 07:37 PM
Also when uou enable SSH on the firewall you need to generate a key:
crypto key generate rsa modulus 1024
Value our effort and rate the assistance!
11-21-2013 10:23 PM
When I try to access the inside interface of the ASA via ssh from my workstation I can't connect. I tried to ping the inside interface IP address of the ASA from my workstation and it doesn't reply. I can however ping anything on my internal network from the ASA through the inside interface. What am I missing on this?
All of your network devices have a /16 so that traffic should not be hitting the Default Gateway of the PC.
Traffic should flow to the ASA
DO the following
cap capin interface inside match tcp host 10.10.30.20 host 10.10.50.150 eq 22
cap capin interface inside match icmp host 10.10.30.20 host 10.10.50.150
cap asp type asp-drop all circular-buffer
Then try to SSH only once and then try to ping only once
Afterwards share with us
show cap capin
show cap asp | include 10.10.30.20
Rate all of the helpful posts!!!
Regards,
Jcarvaja
Follow me on http://laguiadelnetworking.com
11-22-2013 07:39 AM
I did not see the netmask, it seems to be /16 can you post part of the switch configuration, the port that connects to the ASA.
interface Ethernet0/1.1
description inside interface for internal context
nameif inside
security-level 100
ip address 10.10.50.150 255.255.0.0
Also I see the sub-interface created but no vlan ID, the port that connected to the ASA needs to be defined as a trunk and you need to define VLANs.
Step 1 >>>> VLAN ID on that sub interface on the ASA
Step 2 >>>> Switch VLAN database and how the interface that connects to the ASA is configured.
Value our effort and rate the assistance!
11-22-2013 07:43 AM
If you added the route command that I put on my first post please remove it.
Value our effort and rate the assistance!
11-22-2013 09:51 AM
I figured out this issue but now have a new issue. The problem I had accessing the internal network from the ASA was due to the core switch I was being routed through. After looking at the core I saw that the default route was redirecting all traffic to the IP address of the inside interface on the production ASA. I have since pulled a spare switch and created an isolated network with a laptop and the inside interface on the new ASA. This worked great.
Now to my new problem. I am trying to access our ISPs external address from the ASA. The ISP has provided us with two vlans (100 and 101) on one connection and has given us two public IPs (one is the IP for the router on their end and the second is the IP I am supposed to use on my outside interface for vlan 100). I have created sub-interfaces on my outside interface and defined 0/0.1 as vlan 100 and 0/0.2 as vlan 101. VLAN 101 will go to our rack at our disaster recovery site so it will just be an extension of our existing network.
My network is as follows:
ISP (IP 2.2.2.1)
|
|
3560-CG switch (both ports -- to ISP and ASA outside interface are configured as trunk ports)
|
|
ASA (outside 2.2.2.2 vlan 100)
When I try to ping the 2.2.2.1 address from the ASA it doesn't work. If both my ASA outside port and the port to the ISP are both trunk ports shouldn't it route both VLANs (100 and 101) without any issue or am I missing something in my thinking?
Thanks.
11-22-2013 10:37 AM
First check the arp table to see if you see your gateway, then try another IP, 4.2.2.2, also check the ¨show run icmp¨ and confirm that you are not restricting ICMP. Check logs. Try to ping from behind the ASA and check packet tracer to see if it is hitting some NAT rule or any type of restriction.
Value our effort and rate the assistance!
11-25-2013 12:37 PM
I was able to get the ASA to be able to ping an external IP address (e.g. google.com) and also internally to my laptop. Now the last remaining piece is for the laptop to be able to access the Internet. Part of the problem I had was that the VLANs I have weren't defined in the vlan database on the switch. I also had to adjust the speed and duplex on the ports that the inside interface of the ASA is plugged into.
It looks like the issue is with the 3750 switch between my laptop and the ASA. If I try to ping the inside interface of the ASA from my switch that works but if I ping from the switch to an external IP address that I know responds it doesn't work. Seems like the switch is blocking something. There aren't any ACLs in place to allow traffic.
Any ideas?
Thanks.
11-25-2013 02:27 PM
If you have skype or if you want to call me at 407 241 29 65 ext 4863
Value our effort and rate the assistance!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide