Junos OS

Expand all | Collapse all

Applying service name table to a demux0 interface

Jump to Best Answer
  • 1.  Applying service name table to a demux0 interface

    Posted 08-30-2019 04:04

    I have an MX5 with subscriber management where clients connect to when dialing out with PPPoE.

    The MX5 has an aggregated ethernet interface, named ae10.

    ae10 consists out of 2 ethernet interfaces towards two different core devices.

    The demux0 and ae10 association is required or otherwise pppoe establishment doesn't work on ae interfaces.

    I'm trying to send delayed PADO responses when clients don't send a service name in the Access-Request packet.

     

    Hoewever, the service name table doesn't seem to do anything. The CPE, without a service-name specified in its pppoe client configuration, does not wait 5 seconds until the pppoe session is established.
    In the Juniper docs, the service table is either configured on ethernet or aggregated ethernet interfaces. It's not possible to do this on demux0 interfaces, while that interface is the underlying interface for pp0 subscribers.

     

    Below is my config. Happy to hear your thoughts.

     

    pppoe {
       service-name-tables dynamic-pppoe-table {
            service empty {
                delay 5;
            }
        }
    }
    
    ae10 {
        flexible-vlan-tagging;
        native-vlan-id 1;
        mtu 9192;
        aggregated-ether-options {
            lacp {
                active;
                periodic fast;
            }
        }
        unit 0 {
            encapsulation ppp-over-ether;
            vlan-id 1;
            pppoe-underlying-options {
                service-name-table dynamic-pppoe-table;
            }
        }
    }
    demux0 {
        unit 150 {
            description "EVPN primairy VLAN";
            vlan-id 150;
            demux-options {
                underlying-interface ae10;
            }
            family pppoe {
                duplicate-protection;
                dynamic-profile PPPoE-PROFILE-PRIMAIR;
            }
        }
        unit 151 {
            description "EVPN secundairy VLAN";
            vlan-id 151;
            demux-options {
                underlying-interface ae10;  
            }
            family pppoe {
                duplicate-protection;
                dynamic-profile PPPoE-PROFILE-SECUNDAIR;
            }
        }
    }


     

    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";
                        }
                        address xx.xx.xx.xx/32;
                    }
                    family inet6 {
                        address xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/128;
                    }
                }
            }
        }
    }

     

     



  • 2.  RE: Applying service name table to a demux0 interface
    Best Answer

     
    Posted 08-31-2019 19:26

    Hi Beeelzebub,

     

    Think you should be able to configure service table under demux0.  Please try to configure it there and check:

    show pppoe service-name-tables <table-name>

     

    interfaces {
    	demux0
    		{
            unit 10000111 {
                description "test";
                vlan-id 11;
                demux-options {
                    underlying-interface ae0;
                }
                family pppoe {
                    duplicate-protection;
                    dynamic-profile PPP-PROFILE-DEFAULT;
                    service-name-table dynamic-pppoe-table;
                }
            }
    	}
    }

    Hope this helps.

     

    Regards,
    -r.

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

    If this solves your problem, please mark this post as "Accepted Solution."
    Kudos are always appreciated :).



  • 3.  RE: Applying service name table to a demux0 interface

    Posted 09-01-2019 05:35

    I swear I tried applying this on the demux0 interface.

    Oh well, free kudos for you 🙂

     

    Thanks!