Re: FreeBSD 6.2 does not reply to 802.1Q frame



If I switch off 802.1Q in my IP phone (Siemens OptiPoint), then I also would
have to switch off 802.1Q on all other phones in our network; therefore,
this is not feasible. Is it a known bug in FreeBSD that it cannot process
frames for which the VLAN ID is 0?

- Frank

"Martin" <not-for-mail@xxxxxxxxxxx> wrote:
Frank Munkert wrote:
My IP phone does not use VLANs. "vlan 0" means that only the priority tag
in the 802.1Q Ethernet frame shall be considered, and that the VLAN tag
shall be ignored.
A basic question is whether anything on your network (FreeBSD firewall,
ethernet switches, or upstream router) is actually going to recognize the
priority tag. If not, then you might achieve the same effect in other
ways, e.g.

1) If you're using PF and ALTQ, then you could turn off the phone's 802.1Q
tagging, and configure ALTQ traffic shaping based on IP address or
protocol ports.

2) Configure the phone to use VLAN 2 (say) and give priority to traffic
from that VLAN. IP phones are often configurable to use VLANs, so that
corporate deployments can easily separate VOIP frames from other traffic.


.



Relevant Pages

  • Re: 2 networks on sbs
    ... I'm using Cisco switches with Cisco phones, ... <I have one account with one switch for the phones and another switch for ... Another account uses Cisco phones and Cisco switches. ... First, could you tell me what your network topology is, this is very ...
    (microsoft.public.windows.server.sbs)
  • Re: Need guidance on Cisco 6513 install
    ... having this switch set up on Tuesday by noon, ... The switch itself (and other future network hardware) will be on the ... but you can always choose another vlan number and same ... In a two core environment, ...
    (comp.dcom.sys.cisco)
  • Strange results from a tcpdump, can anyone help?
    ... traffic was going ballistic on most ports in the network. ... other hosts went to normal (i.e. the only traffic you could see were ... packets from the same vlan destined to other hosts outside ... If it was simply a bad switch with a bad port that had lost it's mac ...
    (comp.dcom.lans.ethernet)
  • Re: Strange results from a tcpdump, can anyone help?
    ... traffic was going ballistic on most ports in the network. ... other hosts went to normal (i.e. the only traffic you could see were ... packets from the same vlan destined to other hosts outside ... If it was simply a bad switch with a bad port that had lost it's mac ...
    (comp.dcom.lans.ethernet)
  • Re: Help with IGMP
    ... By default it should forward multicast traffic to all port. ... good, it clog the network. ... It switch is has no VLAN or single VLAN and all ... the layer 2 protocol to allow switch interfaces to join multcast streams. ...
    (comp.dcom.sys.cisco)