• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

VLAN Trunk / VPN

Status
Not open for further replies.
S

SKiTLz

2[H]4U
Joined
Aug 3, 2003
Messages
2,664
I'll try give the cliff notes. Just want to see if my line of thinking is corect.

Headend: Cisco ASA 5510
Remote: Cisco ASA 5505
Switching Gear: All procurve

Planning out my VLAN's and I intend on putting all my switching gear on a Management VLAN. I noticed today in some HP documentation that you cannot do Inter-VLAN routing on the Management VLAN which makes sense.

Now I am remote. I do all my admin tasks remote.

Now as a remote VPN user I will be pulling from the VPN pool (10.0.4.0/24 VLAN4). I'm a little unclear on exactly how to set this up so I can access my Management VLAN5 (10.0.5.0/24).

If I trunk the LAN interface of the ASA to my core procurve and tag the neccessary VLAN's can I just create a route on the ASA from VLAN4 (10.0.4.0/24) to VLAN5 (10.0.5.0/24)? Won't my packets be tagged as VLAN4 still? Or will re-routing the packet also re-tag it somehow.

I hope that makes sense. Pretty sure my thinking is ass backwards but after a few hours trying to get it I figured I'd just ask to be sure.

Cheers
 
As a follow up. If i was to assign both the inside interface and the logical vpn interface the same security level. Would traffic flow between them?
 
Status
Not open for further replies.
Back
Top