presumably you can get to something on bt.net via the test login ?

Yes, normally the BT Wholesale 'error' page, which states you have been directed here because you are logged in with bt_test, etc,etc.

But normally you are just looking for a green light next to the sync like on your tester, no more than this required 9 times out of 10.

So, let me get this clear in my head...

1. Ask my ISP if my username is logged on in their Radius server.
If so, then its a messed up PPP session which needs clearing?
However, Namesco tech have already confirmed they could see my "connection dropped" on Wed 27th at 9:15am, will they be getting this info from their Radius server? If so, then have they already confirmed i am not logged in, (i.e. no PPP session is in progress)?

2. I have read that there are two Radius servers requiring authentication to achieve an internet connection, the first by BT and if this is OK then the 2nd by the ISP. I'm not sure of the details here but could it be the trouble is with the BT RAS rather than my ISP? Would that explain why the bt_test login's also fail?

3. If i get a BT engineer back i need to get him to use his JDSU with the bt_test or bt_test_user login and show me the BT wholesale error page. Since my router cannot login via these details i need to know for sure whether the JDSU can. I hope it doesn't becuase otherwise i think i'm at a dead end.

4. Zarjaz, you seem very knowledgeable about what BT test gear can and cannot do. So, is it possible the the BT engineer can use my Namesco UN & PW in his JDSU?

5. Also, Zarjaz, can the engineer's test equipment "listen in" on the PPP handshaking between my router and the Radius servers?

6. Question the engineer whether it could be the port on the DSLAM
------

By the way, thanks for you help, it is much appreciated.

1. The Weds 27th log off sounds like it's from RADIUS logs, typically they log connect / disconnect events and sometimes hourly updates of traffic volume.

2. Sort of, the first RADIUS checks for a valid username and routes to the relevant provider - for example it will send ISP traffic to the ISP and other domains elsewhere @startup_domain perhaps. If your router logged these things you would see if the first RADIUS was contacted and rejected the session or if it got to the ISP. Or if it got nowhere.

Update - It's now fixed!!

Still not heard from Namesco, my support ticket status says "Awaiting BT".

Here is the syslog for the period when it started working. Anyone care to speculate on what had been done to fix it? I'd be interested to know for future ref with my clients.
It wasn't me as i had not touched the router since yesterday.

Looks to my untrained eye that something external to my premises was reset. Looks like it caused a resync so possibly the DSLAM?

Yarwell, Zarjaz thanks again!


