Hi Guys, Thanks for all the suggestion. Part of my requirement is also to integrate with the RADIUS attributes, so that we can dynamic control different users with different bandwidth according to their subscriptions & along with the service accounting.
I'll give it a try together with the RADIUS attributes (ingress / egress filter) to see if it works with the dynamic variable below. Thanks for all the suggestion. Will update shortly. users@lab-bng# ...-profiles PPPOE-IP-PROFILE interfaces pp0 unit "$junos-interface-unit" filter input ? Possible completions: <input> Name of filter applied to received packets $junos-input-filter Dynamic profile input filter $junos-input-ipv6-filter Dynamic profile input v6 filter Rgds Darren On Mon, Nov 3, 2014 at 6:51 AM, Ben Dale <[email protected]> wrote: > Hi Darren, > > > > > Our requirement is per below. For example, the bandwidth package is > 5Mbps. > > The IPv4 & IPv6 should be policed jointly to bandwidth of 5Mbps rather > than > > individual IPv4 or IPv6 family policing. If policing is done individually > > for IPv4 (5Mbps) and for IPv6 (5Mbps), the user is getting bandwidth of > > 10Mbps jointly which we tried to avoid. > > > Modify your PPPoE template so that you're applying the filter under > "$junos-interface-unit" rather than the address family: > > PPPOE-IP-PROFILE { > interfaces { > pp0 { > unit "$junos-interface-unit" { > ppp-options { > pap; > } > pppoe-options { > underlying-interface "$junos-underlying-interface"; > server; > } > filter { > input 5m; > output 5m; > } > family inet { > unnumbered-address "$junos-loopback-interface"; > } > family inet6 { > unnumbered-address "$junos-loopback-interface"; > } > } > } > } > } > > That will police regardless of the underlying address family. > > Cheers, > > Ben _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
