Junos OS

Expand all | Collapse all

MLPPP not passing data

Jump to Best Answer
  • 1.  MLPPP not passing data

     
    Posted 01-10-2020 05:00

    Hi

     

    I have the following, very basic, topology:

     

    Mikrotik -- vMX

     

    I am configuring MLPPP between the vMX and the MikroTik. Here are the session details:

    root> show subscribers
    Interface                   IP Address/VLAN ID                               User Name                               LS:RI
    pp0.3221225473           192.168.1.2                                    MLPPP_Test                        default:default

     

    So, the session comes up but I am unable to ping from the vMX to the MikroTik.

     

    Here is the config on the vMX:

    set version 18.2R1.9
    set system configuration-database resize
    set system configuration-database max-db-size 314572800
    set system root-authentication encrypted-password "$6$jvgGZ2tZ$QB5UMb5x2VmVz.T9uRbv1PT8uWVXcHEmTZpBG.BKukMp94JhOpfKSP/Tm.MTNVmjzwer6yHhQ0hU9T2Q5dT6y."
    set system management-instance
    set system services subscriber-management enable
    set system syslog user * any emergency
    set system syslog file messages any notice
    set system syslog file messages authorization info
    set system syslog file interactive-commands interactive-commands any
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" ppp-options pap
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" pppoe-options underlying-interface "$junos-underlying-interface"
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" pppoe-options server
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family inet
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp bundle "$junos-bundle-interface-name"
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp service-interface si-0/0/0
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp dynamic-profile ml-bundle-prof
    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix next-hop "$junos-framed-route-nexthop"
    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix metric "$junos-framed-route-cost"
    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix preference "$junos-framed-route-distance"
    set dynamic-profiles ml-pp0-member-prof routing-options access-internal route $junos-subscriber-ip-address qualified-next-hop "$junos-interface-name"
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" encapsulation multilink-ppp
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" mrru 1500
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" short-sequence
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" fragment-threshold 320
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family inet unnumbered-address lo0.0
    set chassis fpc 0 pic 0 inline-services bandwidth 1g
    set chassis network-services enhanced-ip
    set access-profile no-auth
    set interfaces ge-0/0/0 unit 0 family pppoe dynamic-profile ml-pp0-member-prof
    set interfaces si-0/0/0 encapsulation generic-services
    set interfaces si-0/0/0 unit 0 family inet
    set interfaces xe-0/0/0 unit 0
    set interfaces fxp0 unit 0 family inet dhcp vendor-id Juniper-vmx-VM5E1773C2E2
    set interfaces lo0 unit 0 family inet address 192.168.1.1/32
    set access profile no-auth authentication-order none
    set access address-assignment pool pool1 family inet network 192.168.1.0/24

     

    Here are the results of the test ping from the vMX to the MikroTik assigned address:

    ping: sendto: No route to host
    ping: sendto: No route to host
    ping: sendto: No route to host
    ping: sendto: No route to host

     

    Also, it seems that the address is incrementing by 1 every 5 minutes or so.... so it starts by giving out .2 then 5 minutes later it becomes .3 then .4 etc etc

     

    Here is the very basic config on the MikroTik:

    /interface pppoe-client
    add allow=pap disabled=no interface=ether1 max-mru=1500 max-mtu=1492 name=pppoe-out1 password=password123 user=MLPPP_Test
    /interface wireless security-profiles
    set [ find default=yes ] supplicant-identity=MikroTik
    /ip hotspot profile
    set [ find default=yes ] html-directory=flash/hotspot
    /ip dhcp-client
    add disabled=no interface=ether2

     

    Any help appreciated please

     

     

     



  • 2.  RE: MLPPP not passing data

     
    Posted 01-10-2020 06:42

    Hello,

     

    Just a guess - could you please try moving the following part of your configuration from ml-pp0-member-prof to ml-bundle-prof dynamic profile and see if it changes anything?

    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix next-hop "$junos-framed-route-nexthop"
    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix metric "$junos-framed-route-cost"
    set dynamic-profiles ml-pp0-member-prof routing-options access route $junos-framed-route-ip-address-prefix preference "$junos-framed-route-distance"
    set dynamic-profiles ml-pp0-member-prof routing-options access-internal route $junos-subscriber-ip-address qualified-next-hop "$junos-interface-name"

    Best regards,

    Sergii

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

    Please accept the solution if your problem is resolved Smiley Happy

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



  • 3.  RE: MLPPP not passing data

    Posted 01-10-2020 07:28

    You seem to have missed out the VLAN and PPOE parts of this on the interfaces as well as the CoS parts and defining the Bundle initially. These are given in the example configs here - https://www.juniper.net/documentation/en_US/junos/topics/example/mlppp-dynamic-pppoe-subscribers-configuring.html

     

    KR Adam



  • 4.  RE: MLPPP not passing data

     
    Posted 01-11-2020 11:14

    I tried moving the sections as shown but it has made no difference.

     

    The starnge thing is that I have this exact same configuration in the lab and it works, well, the MLPPP comes up and it remains stable.

     

    The main problem I have here with testing anything is that the MLPPP comes up, then drops and comes up again with the next address in the pool. Because this is happening I have no route (Private/unicast) in the routing table to the MikroTik and therefore cannot test the passing of traffic.

     

    It would be great to get this stable on my home Lab before travelling back to the office where I can access physical equipment.

     

    I will configure up a VLAN etc as per the docs but as this was working in the Lab at the offices I find it strange that the exact same config will not work at home....



  • 5.  RE: MLPPP not passing data

     
    Posted 01-11-2020 12:37

    The VLAN made no difference. It is still doing the following:

     

    MLPPP Session established: IP Address assigned 192.168.1.2

    After 1 minute or so, MLPPP Session torn down:

    MLPPP Session established: IP Address assigned 192.168.1.3

    After 1 minute or so, MLPPP Session torn down:

    MLPPP Session established: IP Address assigned 192.168.1.4

     

    As can be seen, it just keeps re-cycling and adding the next address in the subnet. No routes in the routing table, only lo0.

     

    This is what is shown in the pppoed file when the following is completed:

    tail -f pppoed

    Jan 11 20:24:08.800964 Pppoe::filterMajorInterface discarding demux0.2147483654
    Jan 11 20:26:15.733992 updateMajorDevice: ge-0/0/0
    Jan 11 20:26:15.734011 ge-0/0/0: changed=0 flags=c000
    Jan 11 20:26:15.734015 updateMajorDevice:MTU : 1514
    Jan 11 20:26:15.734021 removeMajorInterface: UIFL not found: demux0.2147483654
    Jan 11 20:26:21.685379 Pppoe::filterMajorInterface discarding demux0.2147483655
    Jan 11 20:26:21.685402 updateMajorDevice: ge-0/0/0
    Jan 11 20:26:21.685408 ge-0/0/0: changed=0 flags=c000
    Jan 11 20:26:21.685411 updateMajorDevice:MTU : 1514
    Jan 11 20:26:21.704229 Pppoe::filterMajorInterface discarding demux0.2147483655
    Jan 11 20:28:25.930336 updateMajorDevice: ge-0/0/0
    Jan 11 20:28:25.930358 ge-0/0/0: changed=0 flags=c000
    Jan 11 20:28:25.930362 updateMajorDevice:MTU : 1514
    Jan 11 20:28:25.930386 removeMajorInterface: UIFL not found: demux0.2147483655

     

    pppd log shows the following:

    tail -f pppd

    Jan 11 20:37:56 pppd_config_read_access
    Jan 11 20:37:56 pppd_config_read_access_radius_servers
    Jan 11 20:37:56 pppd_config_read_access_profiles
    Jan 11 20:37:56 Reading profile: no-auth
    Jan 11 20:37:56 pppd_config_read_access_profiles_profile
    Jan 11 20:37:56 pppd_config_read_clients
    Jan 11 20:37:56 pppd_config_read_auth_order
    Jan 11 20:37:56 pppd_config_read_profile_radius_servers
    Jan 11 20:37:56 pppd_config_read_system_radius_servers
    Jan 11 20:37:56 === Configuration reload succeeded ===
    Jan 11 20:39:18 op delete ifa demux0.-2147483636 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:18 op delete iff demux0.-2147483636 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:18 op delete ifa demux0.-2147483636 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:18 op change ifd ge-0/0/0 devidx 148 flags c000
    Jan 11 20:39:18 op change ifd ge-0/0/0 devidx 148 (skipped)
    Jan 11 20:39:18 op delete iff demux0.-2147483636 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:18 op delete ifl demux0.-2147483636 idx 334 devindex 128 flags 0
    Jan 11 20:39:18 op delete ifl demux0.-2147483636 idx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op add ifl demux0.-2147483635 idx 334 devindex 128 flags 0
    Jan 11 20:39:22 op add ifl demux0.-2147483635 idx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op change ifd ge-0/0/0 devidx 148 flags c000
    Jan 11 20:39:22 op change ifd ge-0/0/0 devidx 148 (skipped)
    Jan 11 20:39:22 op add iff demux0.-2147483635 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op add ifa demux0.-2147483635 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op add iff demux0.-2147483635 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op add ifa demux0.-2147483635 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:39:22 op change ifl demux0.-2147483635 idx 334 devindex 128 flags 0
    Jan 11 20:39:22 op change ifl demux0.-2147483635 idx 334 devindex 128 (skipped)
    Jan 11 20:41:29 op delete ifa demux0.-2147483635 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:41:29 op delete iff demux0.-2147483635 af inet iflidx 334 devindex 128 (skipped)
    Jan 11 20:41:29 op delete ifa demux0.-2147483635 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:41:29 op change ifd ge-0/0/0 devidx 148 flags c000
    Jan 11 20:41:29 op change ifd ge-0/0/0 devidx 148 (skipped)
    Jan 11 20:41:29 op delete iff demux0.-2147483635 af inet6 iflidx 334 devindex 128 (skipped)
    Jan 11 20:41:29 op delete ifl demux0.-2147483635 idx 334 devindex 128 flags 0
    Jan 11 20:41:29 op delete ifl demux0.-2147483635 idx 334 devindex 128 (skipped)
    Jan 11 20:41:32 op add ifl demux0.-2147483634 idx 334 devindex 128 flags 0
    Jan 11 20:41:32 op add ifl demux0.-2147483634 idx 334 devindex 128 (skipped)
    Jan 11 20:41:32 op change ifd ge-0/0/0 devidx 148 flags c000
    Jan 11 20:41:32 op change ifd ge-0/0/0 devidx 148 (skipped)

     

    Not sure what else I can monitor or try....

     



  • 6.  RE: MLPPP not passing data

     
    Posted 01-12-2020 06:37

    Okay.

     

    I have successfully got the MLPPP session to come up as can be seen below as I now have the pp0 and the si-0/0/0 interfaces showing for the subscriber:

     

    Interface                              IP Address/VLAN ID                   User Name                        LS:RI
    pp0.3221225971                   192.20.14.233                        MLPPP_Test             default:default
    si-0/0/0.3221225972           192.20.14.233                        MLPPP_Test             default:default

     

    And the address now appears in the routing table, as shown below:

     

    192.20.14.233/32 *[Access-internal/12] 00:02:52
    Private unicast

     

    Okay. So, now I have the last issue to resolve. If this were a normal pppoe connection, I can ping the client directly from the vMX with no external requirements (as it takes the loopback address).

     

    However, if I try and ping from the vMX to the client with no external addressing (same as pppoe using loopback) I get the following:

     

    root# run ping 192.20.14.233
    PING 192.20.14.233 (172.20.14.233): 56 data bytes

     

    And no response. Any ideas why? Should I configure an external address to see if this works with some static routes in place?

     

    I configured an external address on a secondary vMX and still nothing.

     



  • 7.  RE: MLPPP not passing data

     
    Posted 01-12-2020 11:14

    Some more information regarding this, I have now configured the vMX with the following (Including VLAN and routing-instance):

    set version 18.2R1.9
    set system configuration-database resize
    set system configuration-database max-db-size 314572800
    set system root-authentication encrypted-password "$6$DiFLAC1o$emUGgK9COurhUASB8n/gCUmjLwP8wnngS/YnC5JYIQTEpJGRE6aNnVDmp8ZPSGes0ZS9yKsUgt.9A/tjvWfAJ."
    set system management-instance
    set system services subscriber-management enable
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" ppp-options pap
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" pppoe-options underlying-interface "$junos-underlying-interface"
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" pppoe-options server
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family inet
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp bundle "$junos-bundle-interface-name"
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp service-interface si-0/0/0
    set dynamic-profiles ml-pp0-member-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family mlppp dynamic-profile ml-bundle-prof
    set dynamic-profiles ml-bundle-prof routing-instances "$junos-routing-instance" routing-options access route $junos-framed-route-ip-address-prefix next-hop "$junos-framed-route-nexthop"
    set dynamic-profiles ml-bundle-prof routing-instances "$junos-routing-instance" routing-options access route $junos-framed-route-ip-address-prefix metric "$junos-framed-route-cost"
    set dynamic-profiles ml-bundle-prof routing-instances "$junos-routing-instance" routing-options access route $junos-framed-route-ip-address-prefix preference "$junos-framed-route-distance"
    set dynamic-profiles ml-bundle-prof routing-instances "$junos-routing-instance" routing-options access route $junos-framed-route-ip-address-prefix tag "$junos-framed-route-tag"
    set dynamic-profiles ml-bundle-prof routing-instances "$junos-routing-instance" routing-options access-internal route $junos-subscriber-ip-address qualified-next-hop "$junos-interface-nam"
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" encapsulation multilink-ppp
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" mrru 1500
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" short-sequence
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" fragment-threshold 320
    set dynamic-profiles ml-bundle-prof interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family inet unnumbered-address lo0.0
    set chassis fpc 0 pic 0 inline-services bandwidth 1g
    set chassis network-services enhanced-ip
    set access-profile no-auth
    set interfaces ge-0/0/0 flexible-vlan-tagging
    set interfaces ge-0/0/0 unit 600 encapsulation ppp-over-ether
    set interfaces ge-0/0/0 unit 600 vlan-id 600
    set interfaces ge-0/0/0 unit 600 pppoe-underlying-options dynamic-profile ml-pp0-member-prof
    set interfaces si-0/0/0 encapsulation generic-services
    set interfaces si-0/0/0 unit 0 family inet
    set interfaces ge-0/0/1 unit 0 family inet address 192.168.1.2/30
    set interfaces ge-0/0/2 unit 0 family inet address 192.168.2.1/24
    set interfaces fxp0 unit 0 family inet dhcp vendor-id Juniper-vmx-VM5E1773C2E2
    set interfaces lo0 unit 0 family inet address 172.20.14.1/32
    set routing-options static route 0.0.0.0/0 next-hop 192.168.1.1
    set protocols ppp traceoptions level all
    set protocols ppp traceoptions flag all
    set protocols pppoe traceoptions level all
    set protocols pppoe traceoptions flag all
    set access profile no-auth authentication-order none
    set access address-assignment pool pool1 family inet network 172.20.14.0/24

     

    The other ge interfaces (other than ge-0/0/0.600) were configured as external test, that is all....

     

    The MikroTik is now configured for VLAN 600 and the route is in the routing table on both devices. Again, the MLPPP bundle comes up but is not passing traffic.... so the connectivity itself is good, there is something else stopping it, but no log files are giving me any information:

    root# run show subscribers
    Interface                                  IP Address/VLAN ID                User Name                          LS:RI
    pp0.3221225484                  172.20.14.7                              MLPPP_Test                   default:default
    si-0/0/0.3221225485          172.20.14.7                              MLPPP_Test                   default:default

     

    But as I mentioned, I still cannot ping the MikroTik from the vMX nor the vMX from the Mikrotik. very frustrating



  • 8.  RE: MLPPP not passing data

     
    Posted 01-13-2020 10:51

    Another add on to this.

     

    When I connect a second port on the same VLAN I am seeing a second pp0 interface and a second si-interface.... this does not seem correct. It is like the system is creating 2 x pppoe single connections instead of joining the bundle....

     

    Any help would be great...

     

    Thanks



  • 9.  RE: MLPPP not passing data

     
    Posted 01-13-2020 12:08

    Okay. I have decided, from a troubleshooting perspective, that instead of a MikroTik I would use a vSRX-NG as the client and therefore have configured the following on the SRX:

     

    set version 20190606.224121_builder.r1033375
    set system root-authentication encrypted-password "$6$LlQ1ufNQ$Mah0vXe4lPNCKYmMQmm3/xm7F1k8UDEMkjvb0MT7jbs7dOZYUPE8sQMBdJFDes.px95V2CfaoNCYynrUWqrsI/"
    set system services ssh
    set system services web-management http interface fxp0.0
    set system syslog user * any emergency
    set system syslog file messages any any
    set system syslog file messages authorization info
    set system syslog file interactive-commands interactive-commands any
    set system license autoupdate url https://ae1.juniper.net/junos/key_retrieval
    set security screen ids-option untrust-screen icmp ping-death
    set security screen ids-option untrust-screen ip source-route-option
    set security screen ids-option untrust-screen ip tear-drop
    set security screen ids-option untrust-screen tcp syn-flood alarm-threshold 1024
    set security screen ids-option untrust-screen tcp syn-flood attack-threshold 200
    set security screen ids-option untrust-screen tcp syn-flood source-threshold 1024
    set security screen ids-option untrust-screen tcp syn-flood destination-threshold 2048
    set security screen ids-option untrust-screen tcp syn-flood queue-size 2000
    set security screen ids-option untrust-screen tcp syn-flood timeout 20
    set security screen ids-option untrust-screen tcp land
    set security policies from-zone trust to-zone trust policy default-permit match source-address any
    set security policies from-zone trust to-zone trust policy default-permit match destination-address any
    set security policies from-zone trust to-zone trust policy default-permit match application any
    set security policies from-zone trust to-zone trust policy default-permit then permit
    set security policies from-zone trust to-zone untrust policy default-permit match source-address any
    set security policies from-zone trust to-zone untrust policy default-permit match destination-address any
    set security policies from-zone trust to-zone untrust policy default-permit match application any
    set security policies from-zone trust to-zone untrust policy default-permit then permit
    set security zones security-zone trust tcp-rst
    set security zones security-zone untrust host-inbound-traffic system-services all
    set security zones security-zone untrust host-inbound-traffic protocols all
    set security zones security-zone untrust interfaces pp0.0
    set security zones security-zone untrust interfaces ge-0/0/0.0
    set interfaces ge-0/0/0 unit 0 encapsulation ppp-over-ether
    set interfaces fxp0 unit 0
    set interfaces pp0 unit 0 ppp-options pap local-name MLPPP-Test
    set interfaces pp0 unit 0 ppp-options pap local-password "$9$9brxCORrlMXNbvWb2oGq.Fn/C0BRhSeM8"
    set interfaces pp0 unit 0 ppp-options pap passive
    set interfaces pp0 unit 0 pppoe-options underlying-interface ge-0/0/0.0
    set interfaces pp0 unit 0 pppoe-options idle-timeout 0
    set interfaces pp0 unit 0 pppoe-options auto-reconnect 10
    set interfaces pp0 unit 0 pppoe-options client
    set interfaces pp0 unit 0 family inet mtu 1492
    set interfaces pp0 unit 0 family inet negotiate-address
    set routing-options static route 0.0.0.0/0 next-hop pp0.0

     

    It is a very basic config for a pppoe client, but I get no subscriber on the vMX.

     

    Can anyone see what is wrong with either of the configs regarding the vMX and the SRX please?

     

    Another point, I have removed vlan600 from the vMX and put it back to the following:

     

    set interfaces ge-0/0/0 unit 0 family pppoe dynamic-profile ml-pp0-member-prof

     



  • 10.  RE: MLPPP not passing data

     
    Posted 01-13-2020 12:58

    Okay, I won't annoy you all much more.... but I may have the issue but do not know how to reolve it as even the docs don't exactly tell you how to get around this..... give the configurations above, on the SRX I am receiving the following error:

     

    IO send ... PADI for pp0.0
    Jan 13 20:49:46 Discovery Input: PADO packet received on uifl (idx 72)
    Jan 13 20:49:46 Malformed packet: no ac name field in incoming PADO packet
    Jan 13 20:49:49 IO send ... Packet resend for pp0.0
    Jan 13 20:49:49 Discovery Input: PADO packet received on uifl (idx 72)
    Jan 13 20:49:49 Malformed packet: no ac name field in incoming PADO packet
    Jan 13 20:49:54 IO send ... Packet resend for pp0.0



  • 11.  RE: MLPPP not passing data

     
    Posted 01-14-2020 01:59

    MX usually includes its hostname in AC-Name tag in PADO packet, but I don't see any hostname configured on your vMX. Can you please try adding it and see if it helps.

    set system host-name <name>

     

    Best regards,

    Sergii

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

    Please accept the solution if your problem is resolved Smiley Happy

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



  • 12.  RE: MLPPP not passing data

     
    Posted 01-14-2020 02:53

    Hi

     

    I have added a system host-name to both devices but I am still getting the malformed packet error as follows:

     

    Jan 14 10:49:17 Malformed packet: no ac name field in incoming PADO packet

     

    I will try adding the command into the config and retry - the specifying the remote ac command



  • 13.  RE: MLPPP not passing data

     
    Posted 01-14-2020 03:44

    According to this link, only a single member link is supported in MLPPP bundle:

    Supports each MLPPP bundle containing a single member link.

    Best regards,

    Sergii

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

    Please accept the solution if your problem is resolved Smiley Happy

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



  • 14.  RE: MLPPP not passing data

     
    Posted 01-14-2020 05:29

    Hi Sergii,

     

    The SRX is being used as the PPPoE Client and the vMX as the Server for the MLPPP Bundle.

    I think the statement by Juniper on the link you mentioned is being mis-read....

     

    It would make absolutely zero sense to state that only "one" member can be used in an MLPPP Bundle on an MX, a PE device normally, with vast amounts of power. That would cause, I am pretty sure, an awful lot of problems for Service Providers using MX devices as PE equipment.

     

    I think what they are actually saying is that the MX can now support a single link, as in other docs it states it couldn't but an MLPPP Bundle can contain up to 8 links.


    Either way, even with a single link I am still back at square 1 (Unless I can get the SRX working).....

     

    The MLPPP bundle comes up but will not pass any traffic. Wireshark traces show no ICMP packets at all when Ping tests are being performed. But this is between a MikroTik and a Juniper.

     

    The reason for me using the SRX is to try and pinpoint where the problem may be. So, if I can get the SRX and MX up and passing traffic then I can narrow it down to the MikroTik.

     

    I still get this issue with AC-Name though....



  • 15.  RE: MLPPP not passing data
    Best Answer

     
    Posted 01-14-2020 07:14

    Hi,

     

    I understand your confusion, but there are two "flavours" of MLPPP implemented on MX. One is inline MLPPP, which supports multiple member links, but requires special MICs: Channelized OC3, Channelized OC12, Channelized T3/E3. It's description is availble here.

    MLPPP that was implemented for subscriber management supports only single member link. It was developed with LFI support in mind to avoid serialization delays. Most likely, there weren't many requests and this feature wasn't developed further.

    I understand that you see the problem of MLPPP staying up and not passing traffic even with single link, but I don't have any suggestions at this point - maybe I'll have some time to look into it a bit later by end of the week.

     

    Best regards,

    Sergii

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

    Please accept the solution if your problem is resolved Smiley Happy

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



  • 16.  RE: MLPPP not passing data

     
    Posted 01-14-2020 08:11

    Hi Sergii,

     

    Thank you for the response. This explains our findings perfectly.

     

    Very much appreciated.



  • 17.  RE: MLPPP not passing data

     
    Posted 01-15-2020 01:47

    Hi Sergii,

     

    Any idea how to get around the malformed packet issue other than host-name (which works in our lab)?

     

    I am trying to get wireshark up and running with eve-ng so I can see exactly what is being received in the PADO packet, but having problems with that.



  • 18.  RE: MLPPP not passing data

     
    Posted 01-15-2020 02:12

    Hi,

     

    You should be able to capture packets between vMX and vSRX by using "monitor traffic interface <name> no-resolve write-file /var/tmp/<capture.pcap>" on vMX.

     

    One more point - 18.2R1.9 is rather old JUNOS. Can you please try upgrading to 18.2R3-S2 and check if it helps?

     

    Best regards,

    Sergii

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

    Please accept the solution if your problem is resolved Smiley Happy

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