Thanks Sergii and rnayar for replying.
Version is 14.2R7-S9 btw.
I'm aware of the Virtual-Router VSA, my dictionary forces me to use it as ERX-Virtual-Router-Name (VSA 26-1).
The contents of this attribute is always logical-instance:routing-instance, so mostly default:routing-instance.
In the logging I see this attribute in my access-accept packet I get back from the radius server.
"routing-instance" is an existing routing instance.
May 7 14:22:23.904 radius-access-accept: Framed-IP-Address received: 10.0.100.3
May 7 14:22:23.904 radius-access-accept: Framed-IP-Netmask received: 255.255.255.255
May 7 14:22:23.904 radius-access-accept: Virtual-Router (Juniper-ERX-VSA) received: default:routing-instance
May 7 14:22:23.905 radius-access-accept: Ingress-Policy-Name (Juniper-ERX-VSA) received: police-unlimited
May 7 14:22:23.905 radius-access-accept: Egress-Policy-Name (Juniper-ERX-VSA) received: police-unlimited
Regarding the unnumbered IP, we're working towards a setup where all subscribers get the same gateway IP address with their PPPoE session. This works fine for us.
And at last:
user@core-ixn-be-01> show services l2tp tunnel extensive
Waiting for statistics...
Tunnel local ID: 18521, Tunnel remote ID: 18323
Remote IP: xx.xx.xx.xx:1701
Sessions: 4, State: Established
Tunnel Name: 1/2
Local IP: yy.yy.yy.yy:1701
Local name: core-ixn-be-01, Remote name: remote
Effective Peer Resync Mechanism: silent failover
Nas Port Method: none
Tunnel Logical System: default, Tunnel Routing Instance: default
Max sessions: 128100, Window size: 1024, Hello interval: 60
Create time: Tue Mar 5 03:30:14 2019, Up time: 063 days,10:01:46
Idle time: 00:00:00, ToS Reflect: Disabled
Interface Name: si-1/0/0, Tunnel Group Name: L2TP-TG
Statistics since: Tue Mar 5 03:30:14 2019
Packets Bytes
Control Tx 96.3k 1328.7k
Control Rx 100.8k 2411.8k
Data Tx 136.6M 69848.1M
Data Rx 124.8M 20966.7M
Errors Tx 0
Errors Rx 3