PPP sessions are first authenticated by BT to see if its the right domain then passed to the ISP for full authentication.

I'm intrigued to know why its front end should be given a private non-internet address but with gateways and dns related to BT.

the connection is provided by BT, you didn't authenticate for an internet service. Sort of explains both.

In reply to a post by Anonymous:

Its only job is to see what the stats are without trying to actually login to the ISP and somehow it ends up showing that info I described.

If you don't authenticate with your ISP then the only relevant figures you can get are the connection stats giving your sync with the exchange.

Those IP addys etc. you quote are meaningless. But, altho' you have so far refused to state your ISP when asked, I guess you are on a BT IPStream ISP and so it makes sense that those addys belong to BT, since BT is unable to connect you with your ISP as you failed to give them your true authentication details.

In reply to a post by Anonymous:

...what happens is that after a short while it says PPOE/LLC and then without providing login details it shows this -

IP address 172.16.67.78

...But why is this occuring?

I believe that your experience is a variation on a fairly common issue;

Here
Mentioned here
Here
Mentioned here
Here
Mentioned here

The problem only appears to occur on BT Wholesale supplied services.

The solution is to move to BE or O2 LLU (possibly other) services.

JC

yarwell wrote

PPP sessions are first authenticated by BT to see if its the right domain then passed to the ISP for full authentication.

the connection is provided by BT, you didn't authenticate for an internet service. Sort of explains both.

xrayspex wrote

If you don't authenticate with your ISP then the only relevant figures you can get are the connection stats giving your sync with the exchange.

Those IP addys etc. you quote are meaningless. But, altho' you have so far refused to state your ISP when asked, I guess you are on a BT IPStream ISP and so it makes sense that those addys belong to BT, since BT is unable to connect you with your ISP as you failed to give them your true authentication details.

In relation to both. My neighbour who has phone and broadband from BT, I tried the setup I have with them. It does _not_ show the addresses I gave earlier. And it gives much the same quality of line details though a bit better than mine.

Do I take it that the implication given about BT Wholesale applies to an ISP who gets a bundle from BT and so the customer might get the an

sorry, finger trouble.


Do I take it that the implication given about BT Wholesale applies to an ISP who gets a bundle from BT, or appears under a kind of umbrella sub-customer of BT services, and so the customer might get the anomaly I've seen.

But this would not apply to BT _itself_, meaning they and their customers are directly involved and not part of "BT Wholesale"?

And I had seen a couple of those referenced Forum posts before starting all this, they didn't provide much in the way of help.

a different router may not do this "auto detect" stuff, which I never use anyway.

BT Wholesale provide services to many users.

I'm failing to see why this is a "problem" in any way ? you're looking at data from a half set up router, finish the job and it'll go away.

If I recall correctly, when I last had a BT Ipstream based connection with an ISP whose radius server was regularly failing, then BT's BRAS or whatever, would eventually connect you to a BT network and when you tried to view any web page, a BT service page informing you that either your ISP's radius server was down, or the authentication details were invalid would be displayed.

Edited by AbandonShip (Wed 19-Jan-11 00:12:23)

In reply to a post by Anonymous:

Do I take it that the implication given about BT Wholesale applies to an ISP who gets a bundle from BT, or appears under a kind of umbrella sub-customer of BT services, and so the customer might get the anomaly I've seen.

Exactly, that's my theory!

In reply to a post by Anonymous:

But this would not apply to BT _itself_,

Again it fits my theory. BT itself, as an ISP, would not need or have another ISP to connect to and so would not be failing an authentication.

In reply to a post by Anonymous:

meaning they and their customers are directly involved and not part of "BT Wholesale"?

Dunno about this bit. BTR's BT Broadband would still be a customer of BTW.

In reply to a post by XRaySpeX:

In reply to a post by Anonymous:

Do I take it that the implication given about BT Wholesale applies to an ISP who gets a bundle from BT, or appears under a kind of umbrella sub-customer of BT services, and so the customer might get the anomaly I've seen.

Exactly, that's my theory!

You are right in principle, but with the Good ISPs (like Zen), it just never happens.

In reply to a post by XRaySpeX:

In reply to a post by Anonymous:

But this would not apply to BT _itself_,

Again it fits my theory. BT itself, as an ISP, would not need or have another ISP to connect to and so would not be failing an authentication.

Not quite right this time - BT Retail are treated just like the other ISPs (Zen, Entanet, etc)

In reply to a post by XRaySpeX:

In reply to a post by Anonymous:

meaning they and their customers are directly involved and not part of "BT Wholesale"?

Dunno about this bit. BTR's BT Broadband would still be a customer of BTW.

BT Retail buy their services from BT Wholsale just as the others. do