0

VLAN Tagging

Gregery Armbrust

December 24, 2018 01:19

None

Follow

I have created a VLAN 10 on the Yeastar and also in my netgear switch. In the switch VLAN 10 is set to tagged. In the Yealink phones I have turned on VLAN 10 and put static IP's in each phone to boot to the Yeastar.

The DCHP server in the Yeastar if turned on I believe cant tag traffice that's why  I put statics in the phones. ((At this point I dont have access to the customers router)) 

 

Question are theses packets even being tagged ?

The phones are booting and working on VLAN 10

Another issue because I have the phones now on VLAN 10 set to tagged I cant access there interfaces because my Lap Top cant view tagged traffic.

 

Any suggestions on a better set up

 

System must be VLANed having IP shortage issues

 

Greg  

 

 

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Larry Neblett December 24, 2018 11:30

  How many phones are there? 

  Must be a pretty old PC? You may be able to to dedicate a port on the switch to being a port based Vlan and let the switch tag the packets for you. You can then have the port be a member of multiple vlans and connect the laptop to this port. 

  https://kb.netgear.com/000051460/How-do-I-create-and-manage-port-based-VLANs-on-my-NETGEAR-GS908E-switch

   

  It is not clear to me what the vlan has to do with the lack of available IPs and why same causes the need for a vlan. I assume the real reason for the vlan is more so to use the NG auto vlan function for isolation and QoS. 

   

  You can do a packet capture from the PBX to look at the SIP traffic and then use Wireshark to examine and if it shows something like the below, then it is tagged. Untagged will not show.

   

  

• 0
  
  Gregery Armbrust December 27, 2018 21:02

  Larry, the reason for the VLAN set up is for more IP's the customers 142.77.222.0 network was only allowed IP's from 142.77.222.100 to 142.77.222.120 for computers and phones and there are more devices then IP's allowed by the 3rd party IT department. The IT company wants over $2000.00 from my customer to increase the numbers (and thats crazy) so I set Up Vlans for the phones with static IPS in the range below

  192.168.100.11 to .150

  This way the phones are not using the 142.77.222.100  range of IP's

   

  So far everything is working but

   

  TIME SYNC for handset is not working (manual enter time for now)

  Cant access the IP phones interface at the 192.168.100.0 network even with giving my computer a static in that range I know this has to do with the 192.168.100.0 traffic being tagged

   

   

   

   

• 0
  
  Larry Neblett December 28, 2018 21:40

  Did you set the phones to use the PBX as the NTP server?

   The client needs to look for a new IT company. $2K to make a single entry in the DHCP server is ridiculous and especially so when the current range is reported to be only 21. I also wonder why they elected to use a 142.XXX.XXX.XXX subnet? This is not a recognized range for private IPs.

   In any event, it is not necessary to have a vlan in place to get added IPs. You could add the phones without a vlan and use a different LAN segment and the switches will pass the data fine.  

   

  So, you can either get a new PC or remove the vlan. 

   

   

• 0
  
  Gregery Armbrust January 08, 2019 23:04

  Larry I removed the VLAN's today things seem to be working fine. Thanks again for all the help