Hi Folks, I don't know if I'm doing something wrong, or just losing my mind. We've finally (6 week wait) had FTTN connected at home, and as I had it connected through work, I was able to connect it the same way as my ADSL used to be - static IP with /28 routed down it. I wanted to 'simplify' my routing a little though, and instead of doing everything on my main CRS109, and using a VRF for my internal routing (to keep them separated from the DMZ, and make sure the DMZ can't route down the VPN to work, etc), I figured I'd temporarily use one of my mAP's for the internet routing. So connection was VDSL modem (Netcomm NF4V) -> port one on CRS, with ingress/egress VLAN translations to put it on vlan 99. DMZ is on vlan 101, both of which are tagged onto a port going to the mAP-2n. Configured the vlans on the ether1 on the mAP, brought up an IP to test connectivity, and I could ping the private IP of the VDSL modem. But PPPoE connection would not come up, and PPPoE scan showed nothing. Bringing up that vlan on the CRS109, and doing a PPPoE scan showed two AC's. So I then plugged the cable from the VDSL modem directly into ether2 on the mAP. And still nothing on the PPPoE scan. Put the cable back and trunked the vlan across to a routerOS VM. Nothing on PPPoE Scan. Trunked the vlan to the CRS109 in the garage - and PPPoE scan worked from there (although only showed one AC, not two) I've also tried two other VDSL modems (draytek Vigor 130, and TP-Link TD-W8977), with the same results. Have I missed something? is there a limitation in the mAP (and RouterOS for x86 for that matter?) that would stop PPPoE from working? or does PPPoE bridging need some special config on switching/vlans to let it work? Thanks, Damien -- Damien Gardner Jnr VK2TDG. Dip EE. GradIEAust rendrag@rendrag.net - http://www.rendrag.net/ -- We rode on the winds of the rising storm, We ran to the sounds of thunder. We danced among the lightning bolts, and tore the world asunder