You can set up captive portal authentication on your switch to redirect all Web browser requests to a

login page that requires users to input a username and password before they are allowed access.

Upon successful authentication, users are allowed access to the network and redirected to the

original page requested. Junos OS provides a customizable template for the captive portal window

that allows you to easily design and modify the look of the captive portal login page. You can modify

the design elements of the template to change the look of your captive portal login page and to add

instructions or information to the page. You can also modify any of the design elements of a captive

portal login page. The first screen displayed before the captive login page requires the user to read

the terms and conditions of use. By clicking the Agree button, the user can access the captive portal

login page. https://www.juniper.net/documentation/us/en/software/junos/user-access/topics/topicmap/user-authentication-captive-portal.html

BUM Traffic Forwarding

Junos devices that use MPLS encapsulation for EVPNs can only use ingress replication at this time.

Ingress replication means, to flood traffic to remote PE routers, the traffic has to be replicated, once

for each remote PE router.

The EVPN label for this BUM traffic is learned per PE router from the route type 3, inclusive multicast

Ethernet tag route.

This table shows the format of the inclusive multicast Ethernet tag route.

All-Active Redundancy (4)

This diagram shows the format of the type 1 route, A-D route per ES. The split horizon label is

advertised as part of an extended community attached to the type 1 route. The split horizon label is

also called the ESI label. The extended community also indicates what type of redundancy mode is

used for this given ESI: single-active represented by binary 1 or active-active represented by binary 0.

:

When enabling MSTP, you define one or more MSTP regions. An MSTP region defines a logical

domain where multiple spanning-tree instances (MSTIs) can be administered independently of MSTIs

in other regions, setting the boundary for bridge protocol data units (BPDUs) sent by one MSTI. An

MSTP region is a group of switches that is defined by three parameters:

Region name—User-defined alphanumeric name for the region.

Revision level—User-defined value that identifies the region.

Mapping table—Numerical digest of VLAN-to-instance mappings.

https://www.juniper.net/documentation/us/en/software/junos/stp-l2/topics/topic-map/spanningtree-configuring-mstp.html

Type 2 route, MAC with IP advertisement route—Type 2 routes are per-VLAN routes, so only PEs that

are part of a VNI need these routes. EVPN allows an end host’s IP and MAC addresses to be

advertised within the EVPN Network Layer reachability information (NLRI). This allows for control

plane learning of ESI MAC addresses. Because there are many Type 2 routes, a separate route-target

auto-derived per VNI helps to confine their propagation. This route type is supported by all EVPN

switches and routers. Type 5 route, IP prefix Route—An IP prefix route provides encoding for inter-

subnet forwarding. In the control plane, EVPN Type 5 routes are used to advertise IP prefixes for

inter-subnet connectivity across data centers. To reach a tenant using connectivity provided by the

EVPN Type 5 IP prefix route, data packets are sent as Layer 2 Ethernet frames encapsulated in the

VXLAN header over the IP network across the data centers.

Apply both the VRF export and BGP group or neighbor export policies (VRF first, then BGP) before

routes from the vrf or l2vpn routing tables are advertised to other PE routers.

https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/vpnapply-export-edit-protocols-bgp-vp.html