Junos OS

I have a pppoe profile applied to some vlans interfaces.

set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" family inet unnumbered-address lo0.0
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" pppoe-options server
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options chap
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options pap

set interfaces xe-0/1/1 flexible-vlan-tagging
set interfaces xe-0/1/1 unit 10 encapsulation ppp-over-ether
set interfaces xe-0/1/1 unit 10 vlan-id 10
set interfaces xe-0/1/1 unit 10 pppoe-underlying-options duplicate-protection
set interfaces xe-0/1/1 unit 10 pppoe-underlying-options dynamic-profile PPPOE-PROFILE
set interfaces xe-0/1/1 unit 11 encapsulation ppp-over-ether
set interfaces xe-0/1/1 unit 11 vlan-id 11
set interfaces xe-0/1/1 unit 11 pppoe-underlying-options duplicate-protection
set interfaces xe-0/1/1 unit 11 pppoe-underlying-options dynamic-profile PPPOE-PROFILE

set interfaces xe-0/1/1 unit 100 encapsulation ppp-over-ether
set interfaces xe-0/1/1 unit 100 vlan-id 100
set interfaces xe-0/1/1 unit 100 pppoe-underlying-options duplicate-protection
set interfaces xe-0/1/1 unit 100 pppoe-underlying-options dynamic-profile PPPOE-PROFILE

I also need inet address together with pppoe service on some shared vlans to manage the remote device.

So I have tried to apply the following configuration:

set interfaces xe-0/1/1 unit 100 family inet address 10.0.0.1/30

and got the error:

[edit interfaces xe-0/1/1 unit 100]
'family'
Can't configure protocol family with encapsulation ppp-over-ether
error: configuration check-out failed: (statements constraint check failed)

Is there any way to solve the problem?

You need demux source to bind inet, for instance:

 

set dynamic-profiles PPPOE-PROFILE routing-instances "$junos-routing-instance" interface "$junos-interface-name"
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" no-traps
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options chap
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options pap
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options authentication chap
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" pppoe-options underlying-interface "$junos-underlying-interface"
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" pppoe-options server
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" keepalives interval 60
set dynamic-profiles PPPOE-PROFILE interfaces pp0 unit "$junos-interface-unit" family inet unnumbered-address "$junos-loopback-interface"

set interfaces xe-0/0/1 flexible-vlan-tagging
set interfaces xe-0/0/1 unit 2000 encapsulation ppp-over-ether
set interfaces xe-0/0/1 unit 2000 vlan-id 50
set interfaces xe-0/0/1 unit 2000 pppoe-underlying-options dynamic-profile PPPOE-PROFILE

set interfaces demux0 unit 1000101 demux-source inet
set interfaces demux0 unit 1000101 vlan-id 50
set interfaces demux0 unit 1000101 demux-options underlying-interface xe-0/0/1
set interfaces demux0 unit 1000101 family inet

 

Or even better, I suggest just configure vlan auto-sense configuration and accept any packet type. For instance:

 

set dynamic-profiles VLAN-PROFILE interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" vlan-id "$junos-vlan-id"
set dynamic-profiles VLAN-PROFILE interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family pppoe duplicate-protection
set dynamic-profiles VLAN-PROFILE interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" family pppoe dynamic-profile PPPoE-Profile

set dynamic-profiles PPPOE_PROFILE routing-instances "$junos-routing-instance" interface "$junos-interface-name"
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options chap
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" ppp-options pap
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" pppoe-options underlying-interface "$junos-underlying-interface"
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" pppoe-options server
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" keepalives interval 60
set dynamic-profiles PPPOE_PROFILE interfaces pp0 unit "$junos-interface-unit" family inet unnumbered-address "$junos-loopback-interface"

set interfaces xe-1/0/1 flexible-vlan-tagging
set interfaces xe-1/0/1 auto-configure vlan-ranges dynamic-profile VLAN-PROFILE accept any  <<<<< any packet type
set interfaces xe-1/0/1 auto-configure vlan-ranges dynamic-profile VLAN-PROFILE ranges any  <<<<< any vlan or you can specfic vlan-range
set interfaces xe-1/0/1 auto-configure remove-when-no-subscribers

 

 

Tried the configuration:

 

set interfaces demux0 unit 400 demux-source inet
set interfaces demux0 unit 400 vlan-id 400
set interfaces demux0 unit 400 demux-options underlying-interface xe-0/1/1
set interfaces demux0 unit 400 family inet address 10.0.0.1/30

 

the configuration commit but I got the error in log:

DCD_CONFIG_WRITE_FAILED: IFL demux0.400 configuration write failed for an IFL ADD: Address already in use

can't ping 10.0.0.1 or remote 10.0.0.2

 

You dont require inet address:

set interfaces demux0 unit 400 family inet address 10.0.0.1/30

 

The server /bras picks source address as loopback back that you defined in dynamic-profile.

Just "set interfaces demux0 unit 400 family inet" should do.  Address is not required. 

 

So i need to have at least a subscriber connected to pick a address. 

 

yes ofcourse you need CPE (or some PPPoE client tester like ixia or sprirent) to dail a PPPoE session.

cpe(client) dails pppoe session by PPPoE discovery phase (padi/o/r/s) post that, the ppp lcp & ncp starts in which at LCP username/pass is authenticated and at NCP,  IpAddr is allocated by server(MX) to the CPE. (an address can be given from address-pool configured locally on MX or can be given from aaa/radius as well.

 

Will this work for the topology below?

I need to manage the bridged device that is in the same vlan as the pppoe client. 

 

whats the bridged device use here for? I think or assume you trying to communicate the vlan 10 PPPoE client to vlan 20 PPPoE client?

 

If yes, this can be just L2 network by setting vlan to access port..Meaning, have switch to tag the vlans (one port vlan 20 and another port vlan 10) and use unrestricted proxy ARP that enables the router or switch to respond to any ARP request, on condition that the router has an active route to the destination address of the ARP request.

 

BRAS will have active route to both of these subscriber (as access-internal /32 host route) since its one who allocated the address in first place.

 

set interfaces demux0 unit x proxy-arp unrestricted

or in the dynamic profile:

set dynamic-profiles test interfaces demux0 unit $junos-interface-unit proxy-arp unrestricted

The bridged device have others wireless devices also bridged. A radio broadcast network, so I need manage these devices.

I'll share the vlans with another switch and configure the ip address there. I think will work out 😉

 

I'll configure setup in my lab and will share you o/p. Meanwhile, did you try my suggested config?