Junos OS

I think I'm close to the solution, or perhaps I'm already there and I don't know it yet.

Assigning IPv4 addresses to PPPoE clients works perfectly and now I've given the task to do the same for IPv6.

We want to give every customer IPv6 addresses / connectivity by default.

I'm using FreeRADIUS where the I only use the Framed-IPv6-Prefix attribute, usually a /48. Not sure if it should be a /128.

I don't think I need to use DHCPv6 server and an IPv6 pool under addresses right?

I want to hand out the IPv6 addresses myself from the RADIUS server.

I'm using version 18.4R2.7

Below is my combined v4/v6 dynamic PPPoE profile.

beelze@ams-eq4-ac1# show dynamic-profiles PPPoE-PROFILE-PRIMAIR 
predefined-variable-defaults {
    input-filter police-unlimited;
    output-filter police-unlimited;
}
routing-instances {
    "$junos-routing-instance" {
        interface "$junos-interface-name";
        routing-options {
            access {
                route $junos-framed-route-ip-address-prefix {
                    next-hop "$junos-framed-route-nexthop";
                    preference 4;
                }
            }
            access-internal {
                route $junos-subscriber-ip-address {
                    qualified-next-hop "$junos-interface-name";
                }
            }
        }
    }
}
interfaces {
    pp0 {
        unit "$junos-interface-unit" {
            routing-service {
                enable;
            }
            ppp-options {
                pap;
                authentication [ pap chap ];
                mru 1492;
                mtu 1492;
            }
            pppoe-options {
                underlying-interface "$junos-underlying-interface";
                server;
            }
            keepalives interval 60;
            family inet {
                filter {
                    input "$junos-input-filter";
                    output "$junos-output-filter";
                }
                address aaa.aaa.aaa.aaa/32;
            }
            family inet6 {
                address bbbb:bbbb:bbbb:bbbb:bbbb:bbbb:bbbb:bbbb/128;
            }
        }
    }
}

