f two or more people are trying to share the same IP on an on-demand type basis, then the router needs to keep some kind of session table to be able to return traffic to the correct end user should something come by at a "random" interval.
And this is essentially what NAT is doing anyway, so wouldn't you be better off just implementing that? On 4 June 2013 11:51, Thong Hawk Yen <[email protected]> wrote: > Hi J-NSP Members, > > We are using MX480 with Junos [11.4X27.44] as BRAS and with Juniper policy > manager SRC with Software version SRC-PE Release 4.2 [V4.2.0.R-16] to > provide Broadband services over PPPoE. > The BRAS is the element that is leasing out IP addresses to the > subscribers on the ppo interfaces. We notice that there is a high > percentage of users are actually idling, not sending/receiving any traffic > but the sessions are taking up ip addresses. > > It is not very efficient to time-out their session because customer end > routers will re-dial. Is there a way to leave the PPPoE session on while > the BRAS relinquish idling sessions ip address and re-assign when the > customer traffic is back ? > > Please advise. Any feedback from any deployment of other BRAS would be > helpful. Thanks. > > Regards > thong > > ________________________________ > > CONFIDENTIALITY > ------------------------- > The contents of and any attachments to this email are private and > confidential. If you are not the intended recipient or addressee indicated > in this message, please notify the sender of the error and destroy the > email and any attachments. Please do not reproduce the contents of the > email or its attachments as such reproduction is a breach of > confidentiality and for which legal action including injunctive relief may > be sought against you. If it is your company policy that official > communications are not by email, please advise immediately. Any opinions, > conclusions and other information in this message that do not relate to the > official business of TIME dotCom shall be understood as neither given nor > endorsed by TIME dotCom, nor shall TIME dotCom shall be liable (directly or > vicariously) for such opinions, statements or communications. > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
