Network Problems?

[Christopher]

Its part of your login. Mines gw5 for instance

Thanks Gary I remember now 

[Christopher]

it's back for me now

[psp83]

It seems ok now, just hope it doesn't start again like earlier.

[Steve]

 

[psp83]

Thanks Gary I remember now 

I don't think "gateways" are used anymore with the new BT links, support/mods can correct me if I'm wrong on this..

But it used to tell which gateway you should connect to at the time but I don't think that happens anymore & it happens automatically now.

When I was having issues a year ago with my FTTC connection I was given a new username and IP to test with, the username ended in just @idnet.

[Bill]

Everything seems back to normal, but I'm not counting chickens yet.

When I was having issues a year ago with my FTTC connection I was given a new username and IP to test with, the username ended in just @idnet.

Similar here- when I was having IPv6 problems IDNet tried me on a new login, that just ends in @idnet.

[psp83]

Everything seems back to normal, but I'm not counting chickens yet.

Similar here- when I was having IPv6 problems IDNet tried me on a new login, that just ends in @idnet.

I prefer the @idnet, it's easier to remember and type than @uk.idnet.dsl4 

[Steve]

I think with the host link and it's back up, we all log on to the same pipe work now with load balancing between the two. The previous links whatever they called them were of more limited capacity and more numerous hence the extension was required to log on to a individual pipe. I presume to prevent congestion and balance the load. But then I could be bullshitting.

[andrue]

Fine here now as well. No sign of my 60 day issue either which is interesting. And yes - if you're on ADSL don't reboot the 'router' if it's also your modem 

[Bill]

One oddity- Everything was working fine, with the sole exception of my IPv6 BQM (other IPv6 tests passed as OK).

I had to disconnect/reconnect to get the BQM working again

[psp83]

One oddity- Everything was working fine, with the sole exception of my IPv6 BQM (other IPv6 tests passed as OK).

I had to disconnect/reconnect to get the BQM working again

And in return it looks like you have a better ping by a ms or 2 

[Bill]

And in return it looks like you have a better ping by a ms or 2 

Yes, it does seem to be a touch better, I hadn't noticed that

[davecollins]

Mine was back up, then I foolishly rebooted the router. Now it won't connect at all. Orange light on the internet indicator. Great.

[Steve]

Turn it off for awhile and try again.

[davecollins]

I had it off for a few minutes just now. Still getting the orange light.

[Bill]

I'm inclined to think that not everything may yet be as it should- I'm still getting the odd spike on the BQM that I don't like the look of.

Never mind- I'd forgotten I'd run a speed test, that would explain it

[davecollins]

Right, but I can't even connect now.

[davecollins]

No idea what's happening now.

[Bill]

That's what my IPv6 BQM looked like until I reconnected... not that that's any help to you

Anything useful in the router log?

[davecollins]

Nothing at all. I also just tried to log in directly to the BT OpenReach router but can't connect. I've been waiting for over an hour for someone from IDNet support to ring me back. The first person said it would be within 15 minutes - an hour ago. Not impressed.

[psp83]

Nothing at all. I also just tried to log in directly to the BT OpenReach router but can't connect. I've been waiting for over an hour for someone from IDNet support to ring me back. The first person said it would be within 15 minutes - an hour ago. Not impressed.

Have you tried turning the router/modem off for 30 mins? maybe stale session.

[psp83]

That's what my IPv6 BQM looked like until I reconnected... not that that's any help to you

There does seem to be a IPv6 issue though..

[Bill]

There does seem to be a IPv6 issue though..

I get 10/10 for the readiness test, the connection one varies, but that could be the operating system (OS X in my case) not IDNet.

Check this link out, I quite often get it on the test-ipv6 site:

http://test-ipv6.com/faq_avoids_ipv6.html

[nomad101]

I had the same symptoms as Bill when it came back.  IPv4 worked fine but IPv6 didn't work until I disconnected and reconnected.  I didn't reboot the router, just did a disconnect/reconnect of the PPPoE session.

IPv6 connectivity tests showed the same as psp83 and you can see the different behaviour of IPv4/IPv6 in my BQM graphs.  I've seen this before after an outage and suspect IPv6 doesn't fail over between routers nicely.  I noticed my tracert is going out via gw2 now when it was using gw4 earlier.

[Bill]

IPv6 was working properly from my end after the outage, it was only the BQM that required the reconnect.

I don't know much about how these things work, but it was as though routing from me was fine, routing to me hadn't failed over properly.