09:59:43Jan 1 09:12:58 WAN1 PPPoE ==> V:1 T:1 PADT ID:6
09:59:43Jan 1 09:12:58 WAN1 PPPoE ==> V:1 T:1 PADI ID:0
09:59:43Jan 1 09:12:58 WAN1 PPPoE <== V:1 T:1 PADO ID:0
09:59:46Jan 1 09:13:01 WAN1 PPPoE <== V:1 T:1 PADO ID:0
09:59:46Jan 1 09:13:01 WAN1 PPPoE ==> V:1 T:1 PADR ID:0
09:59:46Jan 1 09:13:01 WAN1 PPPoE <== V:1 T:1 PADS ID:6
09:59:49Jan 1 09:13:04 WAN1 PPPoE <== V:1 T:1 PADS ID:6
09:59:49Jan 1 09:13:04 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x00 MRU: 1500 ##
09:59:57Jan 1 09:13:11 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x01 MRU: 1500 ##
10:00:05Jan 1 09:13:19 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x02 MRU: 1500 ##
10:00:13Jan 1 09:13:27 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x03 MRU: 1500 ##
10:00:16Jan 1 09:13:31 DSL: LineFailure Update: DSL_G997_LINEFAILURE_LOS!
10:00:17Jan 1 09:13:31 DSL: NE Loss of Signal, rebooting DSL state machine
10:00:17Jan 1 09:13:31 DSL: LineFailure Update: DSL_G997_LINEFAILURE_LOS
10:00:17Jan 1 09:13:31 DSL: DSL Rebooting...
10:00:17Jan 1 09:13:31 DSL: Modem Shut Down from ADSL Phy Layer (0)
10:00:31Jan 1 09:13:45 DSL: DSL Rebooting...
10:00:48Jan 1 09:14:03 DSL: DSL SHOWTIME
10:00:51Jan 1 09:14:06 WAN1 PPPoE ==> V:1 T:1 PADT ID:6
10:00:51Jan 1 09:14:06 WAN1 PPPoE ==> V:1 T:1 PADI ID:0
10:00:51Jan 1 09:14:06 WAN1 PPPoE <== V:1 T:1 PADO ID:0
10:00:54Jan 1 09:14:09 WAN1 PPPoE <== V:1 T:1 PADO ID:0
10:00:54Jan 1 09:14:09 WAN1 PPPoE ==> V:1 T:1 PADR ID:0
10:00:54Jan 1 09:14:09 WAN1 PPPoE <== V:1 T:1 PADS ID:6
10:00:57Jan 1 09:14:12 WAN1 PPPoE <== V:1 T:1 PADS ID:6
10:00:57Jan 1 09:14:12 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x00 MRU: 1500 ##
10:00:58Jan 1 09:14:13 WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0xF7 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:00:58Jan 1 09:14:13 WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0xF7 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:01:01Jan 1 09:14:16 WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0xF8 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:01:01Jan 1 09:14:16 WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0xF8 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:01:04Jan 1 09:14:19 WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0xF9 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:01:04Jan 1 09:14:19 WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0xF9 Authentication Type: CHAP 05 Magic Number: 0xd1c9d2a ##
10:01:05Jan 1 09:14:19 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x01 MRU: 1500 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:LCP(c021) ConfAck Identifier:0x01 MRU: 1500 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:CHAP(c223) Challenge Identifier:0x00 10 8e 97 d7 75 c8 56 16 37 48 0d cd e7 6f fc e7 fa 45 52 58 31 35 2e 53 68 65 66 66 69 65 6c 64 32 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:CHAP(c223) Response Identifier:0x00 10 f6 12 8c 85 3f be c2 c4 a1 d1 01 28 ad b9 51 19 31 32 33 30 30 35 32 40 64 73 6c 2d 6c 6f 67 69 6e 32 2e 63 6f 6d ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:LCP(c021) ConfReq Identifier:0x01 Authentication Type: CHAP 05 Magic Number: 0x23f26a64 MRRU: 1524 Endpoint Discriminator Locally Assigned Address: 61 72 32 2e 74 68 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:LCP(c021) ConfReq Identifier:0x02 MRU: 1500 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:LCP(c021) ConfAck Identifier:0x01 Authentication Type: CHAP 05 Magic Number: 0x23f26a64 MRRU: 1524 Endpoint Discriminator Locally Assigned Address: 61 72 32 2e 74 68 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:LCP(c021) ConfAck Identifier:0x02 MRU: 1500 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:CHAP(c223) Challenge Identifier:0x01 10 3a 24 16 67 14 a1 8d ff 1b 79 64 22 57 b9 bc ec 61 72 32 2e 74 68 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:CHAP(c223) Response Identifier:0x01 10 68 0b f6 33 ea a1 8f 00 30 ec 96 e6 eb 1a f9 ee 31 32 33 30 30 35 32 40 64 73 6c 2d 6c 6f 67 69 6e 32 2e 63 6f 6d ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:CHAP(c223) Success Identifier:0x01 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x00 Vendor Specific: 00 00 0c 01 00 00 00 00 IP Address: 0 0 0 0 Primary Domain Name Server: 0 0 0 0 Secondary Domain Name Server: 0 0 0 0 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:IPCP(8021) ConfReq Identifier:0x01 IP Address: 195 7 254 131 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:IPCP(8021) ConfAck Identifier:0x01 IP Address: 195 7 254 131 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:IPCP(8021) ConfRej Identifier:0x00 Vendor Specific: 00 00 0c 01 00 00 00 00 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x01 IP Address: 0 0 0 0 Primary Domain Name Server: 0 0 0 0 Secondary Domain Name Server: 0 0 0 0 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:IPCP(8021) ConfNak Identifier:0x01 IP Address: 213 246 85 98 Primary Domain Name Server: 195 7 224 57 Secondary Domain Name Server: 195 7 224 143 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE ==> Protocol:IPCP(8021) ConfReq Identifier:0x02 IP Address: 213 246 85 98 Primary Domain Name Server: 195 7 224 57 Secondary Domain Name Server: 195 7 224 143 ##
10:01:05Jan 1 09:14:20 WAN1 PPPoE <== Protocol:IPCP(8021) ConfAck Identifier:0x02 IP Address: 213 246 85 98 Primary Domain Name Server: 195 7 224 57 Secondary Domain Name Server: 195 7 224 143 ##
10:01:05Jan 1 09:14:20 WAN 1 is up.

So, is it possible the the BT engineer can use my Namesco UN & PW in his JDSU?

Yes, but you'd need to be a bit 'lucky' and get a slightly more clued up engineer. Do what you ask is not actually a required part of the LLU SFI visit, so they could just decline.

can the engineer's test equipment "listen in" on the PPP handshaking between my router and the Radius servers?

Not as far as I am aware.


Glad to hear it's fixed. At a guess, the port has been flexed or reset.