I may have to have a chat with BT and/or MDNX in the morning...
2013-04-30T20:40:09.191754Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=MDNX70364@dsl.mdnx.com Calling=BBEU09880595
2013-04-30T20:40:10.271865Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=MDNX135303@dsl.mdnx.com Calling=BBEU09574052
2013-04-30T20:40:10.663198Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=UKDSL00717@vtl.viateldsl.com Calling=BBEU00380785
2013-04-30T20:40:11.570704Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=MDNX135303@dsl.mdnx.com Calling=BBEU09574052
2013-04-30T20:40:12.133318Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=MDNX70364@dsl.mdnx.com Calling=BBEU09880595
2013-04-30T20:40:12.712036Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=mdnx120891@dsl.mdnx.com Calling=BBEU09248797
2013-04-30T20:40:12.893569Z c.gormless radius-rx 81.145.117.4->90.155.53.21 Platform Accounting Username=WOLVS.STORE@LINKTWO.SOLUTIONONE.COM Calling=BBEU04679151
Out of interest, do the BBEU numbers correspond to AAISP lines? I wonder if this is plausibly misconfigured end user equipment, or if it's simply wrong.
ReplyDeleteNope, they are not A&A BBUEs
DeleteThey do match up on the MDNX side, and most of them I can now see in our RADIUS logs. Possibly a temporary BT glitch, but I've flagged it with the engineering team.
ReplyDeleteYeh, no way it is your fault, someone in BT has miss typed I am sure, and his mobile phone is on voicemail :-)
DeleteWell, whats 200 yards accross the A329 between friends?! :-)
ReplyDeleteWell, whats 200 yards accross the A329 between friends?! :-)
ReplyDeleteMind you that proximity does worry me slightly considering we use A&A to overlay MDNX MPLS... not something that we could have managed if we tried, we just hope no one gets trigger happy and nukes Bracknell!