ASA Firewall single interface

You should be able to when using VLANs and subinterfaces on the ASA. That way you can use the subinterfaces just like physical interfaces.

A small example:

interface GigabitEthernet0/4
 no nameif
 no security-level
 no ip address
!
interface GigabitEthernet0/4.100
 vlan 100
 nameif sub100
 security-level 80
 ip address 10.1.0.254 255.255.255.0
!
interface GigabitEthernet0/4.101
 vlan 101
 nameif sub101
 security-level 80
 ip address 10.2.0.254 255.255.255.0

That way you create the subinterfaces. On the switchport, create a trunk:

switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100-101
switchport mode trunk
switchport nonegotiate
no cdp enable

This way you can have multiple subinterfaces on one physical interface.

It’s not what I want please refer to my diagram.

same-security –traffic permit intra interface

Ah, wait. Let's see if I get it.

Server A is at another location which is connected through the router.
You want to have the connection from server B to server A to go through the firewall so you deny/allow certain traffic, right?

if you issue this command:

same-security-traffic permit intra-interface

you will be able to route traffic back to the same interface. The problem is the traffic from 10.0.0.0/24 to 192.168.1.0/24. This return traffic will not flow trough the ASA.

There are different solutions for this problem:

1. NAT traffic from 192.168.1.0/24 to 10.0.0.0/24 trough the inside interface on the ASA. This way the return traffic goes to the ASA first.
2. Disable TCP state in the inspection policy, this way the ASA will not drop connections with unknown state (which will happen when not all traffic hits the ASA).
3. Use the proxy arp to issue a second IP on the ASA 5505 inside interface to create a second subnet between the router and the ASA 5505: http://www.ducea.com/2008/05/31/adding-a-secondary-ip-address-on-a-cisco-asa-ethernet-interface/ (I have personally used this solution sometimes)

@henkva: how did you know it's a 5505? Am I in need of glasses?

Further, using the ASA as a router does work (i agree) but it's not the most optimal solution. If ciscosupp wants to have all the traffic going through the ASA, thus separating the two networks, I still think using VLANs is a good option.
I know it will work by using 2 interface in different subnets
Using my formentioned setup would give the same result, but you would only need one interface on the ASA.

The question is, what do you (ciscosupp) have in mind?

I mention the ASA 5505 but the TS does not specify the model. The commands however work for every ASA.

@erniebeek: Glasses can also be worn as fashion, who knows how pretty you are with glasses ;-)

I agree with Ernie that the VLAN setup is the best approach. But when you have a base license you do not have multiple VLANs on a single interface.

@henkva: met of zonder bril, 't blijft even erg ;)

On topic: the base license issue only applies to the 5505. Even worse, you can't have subinterfaces on the 5505, only on 5510 and up. The ports on the 5505 are more like switchports than routerports (though an ASA is neither of those!) to put it simple.

Thanks All yes I want server a to b and vice versa to go through firewall so I can deny/allow certain traffic.

I also don’t like this setup but I’m working on a site with this kind of setup so try testing it in my lab.


So basically my question is traffic from server A to B and vice versa must go through firewall so I can deny allow traffic. I will try the things you mentioned in the post