• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 353
  • Last Modified:

Virtual interface

Let me explain my network:

--Internet pipe--
--switch(publicVLAN/PrivateVLAN)-
--PIX506E(I have PIX515E on production) outside connected to PUBLIC VLAN
--Pix Inside connected to Switch private VLAN
 
because of OLD sin we assign 10.10.8.0/255.255.255.0(means only 253 host) to inside interface.

Now I would like to wash the OLD SIN, I like to expand the network. I know following solution is possiable

[1] change mask on PIX inside interface 255.255.0.0 -- as this is production setup and I need to do lot of changes in ACL/machine level / load balancer level. Downtime also require for this process.
[2] I came to know from cisco my pix will support virtual interface so I did following on staging setup:

-pix inside IP is 10.10.8.1
-created Virtual interface virt and IP is 10.10.15.2


now my problem is I am not able to ping 10.10.15.2 from my machines.

please give me suggestion or some other idea which will solve my problem

0
arvind
Asked:
arvind
1 Solution
 
lrmooreCommented:
virtual interfaces on a pix are not the same as sub--interfaces on a router. each still has its own security level. You still have to setup access-lists and nat rules or exemptions between interfaces of different security levels.
I'm assuming that you're talking about the 506? Then if you assign the two interfaces the same security level there will be NO communication between them.
If you're talking about the 515, and if you upgrade to v7 you can then setup basic routing between two interfaces of same security level
0
 
arvindAuthor Commented:
here is my running config:
***************************************
 PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
interface ethernet1 vlan4 logical
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif vlan4 virt security80
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 209.165.201.1 255.255.255.224
ip address inside 192.168.101.11 255.255.255.0
ip address virt 192.168.100.217 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 209.165.201.5 255.255.255.255 outside
pdm location 192.168.102.0 255.255.255.0 inside
pdm location 192.168.100.217 255.255.255.255 inside
pdm location 192.168.100.0 255.255.255.255 inside
pdm location 192.168.100.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 209.165.201.5 netmask 255.255.255.224
global (inside) 1 192.168.101.50-192.168.101.53 netmask 255.255.255.0
nat (outside) 1 0.0.0.0 0.0.0.0 0 0
nat (inside) 1 192.168.101.0 255.255.255.0 0 0
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.101.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.101.0 255.255.255.0 inside
telnet timeout 5
ssh 192.168.101.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:a69e42667c803b55e1d10fc2c87cab7f
: end
*********************************************
please suggest what shud I add in ACL?

0
 
charan_jeetsinghCommented:
hi arvind....what are these for....i really cant understand.....
global (inside) 1 192.168.101.50-192.168.101.53 netmask 255.255.255.0
nat (outside) 1 0.0.0.0 0.0.0.0 0 0
--------------------------------------------------------
anyway..i beleive u can give some different security level to virtual interface and define a acl permitting all ip withing 2 local networks...........

add>>
access-list 101 permit ip 192.168.101.0 255.255.255.0 192.168.100.0 255.255.255.255
access-list 101 permit ip 192.168.100.0 255.255.255.0 192.168.101.0 255.255.255.255
access-group 101 in interface virt
nat (inside) 1 192.168.100.0 255.255.255.0

i beleive that shud make things work as u dont have much on it besides for browsing traffic...
0
Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

 
arvindAuthor Commented:
I'll try this and let you know, By the way that is my testing pix config.

0
 
arvindAuthor Commented:
Not able to ping 101 series..

Could you please suggest me fresh config as this is my testing pix.

My inside interface conected to VLAN 14
Extra VLAN is VLAN4

0
 
arvindAuthor Commented:
I solved problem by myself...
0
 
NetminderCommented:
Closed, 500 points refunded.
Netminder
Site Admin
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now