demux0 {
    unit 150 {
        description "EVPN primairy VLAN";
        routing-service {
            enable;
        }
        vlan-id 150;
        demux-options {
            underlying-interface ae10;
        }
        family pppoe {
            duplicate-protection;
            dynamic-profile PPPoE-PROFILE-PRIMAIR;
        }
    }

beelze@ams-nik-ac1> show route bbbb:bbbb:bbbb::/48 

beelze@ams-nik-ac1> 

And the subscriber logs in and is assigned both a v4 and v6 address.

It seems that it doesn't show an IPv6 Interface Address

marijn@ams-nik-ac1> show subscribers user-name ipv6test extensive 
Type: PPPoE
User Name: ipv6test
IP Address: aaa.aaa.aaa.aaa
IP Netmask: 255.255.255.255
Domain name server inet: DNS 
IPv6 User Prefix: bbbb:bbbb:bbbb::/48
Logical System: default
Routing Instance: default
Interface: pp0.3221246598
Interface type: Dynamic
Underlying Interface: demux0.150
Dynamic Profile Name: PPPoE-PROFILE-PRIMAIR
Dynamic Profile Version: 4
MAC Address: 00:00:00:00:44:44
State: Active
Radius Accounting ID: 65529
Session ID: 65529
PFE Flow ID: 31872
VLAN Id: 150
Login Time: 2019-09-13 13:20:49 CEST
IPv6 Framed Interface Id: 0:0:0:33
IPv4 Input Filter Name: police-unlimited-pp0.3221246598-in
IPv4 Output Filter Name: police-unlimited-pp0.3221246598-out
Dynamic configuration: 
  junos-input-filter: police-unlimited
  junos-output-filter: police-unlimited

However, nothing is shown in the IPv6 routing table:

beelze@ams-nik-ac1> show route 2a01:bb60:cccc::/48

beelze@ams-nik-ac1>

Hello,

Output of "show ppp interface pp0.xxx" and "show interface pp0.xxx extensive" should show you whether CPE tried to negotiate IPv6CP. If CPE negotiated only IPCP, the corresponding IPv6 access-internal route won't be installed:

user@mx> show ppp interface pp0.3221592148
  Session pp0.3221592148, Type: PPP, Phase: Network
    LCP State: Opened
    Authentication: CHAP State: Grant
    IPV6CP State: Opened <===

user@mx> show interfaces pp0.3221592148 extensive
  Logical interface pp0.3221592148 (Index 537247473) (SNMP ifIndex 200376561) (Generation 375956)
    Flags: Up Point-To-Point Encapsulation: PPPoE
    Interface set: ge-4/1/8
    PPPoE:
      State: SessionUp, Session ID: 1,
      Session AC name: mx, Remote MAC address: 00:19:92:d2:c7:c7,
      Underlying interface: ge-4/1/8.7 (Index 681)
      Ignore End-Of-List tag: Disable
    Bandwidth: 0
    Traffic statistics:
    [...]
  Keepalive settings: Interval 30 seconds, Up-count 3, Down-count 3
  LCP state: Opened
  NCP state: inet: Not-configured, inet6: Opened, iso: Not-configured, mpls: Not-configured
  CHAP state: Success
  PAP state: Closed
    Protocol inet6, MTU: 1492 <===
    Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
    Generation: 0, Route table: 0
      Flags: uRPF, Unnumbered
      Donor interface: lo0.0 (Index 323)
      [...]

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Hi Sergii,

Seems like it negotiates for IPv6:

beelze@ams-nik-ac1> show ppp interface pp0.3221246606 
  Session pp0.3221246606, Type: PPP, Phase: Network
    LCP State: Opened
    Authentication: PAP State: Grant
    IPCP State: Opened, IPV6CP State: Opened

beelze@ams-nik-ac1> show ppp interface pp0.3221246606 extensive 
  Session pp0.3221246606, Type: PPP, Phase: Network
   Keepalive settings: Interval 60 seconds, Up-count 1, Down-count 3
               Magic-Number validation: enable
    LCP
      State: Opened
      Last started: 2019-09-13 14:35:19 CEST
      Last completed: 2019-09-13 14:35:19 CEST
      Negotiated options:
        Authentication protocol: pap, Magic number: 1152794964, Initial Advertised MRU: 1492, Local MRU: 1492, Peer MRU: 1480
    Authentication: PAP
      State: Grant
      Last started: 2019-09-13 14:35:19 CEST
      Last completed: 2019-09-13 14:35:19 CEST
    IPCP
      State: Opened
      Last started: 2019-09-13 14:35:20 CEST
      Last completed: 2019-09-13 14:35:20 CEST
      Negotiated options:
        Local address: ggg.ggg.ggg.ggg, Remote address: aaa.aaa.aaa.aaa
      Negotiation mode: Passive
    IPV6CP
      State: Opened
      Last started: 2019-09-13 14:35:20 CEST
      Last completed: 2019-09-13 14:35:20 CEST
      Negotiated options:
        Local interface identifier: 6687:88ff:fe5f:6d80, Remote interface identifier: 0:0:0:33
      Negotiation mode: Passive

The matter is that your CPE can receive the assigned IPv6 prefix either via DHCPv6, or via ND/RA protocols - IPv6CP only negotiates interface-id and allows CPE to use either of these protocols (or both). Please refer:

Dual-Stack Access Models in a PPPoE Network

Best Practices for Configuring IPv4 and IPv6 Dual Stack in a PPPoE Access Network

If you add the following piece to your dynamic profile configuration, it should work (Framed-IPv6-Prefix will be used as NDRA-Prefix):

    protocols {
        router-advertisement {
            interface "$junos-interface-name" {
                other-stateful-configuration;
                link-mtu;
                prefix $junos-ipv6-ndra-prefix {
                    valid-lifetime 14400;
                    on-link;
                    preferred-lifetime 1800;
                }
            }
        }
    }

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Hello sergii,

I added the configuration in the dynamic profile, the prefix is added to the session, but the MX still doesn't have a route to the IPv6 prefix:

beelze@ams-nik-ac1> show subscribers user-name ipv6test extensive 
Type: PPPoE
User Name: ipv6test
IP Address: aaa.aaa.aaa.aaa
IP Netmask: 255.255.255.255
Domain name server inet: dns.dns.dns.dns dns2.dns2.dns2.dns2
IPv6 User Prefix: bbbb:bbbb:bbbb::/48
Logical System: default
Routing Instance: default
Interface: pp0.3221271192
Interface type: Dynamic
Underlying Interface: demux0.150
Dynamic Profile Name: PPPoE-PROFILE-PRIMAIR
Dynamic Profile Version: 9
MAC Address: 00:00:00:00:44:44
State: Active
Radius Accounting ID: 89143
Session ID: 89143
PFE Flow ID: 60546
VLAN Id: 150
Login Time: 2019-09-17 11:06:10 CEST
IPv6 Framed Interface Id: 0:0:0:33
IPv4 Input Filter Name: police-unlimited-pp0.3221271192-in
IPv4 Output Filter Name: police-unlimited-pp0.3221271192-out
Dynamic configuration: 
  junos-ipv6-ndra-prefix: bbbb:bbbb:bbbb::/48

beelze@ams-nik-ac1> show route bbbb:bbbb:bbbb::/48 

beelze@ams-nik-ac1> 

CPE needs to request this address. Can you please check:

root@mx1> show ipv6 router-advertisement
Interface: pp0.3221225487
  Advertisements sent: 541, last sent 0:00:50 ago
  Solicits received: 1, last received 90:01:00 ago <===
  Advertisements received: 0

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Also your dynamic profile includes the same prefix - can you please change it to something else?

family inet6 {
                address bbbb:bbbb:bbbb:bbbb:bbbb:bbbb:bbbb:bbbb/128;
            }

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

I inserted a different /48 prefix in the radius server.

Also, I changed the family inet6 address to:

family inet6 {
    address $junos-ipv6-address;
 }

beelze@ams-nik-ac1# run show subscribers user-name ipv6test extensive    
Type: PPPoE
User Name: ipv6test
IP Address: 185.217.211.88
IP Netmask: 255.255.255.255
Domain name server inet: 185.52.208.18 185.52.208.26 
IPv6 User Prefix: 2a0b:9b41:967::/48
Logical System: default
Routing Instance: default
Interface: pp0.3221271286
Interface type: Dynamic
Underlying Interface: demux0.150
Dynamic Profile Name: PPPoE-PROFILE-PRIMAIR
Dynamic Profile Version: 13
MAC Address: 00:00:00:00:44:44
State: Active
Radius Accounting ID: 93003
Session ID: 93003
PFE Flow ID: 60652
VLAN Id: 150
Login Time: 2019-09-17 12:09:55 CEST
IPv6 Interface Address: 2a0b:9b41:967::1/48
IPv6 Framed Interface Id: 0:0:0:33
IPv4 Input Filter Name: police-unlimited-pp0.3221271286-in
IPv4 Output Filter Name: police-unlimited-pp0.3221271286-out
Dynamic configuration: 
  junos-input-filter: police-unlimited
  junos-ipv6-ndra-prefix: 2a0b:9b41:967::/48
  junos-output-filter: police-unlimited

beelze@ams-nik-ac1# run show ipv6 router-advertisement

- output is empty

I'm testing on 18.4R2.7.

I've got a working session on 14.2R7-S9 where I am not using IPv6 NDRA.

The only IPv6 reference I see in a profile on that router is:

interfaces {
        pp0 {
            unit "$junos-interface-unit" {            
                family inet6 {
                    address $junos-ipv6-address;
                }
           }
      }
 }

Its subscriber:

beelze@ams-nik-er2# run show subscribers user-name ipv6test extensive    

Type: PPPoE

User Name:ipv6test

IP Address: 185.201.201.56

IP Netmask: 255.255.255.255

IPv6 User Prefix: 2a0b:9b41:966::/48

Logical System: default

Routing Instance: default

Interface: pp0.1073791164

Interface type: Dynamic

Underlying Interface: xe-1/3/0.473

Dynamic Profile Name: PPPoE-PROFILE

Dynamic Profile Version: 5

MAC Address: mac

State: Active

Radius Accounting ID: 52773322

Session ID: 52773322

VLAN Id: 473

Login Time: 2019-05-13 14:54:40 CEST

IPv6 Interface Address: 2a0b:9b41:966::1/48

IPv6 Framed Interface Id: 0:0:0:e

IPv4 Input Filter Name: police-unlimited-pp0.1073791164-in

IPv4 Output Filter Name: police-unlimited-pp0.1073791164-out

beelze@ams-nik-er2# run show route 2a0b:9b41:966::/48

inet6.0: 104 destinations, 150 routes (104 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

2a0b:9b41:966::/48 *[Direct/0] 18w0d 21:31:12

                    > via pp0.1073791164

2a0b:9b41:966::1/128

                   *[Local/0] 18w0d 21:31:12

                      Local via pp0.1073791164

Can you please provide the output of the following command (for your subscriber id is 93003):

root@mx> show dynamic-profile session client-id 17
dp-pppoe {
    routing-instances {
        default {
            interface pp0.3221225487;
        }
    }
    interfaces {
        pp0 {
            unit 3221225487 {
                no-traps;
                ppp-options {
                    chap;
                    pap;
                }
                pppoe-options {
                    underlying-interface demux0.3221225486;
                    server;
                }
                keepalives interval 30;
                family {
                    inet {
                        unnumbered-address lo0.0;
                    }
                    inet6 {
                        unnumbered-address lo0.0;
                    }
                }
            }
        }
    }
    protocols {
        router-advertisement {
            interface pp0.3221225487 {
                other-stateful-configuration;
                link-mtu;
                prefix 2001:db8:a000:ff::/64 {
                    valid-lifetime 14400;
                    on-link;
                    preferred-lifetime 1800;
                }
            }
        }
    }
}

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Also you should use the following lines in your dynamic profile:

                family inet6 {
                    unnumbered-address "$junos-loopback-interface";
                }

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

beelze@ams-nik-ac1> show dynamic-profile session client-id 93006     
PPPoE-PROFILE-PRIMAIR {
    predefined-variable-defaults {
        input-filter {
            police-unlimited;
        }
        output-filter {
            police-unlimited;
        }
    }
    routing-instances {
        default {
            interface pp0.3221271289;
            routing-options {
                rib inet6.0 {
                    access {
                        route NONE {
                            next-hop NONE;
                            preference 4;
                        }
                    }
                }
                access {
                    route NONE {
                        next-hop NONE;
                        preference 4;
                    }
                }
                access-internal {
                    route 185.217.211.88/32 {
                        qualified-next-hop pp0.3221271289;
                    }
                }
            }
        }
    }
    interfaces {
        pp0 {
            unit 3221271289 {
                routing-service {
                    enable;
                }
                ppp-options {
                    pap;
                    authentication pap;
                    authentication chap;
                    mru 1492;
                    mtu 1492;
                }
                pppoe-options {
                    underlying-interface demux0.150;
                    server;
                }
                keepalives interval 60;
                family {
                    inet {
                        filter {
                            input police-unlimited;
                            output police-unlimited;
                        }
                        address 185.52.208.150/32;
                    }
                    inet6 {
                        unnumbered-address lo0.0;
                    }
                }
            }
        }
    }                                   
    protocols {
        router-advertisement {
            interface pp0.3221271289 {
                other-stateful-configuration;
                link-mtu;
                prefix 2a0b:9b41:967::/48 {
                    valid-lifetime 14400;
                    on-link;
                    preferred-lifetime 1800;
                }
            }
        }
    }
}

It seems like nothing gets installed in the IPv6 routing table. 

Downgraded to version 14.2R7-S9.

CPE can for example ping/trace google name server 2001:4860:4860::8888.

Default route on CPE: ::/0 to PPPoE interface.

Once I upgrade to 18.4R2.7 (don't want to use 14.2 because it is unsupported), I don't see the same behaviour.

Maybe this will help troubleshooting everything further.

Used FreeRADIUS attribute Framed-IPv6-Prefix 2a0b:9b41:967::/48.

Used the following configuration to get a working IPv6 connection from a client:

beelze@ams-nik-ac1# show interfaces demux0 
unit 150 {
    description "EVPN primairy VLAN";
    vlan-id 150;
    demux-options {
        underlying-interface ae10;
    }
    family pppoe {
        duplicate-protection;
        dynamic-profile PPPoE-PROFILE-PRIMAIR;
    }
}

beelze@ams-nik-ac1# show interfaces ae10 
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
aggregated-ether-options {
    lacp {
        active;
        periodic fast;
    }
}

beelze@ams-nik-ac1# show dynamic-profiles PPPoE-PROFILE-PRIMAIR 
predefined-variable-defaults {
    input-filter police-unlimited;
    output-filter police-unlimited;
}
routing-instances {
    "$junos-routing-instance" {
        interface "$junos-interface-name";
        routing-options {
            access {
                route $junos-framed-route-ip-address-prefix {
                    next-hop "$junos-framed-route-nexthop";
                    preference 4;
                }
            }
            access-internal {
                route $junos-subscriber-ip-address {
                    qualified-next-hop "$junos-interface-name";
                }
            }
        }
    }
}
interfaces {
    pp0 {
        unit "$junos-interface-unit" {
            ppp-options {
                pap;
                authentication [ pap chap ];
                mru 1492;
                mtu 1492;
            }
            pppoe-options {
                underlying-interface "$junos-underlying-interface";
                server;
            }
            keepalives interval 60;
            family inet {
                filter {
                    input "$junos-input-filter";
                    output "$junos-output-filter";
                }
                unnumbered-address "$junos-loopback-interface";
            }
            family inet6 {
                address $junos-ipv6-address;
            }
        }
    }
}

The subscriber:

beelze@ams-nik-ac1> show subscribers user-name ipv6test extensive 
Type: PPPoE
User Name: ipv6test
IP Address: 185.217.211.88
IP Netmask: 255.255.255.255
IPv6 User Prefix: 2a0b:9b41:967::/48
Logical System: default
Routing Instance: default
Interface: pp0.1073741827
Interface type: Dynamic
Underlying Interface: demux0.150
Dynamic Profile Name: PPPoE-PROFILE-PRIMAIR
Dynamic Profile Version: 2
MAC Address: 00:00:00:00:20:00
State: Active
Radius Accounting ID: 4
Session ID: 4
VLAN Id: 150
Login Time: 2019-09-18 11:40:17 CEST
IPv6 Interface Address: 2a0b:9b41:967::1/48
IPv6 Framed Interface Id: 0:0:0:7de
IPv4 Input Filter Name: police-unlimited-pp0.1073741827-in
IPv4 Output Filter Name: police-unlimited-pp0.1073741827-out

IPv6 routes:

beelze@ams-nik-ac1> show route 2a0b:9b41:967::/48   

inet6.0: 55 destinations, 103 routes (55 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2a0b:9b41:967::/48 *[Direct/0] 00:10:53
                    > via pp0.1073741827
2a0b:9b41:967::1/128
                   *[Local/0] 00:10:53
                      Local via pp0.1073741827

Interface address on BNG:

beelze@ams-nik-ac1> show dynamic-profile session client-id 4  
PPPoE-PROFILE-PRIMAIR {
    predefined-variable-defaults {
        input-filter {
            police-unlimited;
        }
        output-filter {
            police-unlimited;
        }
    }
    routing-instances {
        default {
            interface pp0.1073741827;
            routing-options {
                access {
                    route NONE {
                        next-hop NONE;
                        preference 4;
                    }
                }
                access-internal {
                    route 185.217.211.88/32 {
                        qualified-next-hop pp0.1073741827;
                    }
                }
            }
        }
    }
    interfaces {
        pp0 {
            unit 1073741827 {
                ppp-options {
                    pap;
                    authentication pap;
                    authentication chap;
                    mru 1492;
                    mtu 1492;
                }
                pppoe-options {
                    underlying-interface demux0.150;
                    server;
                }
                keepalives interval 60;
                family {
                    inet {
                        filter {
                            input police-unlimited;
                            output police-unlimited;
                        }
                        unnumbered-address lo0.0;
                    }
                    inet6 {
                        address 2a0b:9b41:967::1/48; <<---
                    }
                }
            }
        }
    }
}

I got it working, not sure why, but here is my working Dual Stack PPPoE profile:

predefined-variable-defaults {
    input-filter police-unlimited;
    output-filter police-unlimited;
}
routing-instances {
    "$junos-routing-instance" {
        interface "$junos-interface-name";
        routing-options {
            access {
                route $junos-framed-route-ip-address-prefix {
                    next-hop "$junos-framed-route-nexthop";
                    preference 4;
                }
            }
            access-internal {
                route $junos-subscriber-ip-address {
                    qualified-next-hop "$junos-interface-name";
                }
            }
        }
    }
}
interfaces {
    pp0 {
        unit "$junos-interface-unit" {
            ppp-options {
                pap;
                authentication [ pap chap ];
                mru 1492;
                mtu 1492;
            }
            pppoe-options {
                underlying-interface "$junos-underlying-interface";
                server;
            }
            keepalives interval 60;
            family inet {
                filter {
                    input "$junos-input-filter";
                    output "$junos-output-filter";
                }
                address 185.52.208.150/32;
            }
            family inet6 {
                address $junos-ipv6-address;
            }
        }
    }
}
protocols {
    router-advertisement {
        interface "$junos-interface-name" {
            managed-configuration;
            other-stateful-configuration;
            link-mtu;
            prefix $junos-ipv6-ndra-prefix;
        }
    }
}

I found the issue, the following command fixed it:

"deactivate dynamic-profiles PPPoE-PROFILE-PRIMAIR interface pp0 unit $junos-interface unit routing-service" which was enabled.

This statement is required to be able to use BGP over PPPoE IPv4.

My network requires both that and IPv6 connectivity. How would I solve this?

Hi,

Yes, I think it was the only significant difference between your current and previous configuration for 18.4R2. However, it's not quite obvious why NDRA doesn't work when routing-services are enabled (smells like a bug to me). The only other option I see is to try to assign IPv6 address via DHCPv6 - hopefully your CPE supports it.

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Hello Beeelzebub,

I've got confirmation that NDRA should work regardless of the presence of "routing-service" knob, which means that the observed behavior is a bug. I'll try to file a PR this or next week. Having a JTAC case would help to get it resolved faster (and to get into one of the service releases).

In the meanwhile, have you had a chance to check if your CPE supports address assignment via DHCPv6?

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Hey Sergii,

That's somewhat comforting knowing that it's most likely a bug and not the MX's / client configuration.

I have opened a JTAC case for getting IPv6 NDRA to work and found out later that the only difference was indeed the presence of the routing-service knob.

I will tell the JTAC engineer if this can be resolved in the next service releases.

Would it help to test this with version 19.1R1 and 19.2R2?

I've taken a look in the Release Notes, but could not found something that points to a fix.

We will probably have to use a very old version (14.2R7-S9, we are using this version in production right now), but knowing that it's an unsupported release doesn't help much in the future.

We do need BGP over PPPoE IPv4 (and also IPv6 very soon).

Regarding DHCPv6, I still haven't found time to look at that since I have tried to find a solution not knowing it's a bug.

Hello Beeelzebub,

I briefly searched for a PR and didn't find any - it shouldn't mean that there is no chance that the issue was fixed by via a PR that I haven't found, but my expectation is that this issue is not fixed in any JUNOS releases yet. Of course, you can test 19.x and get 100% reliable information whether the issue is still present there or not.

If the issue is still present in 19.x, please inform your JTAC engineer - it should help him to create a new PR faster.

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

This issue has not been fixed in release 19.x.

It might not be 100% related to BGP, because of the following..

The thing is, the CPE is unable to ping its peer IP / gateway IP address when the "routing-service enable" knob is configured.

The traceroute goes like this: starts at CPE --> loopback address AC --> next hop / core router.

When the "routing-service enable" knob is deactivated, then the traceroute shows only 1 hop, the peer IP / gateway IP address.

Not sure how this will help solving it, but maybe there is a work-around for this on this version?

I'm in contact with a JTAC engineer and he's testing it on an MX40.

He might thing it's related to https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1444696 on PPC based platforms (MX5,10,40,80.104).

Hello Beeelzebub,

PR1444696 (an issue with code responsible for keepalive processing on PFE) can't be related to BGP or ping issue. In any case, this discussion is straying away (and it's not clear what is not working in your last message). It should be easy to keep discussion straight to the point (e.g. to discuss one problem at a time). In this case the conclusion should be the following:

NDRA for a dual-stack PPPoE subscriber doesn't work if dynamic-profile includes "routing-services" knob (PR#, fixed in, etc.)

It would be clearer if you could create a new thread, mention all conditions (e.g. dynamic profile with or without routing-services, etc.), and provide all relevant outputs there. By the way, for BGP over PPPoE to work, if I'm not mistaken, you're required to configure multihop BGP with ttl 2.

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

FYI: PR 1464415 has been filed a couple of days ago and I got confirmation by JTAC that the NDRA + "routing-service enable" knob fix will be released in version 18.4R2-S2 (by the end of november 2019) and 18.4R3.

Thank you for updating this thread! Can you please also mark one of posts as the accepted solution, to complete this discussion?

Best regards,

Sergii

-------------------------------------------------------------------

Please accept the solution if your problem is resolved

-------------------------------------------------------------------

Yes, I just did!

Thanks for the support.