Vlan tagging/trunk, L2 required???

I have a wireless AP that I'm trying to tag and trunk. I'm in a pure L3 setup for the SRX. The AP is an Asus RT-AC68U with dd-wrt on it. I have tried trunk/tagging it with these two configs.

ge-0/0/14 {
flexible-vlan-tagging;
encapsulation vlan-vpls;
unit 0 {
arp-resp;
vlan-id 0;
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
unit 1 {
arp-resp;
vlan-id 1;
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
unit 2 {
arp-resp;
vlan-id 2;
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}

This first config passes the traffic but of course vlan2 has no communication. My setup consists of vlan-trust and an unsuccessful use of vlan2. In the first config the vlan2 traffic passes but won't communicate with vlan2 on the SRX. The internet connects on this config. Vlan-trust does it's job for all three vlans on the AP. Vlan 0, 1 and 2 .

The next config doesn't work at all.

ge-0/0/15 {
unit 0 {
arp-resp;
family ethernet-switching {
port-mode trunk;
vlan {
members [ vlan-trust vlan2 ];
}
}
}
}

It gets no communication. I know that the Asus AP will trunk and tag properly because I have tried it on an Avaya ers switch. On that switch/stack it is vlan1 and vlan2. On the SRX it is vlan-trust which is made up of vlan default and vlan.0 . Which are vlan0, vlan1 tagged as vlan-id 3. The ers stack is in router mode which makes it L3.

Do I still need to do something else?

How can I simulate the use of vlan1 and vlan2 properly. The SRX doesn't want to talk. I know that vlan2 on the SRX will go in the up position.