O Canada! > Canadian > Canadian Broadband > Ebox MLPPP testing time

reply to grunze510

Re: Ebox MLPPP testing time

if you guys are going to connect and disconnect in your scripts add a sleep timer between conecting to avoid bells timeout.

reply to diskace
Mr Diskace, when you say "force session on the same gateway .14", how do we do that ?

Friday morning, I did end up on .14 twice. Is it part of the standard pool of routers which handle any user on 3men ? Or do the AHSSPI facing routers only give .14 to users which radius qualifies as "ebox" ?

Angelo, unless you wait 15 minutes between login attempts (which resets the lock out to 0), you still get hit by it by the lock out.

What is not sure is whether a PADI request during a lock out will increase the lock out period (even though it is ignored) or whether it is only a PADI request that arrives after a lock out as ended.

For instance, if you are currently locked out for 4 seconds, if you send a PADI after 5 seconds, you will get a PADO, but if the login fails, the lock out increases to 8 seconds.

But if you send a PADI after 3 seconds, you will not get a response since it is during the lock out period, and it is not sure if this action results in the lock out increasing to 8 seconds or whether only the next PADI sent after the 4 second lock out ends will cause the increase to 8 seconds.

This will dictate whether it is worth coding delays in the scripts or not. If a PADI during a lock out period does not change the lockout period, then there is no point in having a script.

But if such a PADI does cause the lock out to increase, then there is a point in having a script since there is no point in sending a PADI during a lock out when you know that you won't get a response, while you also know it will extend the lock out.