Sam or Bill

Ok, fair enough. But if I create an uplink to a router and specifically
define VLANs e.g. 25, 26, 27 etc. I assume (yes, I realize the danger)
that VLAN 1 will be included. However, I am concerned on how to create the
router interface the switch is linking to.
In the config I posted I created sub-interfaces and ties the VLANs to them
and defined the subnet (albeit only /30's) that is in the VLAN. I am
wondering how the VLAN 1 traffic will react to the interface. I would like
to be able to route from the VLAN 1 interface on the 3550 to the router.
I am not sure about the "untagged" comment.
When the traffic leaves the 3550 on it's way to the router is there a VLAN
ID of 1? I somehow doubt it. I believe the VLAN 1 is used in the switch
itself. Perhaps I am wrong, but it seems to me with the scenario I am
working that there would be traffic that has an explicit VLAN ID defined and
other traffic that has no VLAN ID set (untagged) This is just what I assume
and am not sure however. Is it the case that if the traffic leaves the
switch on a trunk port it populates the VLAN ID with 1?

Thank you for your response. I am still looking for answers/input as well.

----- Original Message -----
From: "Bill" 
To: 
Sent: Tuesday, March 04, 2003 8:19 PM
Subject: Re: Native VLAN question [7:64431]


> Hey Jim
> Supposing you take a new switch out of the box and don't configure any
> vlan's etc, all the ports will still be using a vlan. That vlan is called
> vlan1 and all ports are on vlan1 by default. The devices on those ports
> wouldn't need any router to route traffic since they all belong to the
same
> vlan and can talk directly.
>
> Hence, there is no such thing as untagged traffic.
> And yes, to answer your question-all the packets you talked about will
route
> fine.
>
> I'll appreciate comments by experts on this list if I am talking correct.
> Sam
>
> ""Jim Devane""  wrote in message
> news:[EMAIL PROTECTED]
> > I am kinda new to VLANs and need some advice.
> > I have a router which I have broken an interface into FastEthernet
> > subinterfaces. Each subinterface defines the VLAN. This has worked very
> > well. But I am wondering if it is possible to make this port a trunk
port
> > and have other non-tagged traffic arrive on this port as well.
> > Basically, I want to have tagged traffic and untagged traffic go to the
> same
> > Ethernet port, route the untagged traffic and tag the VLAN traffic. I am
> not
> > sure if I can have both types of frames on the same port
> > I have posted my router's config below:
> > I need to know how to allow other untagged traffic to be recieved on
this
> > port.
> >
> > thanks,
> > jim
> > interface FastEthernet0/1
> >  description TRUNK_PORT
> >  no ip address
> >  no ip directed-broadcast
> >  no ip mroute-cache
> >  load-interval 30
> >  duplex full
> > !
> > interface FastEthernet0/1.25
> >  description VLAN
> >  encapsulation dot1Q 25
> >  ip address 192.168.64.101 255.255.255.252
> >  no ip directed-broadcast
> > !
> > interface FastEthernet0/1.26
> >  description VLAN 26
> >  encapsulation dot1Q 26
> >  ip address 192.168.64.97 255.255.255.252
> >  no ip directed-broadcast




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=64441&t=64431
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to