VLAN problems

I think Watson pegged it for you. If you plug the PC into the switch port it would see the untagged packets on the native VLAN (in your case 1). I am not sure what "pass through" mode is. I don't have an Aastra phone in front of me. You simply tell the phone what VLAN the voice is on and it looks at the tag header and sorts out the frames.

If you are doing this for QoS make sure you have a priority set for the voice VLAN. Not sure what switch you are using or I could make specific recommendations if I am familiar with it.

Scott

What VLAN on your switch is set to the default VLAN?

Think of the phone as having an additional layer two interface so it is really a three port switch.

Port 1 hooks up to your switch, frames on the Voice VLAN should be tagged with 802.1q tags and the phone will pickup send out DHCP requests tagged with the voice VLAN tag.

The PC's is hooked up to the second port of the switch. Frames on this port are forwarded to the port connected to your switch. These frames are not tagged so whatever DHCP server is sitting in the default LAN will "hear" the DHCP requests from the PC attached to the second port.

Does this make sense?

Please don't take this question wrong, do you know how 802.1q VLAN's work in general (not specific to the Aastra)?

Scott

Ok excuse my humor but it is Sunday, I kinda figure a guy calling himself the "lanman" would know more about VLAN's than I do.

With all that being said, I can see some custom applications that could utilize the ability to respond to tags on the second port however this is not the norm.

What kind of switch do you have?

The default LAN should be your data LAN

The voice LAN should be your voice LAN (on a Cisco switch you can configure this and the phone will automatically pick up the parameters.)

This will result in the following behavior:

1. A PC plugged into a switch port will work with no special configuration
2. A phone plugged into a switch port configured properly will attach to the voice VLAN

With the phones picking up DHCP it sounds like you are almost 100%

Are we getting closer?

Scott

The PC VLAN port should not be set to anything for a typical configuration:

1. What type of switch are you using?
2. What traffic is on VLAN ID 1?
3. What traffic is on VLAN ID 2?
4. What VLAN is the default VLAN?

I can explain clearly with this data.

Scott

No trunk mode needed

The ports for the phones should be configured:

switchport mode access
switchport voice vlan 5

This will automatically set VLAN voice priority.

The port for the trixbox should be configured:

switchport mode access
switchport access vlan 1

There should be no need for a data VLAN tag on the phone except for special applications.

Scott

Second Internet connection?

Just set the port the router is attached to VLAN 5 with the command

switchport access vlan 5

Here is an example of how the phone looks to your switch:

Keep in mind for the most part your Dell switch IOS is identical to Cisco switch IOS, that is why the Cisco reference in the image.

That is all that it takes to configure VLAN's, 1 command. The voice VLAN command takes care of the tagging and priority in 1 line of code.

How do you intend to route across the VLAN's so that the PC's in VLAN 1 can manage the trixbox?

Scott

Great so did the voice vlan do the trick for you?

Yeah that is the command. Do you know how to use IOS.

You might have to telnet in, then you use the command "enable" to access full command mode.

One in command mode get a list of your ports by using the command "show int"

You then place that command on each interface.

Update interfaces in configuration mode.

So it would go like this

telnet switch
enable: Password
show int
config t
int f0/2 <-- Example port you want to change
switchport voice vlan 5
exit
write memory <<- save to flash.

You will have to look at the config with the "show run command"

Place the keyword no in front of any config line you may need to remove.

Scott