198.18.1.x address problems
Regarding the link, yes, I've made a complete arse of myself 
getting it wrong for the second time by rushing to correct it. I'll amend it again. 
I would think you really knew which link of the 4 in that thread I really meant.
We all make mistakes from time to time, you choose to use that minor mistake to try and belittle everything else I've said with your second comment.
It has nothing to do with my opinion not agreeing with you. As the comment says, there are posts of yours in the past (and I'm not going to search for links, other's can readily do that, I would prefer to do something more constructive) where you have just dismissed the 582n as - I'll paraphrase - a pile of junk. It's rather odd that a number of major ISPs have chosen to use the TG582n including the well respected A&AISP so it can't exactly be a pile of junk. So you mention forum rules as another red herring to justify your position. I have always said that the 582n is quite good for a budget modem/router, that doesn't mean it's perfect. Now do you think we can stop this petty bickering and actually discuss some facts especially using terminology and language that the majority of people instead of a select few might understand.
I'll reply further with some technical responses in a follow up post.
getting it wrong for the second time by rushing to correct it. I'll amend it again. I would think you really knew which link of the 4 in that thread I really meant.
We all make mistakes from time to time, you choose to use that minor mistake to try and belittle everything else I've said with your second comment.
It has nothing to do with my opinion not agreeing with you. As the comment says, there are posts of yours in the past (and I'm not going to search for links, other's can readily do that, I would prefer to do something more constructive) where you have just dismissed the 582n as - I'll paraphrase - a pile of junk. It's rather odd that a number of major ISPs have chosen to use the TG582n including the well respected A&AISP so it can't exactly be a pile of junk. So you mention forum rules as another red herring to justify your position. I have always said that the 582n is quite good for a budget modem/router, that doesn't mean it's perfect. Now do you think we can stop this petty bickering and actually discuss some facts especially using terminology and language that the majority of people instead of a select few might understand.
I'll reply further with some technical responses in a follow up post.
Just ran into this on my mum's connection! 
Hi Kelly,
Happy Christmas. Hope the thread helped you circumvent the issue. May be when you get back to the office, you'll give the product boys a prod? I've tried but no one has responded on this issue.
...for a moment I thought you where working the forums today
Kevin
Happy Christmas. Hope the thread helped you circumvent the issue. May be when you get back to the office, you'll give the product boys a prod? I've tried but no one has responded on this issue.
...for a moment I thought you where working the forums today
Kevin
Kelly,
Thanks for that - much appreciated. I have made direct approaches to people in products asking for this to be examined, but I have not received a reply on the matter.
In passing, I was 'elsewhere' yesterday with my laptop and could not connect to anywhere until after I had 'unfixed' my fix for being at home with the TG582n router. Now that I'm back home I had issues on start-up (which seem to have righted themselves) but I suspect I'll need to reapply the fix later today - not ideal!
Kevin
Thanks for that - much appreciated. I have made direct approaches to people in products asking for this to be examined, but I have not received a reply on the matter.
In passing, I was 'elsewhere' yesterday with my laptop and could not connect to anywhere until after I had 'unfixed' my fix for being at home with the TG582n router. Now that I'm back home I had issues on start-up (which seem to have righted themselves) but I suspect I'll need to reapply the fix later today - not ideal!
Kevin
We haven't got a trees smiley, there is a wood for the trees problem here 
The "fix" should be -
Turn off the DNS spoofing as suggested by Matt
Matt explained in that post that the TG582n did this when the WAN was down, however that was not the complete picture. It will also do it when a DNS lookup fails.
He went on to say it was
Well to be quite honest I found that this "feature" and the 'Web browsing Interception' "feature" to be two of the most unhelpful "features" of the TG582n's default settings. Even with the various firmware upgrades they never seem to have directed towards anything helpful. I have both turned off. As far as I'm concerned they have no practical purpose whatsoever.
The Spoofing issue is the primary context of the thread. However there are 3 different things going on here which have become confused at various times and resulted in some red herrings on occasion. So for clarity they are -
1) With default settings the TG582n produces a spoofed IP address if a DNS lookup fails
2) Certain Windows OSes compound the problem because they cache the spoofed addresses which are not cleared in a timely manner - this results in browsing failures
3) Plusnet DNS lookups seem to fail more frequently than other DNS resolvers
To get rid of the problem - Turn OFF the Spoofing by telnetting into the TG582n and run the following commands.
dns server config WANDownSpoofing = disabled
dns server debug spoof clear
dns server debug spoof list
saveall
exit
The spoof 'clear' and 'list' commands are to make sure the list is empty (so your OS cache won't pick up any old spoofed addresses).
When you've done the above, then clear your OS (usually Windows) caches.
That will get rid of the problem.
To try and keep this simple, DNS Lookups fail from time to time for a variety of reasons. It doesn't matter which DNS resolvers you use, whether they are Plusnet, Google, Level3, OpenDNS etc. it happens. I've used different DNS, different routers, different OSes & different machines at various times and it still happens now and again.
If you want to know why a particular one failed, you will probably be chasing your tail for a long time. But you will need to do a variety of things such as wiresharking and the likes as has been suggested by Matt, ejs and others. I've tried some of these at various times in the past and found it to be totally fruitless because the failures are generally random (except when there's been an obvious resolver issue which has affected multiple users) and for example, the results of a eg. wireshark simply show the lookup has failed.
Matt asked for an example, one was given here. If he looked at it, he didn't come back to comment.
Now if you want to know why Plusnet DNS ones fail more frequently, that's a very good question which many have asked about from time to time over the years but we've never had a real explanation. But as Plusnet's network is changing, that question may no longer be relevant - or may become more relevant if there's a gremlin somewhere
If you find Plusnet DNS resolvers to be a problem then pick some other ones and either set them in your Router or in your OS IP Config.
@Townman
Have you actually tried turning off Spoofing?
Kelly, getting any feedback from Products regarding any Modem/Router firmware issues seems to be a problem these days (apart from one very helpful individual) which makes it virtually impossible to help a variety of people with their problems from time to time, so I have virtually given up.
Quote from: Kelly What's your fix?
The "fix" should be -
Turn off the DNS spoofing as suggested by Matt
Quote from: Matt You can turn off this functionality by running the command given by npr earlier ":dns server config WANDownSpoofing=disabled"
Matt explained in that post that the TG582n did this when the WAN was down, however that was not the complete picture. It will also do it when a DNS lookup fails.
He went on to say it was
Quote so that any browsing requests are directed towards 'helpful' features on the router to get people back online.
Well to be quite honest I found that this "feature" and the 'Web browsing Interception' "feature" to be two of the most unhelpful "features" of the TG582n's default settings. Even with the various firmware upgrades they never seem to have directed towards anything helpful. I have both turned off. As far as I'm concerned they have no practical purpose whatsoever.
The Spoofing issue is the primary context of the thread. However there are 3 different things going on here which have become confused at various times and resulted in some red herrings on occasion. So for clarity they are -
1) With default settings the TG582n produces a spoofed IP address if a DNS lookup fails
2) Certain Windows OSes compound the problem because they cache the spoofed addresses which are not cleared in a timely manner - this results in browsing failures
3) Plusnet DNS lookups seem to fail more frequently than other DNS resolvers
To get rid of the problem - Turn OFF the Spoofing by telnetting into the TG582n and run the following commands.
dns server config WANDownSpoofing = disabled
dns server debug spoof clear
dns server debug spoof list
saveall
exit
The spoof 'clear' and 'list' commands are to make sure the list is empty (so your OS cache won't pick up any old spoofed addresses).
When you've done the above, then clear your OS (usually Windows) caches.
That will get rid of the problem.
To try and keep this simple, DNS Lookups fail from time to time for a variety of reasons. It doesn't matter which DNS resolvers you use, whether they are Plusnet, Google, Level3, OpenDNS etc. it happens. I've used different DNS, different routers, different OSes & different machines at various times and it still happens now and again.
If you want to know why a particular one failed, you will probably be chasing your tail for a long time. But you will need to do a variety of things such as wiresharking and the likes as has been suggested by Matt, ejs and others. I've tried some of these at various times in the past and found it to be totally fruitless because the failures are generally random (except when there's been an obvious resolver issue which has affected multiple users) and for example, the results of a eg. wireshark simply show the lookup has failed.
Matt asked for an example, one was given here. If he looked at it, he didn't come back to comment.
Now if you want to know why Plusnet DNS ones fail more frequently, that's a very good question which many have asked about from time to time over the years but we've never had a real explanation. But as Plusnet's network is changing, that question may no longer be relevant - or may become more relevant if there's a gremlin somewhere
If you find Plusnet DNS resolvers to be a problem then pick some other ones and either set them in your Router or in your OS IP Config.
@Townman
Have you actually tried turning off Spoofing?
Quote from: Kelly I didn't have time to read the thread, so I just used Googles DNS which got around the issue.
I'm flagging it up with Matt again today though.
Quote from: Townman Kelly,
Thanks for that - much appreciated. I have made direct approaches to people in products asking for this to be examined, but I have not received a reply on the matter.
Kelly, getting any feedback from Products regarding any Modem/Router firmware issues seems to be a problem these days (apart from one very helpful individual) which makes it virtually impossible to help a variety of people with their problems from time to time, so I have virtually given up.
AO,
Thanks for the recap! I've now modified my router to turn off spoofing and will wait to see what happens.
I remain unconvinced though that the mater is quite as crystal clear as implied. There is something still less than clear about the spoofing process which ought to be explored by PlusNet products...
- what causes an address t become spoofed?
- under what conditions will it be "given out" even though a resolution is available from the DNS server?
- under what conditions will a spoofed address be correctly resolved?
On the last point (before updating / clearing the list) spoofed URLs were not having the spoofed address returned to applications (post ipconfig /flushdns) which implies that a full DNS lookup was performed and was successful.
As ejs suggests may be I need to find some free time and run up Wireshark - though I rather think PlusNet ought to be in a better position to do this.
Thanks for the recap! I've now modified my router to turn off spoofing and will wait to see what happens.
I remain unconvinced though that the mater is quite as crystal clear as implied. There is something still less than clear about the spoofing process which ought to be explored by PlusNet products...
- what causes an address t become spoofed?
- under what conditions will it be "given out" even though a resolution is available from the DNS server?
- under what conditions will a spoofed address be correctly resolved?
On the last point (before updating / clearing the list) spoofed URLs were not having the spoofed address returned to applications (post ipconfig /flushdns) which implies that a full DNS lookup was performed and was successful.
As ejs suggests may be I need to find some free time and run up Wireshark - though I rather think PlusNet ought to be in a better position to do this.