Routing

Hi everyone. I am doing some simulations and I have stumbled upon an issue that I can't get around. The problem is that when I configure vlan-tagging (or flexible-vlan-tagging) with a vlan-id on an interface, traffic does not pass (even b/w directly connected vMXs).

For example, if I do the following config on vMX3 and vXM1 which are directly connected, ping to directly connected subnet (other end IP) fails. When I remove the vlan-id and vlan-tagging and just use unit 0, ping works. I want this to work because I am simulating Layer 2 VPNs (pseudowires, VPLS, EVPN). 
 
Has anyone encountered this? Is there a way to get around this? I would be grateful for any help in this matter since my JNCIP-SP studies depend on this. (I don't have a good enough computer to simulate vMXs (or vjunos etc) in GNS3 or eve-NG).

P.S. I posted this on reddit, but apparently no one in the Juniper subreddit knows how to fix this.
Issue with VLANs using Juniper vLABS. : r/Juniper (reddit.com)

[edit interfaces ge-0/0/4]
jcluser@vMX3# show 
vlan-tagging;
unit 610 {
    vlan-id 610;
    family inet {
        address 192.168.10.2/24;
    }
}


[edit interfaces ge-0/0/4]
jcluser@vMX1# show 
vlan-tagging;
unit 610 {
    vlan-id 610;
    family inet {
        address 192.168.10.1/24;
    }
}

Hi Shahbaz,

You will need to change the ethertype used for VLANs as ESXi (used by JCL / vLabs) drops 0x8100. There is an FAQ available here.

I've confirmed this works with vMX_NV and vJunosEVO_NV:

vMX_NV:

jcluser@vMX_NV-A2> show configuration interfaces ge-0/0/3 
vlan-tagging;
gigether-options {
    ethernet-switch-profile {
        tag-protocol-id 0x9100;
    }
}
unit 100 {
    vlan-tags outer 0x9100.100;
    family inet {
        address 192.168.23.2/24;
    }
}

jcluser@vMX_NV-A2> ping 192.168.23.3 source 192.168.23.2 
PING 192.168.23.3 (192.168.23.3): 56 data bytes
64 bytes from 192.168.23.3: icmp_seq=0 ttl=64 time=8.387 ms
64 bytes from 192.168.23.3: icmp_seq=1 ttl=64 time=47.791 ms
64 bytes from 192.168.23.3: icmp_seq=2 ttl=64 time=6.923 ms
^C
--- 192.168.23.3 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 6.923/21.034/47.791/18.930 ms

vJunosEVO_NV:

jcluser@vJunosEVO-NV-A3> show configuration interfaces et-0/0/2 
vlan-tagging;
ether-options {
    ethernet-switch-profile {
        tag-protocol-id 0x9100;
    }
}
unit 100 {
    vlan-tags outer 0x9100.100;
    family inet {
        address 192.168.23.3/24;
    }
}

jcluser@vJunosEVO-NV-A3> ping 192.168.23.2 source 192.168.23.3 
PING 192.168.23.2 (192.168.23.2) from 192.168.23.3 : 56(84) bytes of data.
64 bytes from 192.168.23.2: icmp_seq=1 ttl=64 time=4.27 ms
64 bytes from 192.168.23.2: icmp_seq=2 ttl=64 time=7.43 ms
64 bytes from 192.168.23.2: icmp_seq=3 ttl=64 time=4.85 ms
64 bytes from 192.168.23.2: icmp_seq=4 ttl=64 time=6.36 ms
^C
--- 192.168.23.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.265/5.724/7.425/1.242 ms

[edit interfaces ge-0/0/4]jcluser@vMX3# show vlan-tagging;unit 610 {    vlan-id 610;    family inet {        address 192.168.10.2/24;    }}[edit interfaces ge-0/0/4]jcluser@vMX1# show vlan-tagging;unit 610 {    vlan-id 610;    family inet {        address 192.168.10.1/24;    }}