PN gateway question
Hi all, I'm trying to work out whether I have a problem or PN does...
Is anyone having issues on gateways:
ptn-ag2
pcl-ag01
thn-ag1
?
When connected to any of those, I can get to most websites but not some (such as btinternet.com and metoffice.gov.uk). Same sorta thing for email - sometimes I can pickup from PN but not others... sometimes I can pick from everywhere *except* PN.
After lots of router reboots I'm on thn-ag3 and everything's OK again, but it's bugging me 'cos I haven't seen any recent gateway issues on the stats page and I'm wondering if it's me that's doing something stupid. (Wouldn't be the first time
)
Is anyone having issues on gateways:
ptn-ag2
pcl-ag01
thn-ag1
?
When connected to any of those, I can get to most websites but not some (such as btinternet.com and metoffice.gov.uk). Same sorta thing for email - sometimes I can pickup from PN but not others... sometimes I can pick from everywhere *except* PN.
After lots of router reboots I'm on thn-ag3 and everything's OK again, but it's bugging me 'cos I haven't seen any recent gateway issues on the stats page and I'm wondering if it's me that's doing something stupid. (Wouldn't be the first time
)
Oops.
It turns out it was me doing something stupid after all, although not here, quite.
I had set up a new router for someone starting with PlusNet by configuring it here, with my login details. Usually I do that on the client's site but for other reasons I ended up with the router here first.
So... I forgot to replace my PlusNet login with the client's when I set up the router onsite. The client's connection seemed OK if a trifle slow, but often connections are a bit odd for the first few days so I didn't think too much about it.
Anyway, to cut a long story short, if two routers use the same credentials to log on to PlusNet and the account is configured with a static IP... both resulting nodes get assigned the same IP. Cue fun and games with routing at both nodes.
What was amazing was that at times both routers managed to get logged on at the same time with the same IP and still pass some traffic, albeit rather slowly or intermittently.
It was all my fault for setting up 2 routers with the same credentials, but if the 2nd one had simply failed to login when the 1st one was already online, I'd have spotted my mistake almost immediately.
It was only when I went back to the client's site to have a look at continued slow/non-performance that I checked the new router and had the "Doh!" moment 🙂
Ah well, I'll remember not to do that again!
It turns out it was me doing something stupid after all, although not here, quite.
I had set up a new router for someone starting with PlusNet by configuring it here, with my login details. Usually I do that on the client's site but for other reasons I ended up with the router here first.
So... I forgot to replace my PlusNet login with the client's when I set up the router onsite. The client's connection seemed OK if a trifle slow, but often connections are a bit odd for the first few days so I didn't think too much about it.
Anyway, to cut a long story short, if two routers use the same credentials to log on to PlusNet and the account is configured with a static IP... both resulting nodes get assigned the same IP. Cue fun and games with routing at both nodes.
What was amazing was that at times both routers managed to get logged on at the same time with the same IP and still pass some traffic, albeit rather slowly or intermittently.
It was all my fault for setting up 2 routers with the same credentials, but if the 2nd one had simply failed to login when the 1st one was already online, I'd have spotted my mistake almost immediately.
It was only when I went back to the client's site to have a look at continued slow/non-performance that I checked the new router and had the "Doh!" moment 🙂
Ah well, I'll remember not to do that again!