|
|
|
NetSafeChris: But this would suggest the firmware in the box itself - something the average home user simply plugs in and hopes for the best with - is the issue, leaving ports open that allows DNS resolving to use traffic on their account. Have I absorbed the 2 page thread correctly?
NetSafeChris: So how do we convey blocking ports and setting up a DMZ to the average home user? Or should the home user only use the modem the ISP delivers and hopefully has tested and secured?
Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies
Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.
NetSafeChris: I saw Juha Saarinen tweet this link and am intrigued by the flaw you identify for the increased data usage.
At NetSafe we had this issue raised by a new Orcon customer and there was absolutely no reason for the massive rise in data usage - no sign of malware at all, no sharing of passwords with house guests, good encryption and long passphrase - all the standard consumer security messaging we put out around wireless.
But this would suggest the firmware in the box itself - something the average home user simply plugs in and hopes for the best with - is the issue, leaving ports open that allows DNS resolving to use traffic on their account. Have I absorbed the 2 page thread correctly?
So how do we convey blocking ports and setting up a DMZ to the average home user? Or should the home user only use the modem the ISP delivers and hopefully has tested and secured?
eXDee: Haven't found one with a simple test to your own IP without having to enter it, but there is probably one out there. You could possibly do this on your own website, wrapping it in a nice user friendly interface where they just press a button and it checks their connecting IP if it responds to DNS.
Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies
Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.
freitasm:eXDee: Haven't found one with a simple test to your own IP without having to enter it, but there is probably one out there. You could possibly do this on your own website, wrapping it in a nice user friendly interface where they just press a button and it checks their connecting IP if it responds to DNS.
https://www.grc.com/x/ne.dll?rh1dkyd2 and click Proceed. Then click Service Ports. No need to enter IP address.
darthmeow:freitasm:eXDee: Haven't found one with a simple test to your own IP without having to enter it, but there is probably one out there. You could possibly do this on your own website, wrapping it in a nice user friendly interface where they just press a button and it checks their connecting IP if it responds to DNS.
https://www.grc.com/x/ne.dll?rh1dkyd2 and click Proceed. Then click Service Ports. No need to enter IP address.
Or go to https://www.grc.com and click shields up, proceed, all service ports. 9/10 with GRC now shields up won't load unless you go at it this way.
plambrechtsen: I would however like to know what its modem code is though.
If you could pm me and you are a Telecom customer email me and we could do a quick line test with it and I can grab the necessary numbers at our end.
eXDee:
DNS is port 53 UDP not TCP. I think its better to specifically check that a recursive resolver is responding to queries rather than a simple port test too, to result in less false positives.
kyhwana2:eXDee:
DNS is port 53 UDP not TCP. I think its better to specifically check that a recursive resolver is responding to queries rather than a simple port test too, to result in less false positives.
Actually, it's both. If UDP doesn't work for whatever reason (packet too large/fragments/UDP not working) it will fall back to using TCP port 53.
eXDee:kyhwana2:eXDee:
DNS is port 53 UDP not TCP. I think its better to specifically check that a recursive resolver is responding to queries rather than a simple port test too, to result in less false positives.
Actually, it's both. If UDP doesn't work for whatever reason (packet too large/fragments/UDP not working) it will fall back to using TCP port 53.
Good point actually, though you want to test for 53 UDP at least/as well, i wouldn't be satisfied with a TCP only check.
Psi:plambrechtsen: I would however like to know what its modem code is though.
If you could pm me and you are a Telecom customer email me and we could do a quick line test with it and I can grab the necessary numbers at our end.
Telecom already know. They are investigating 5 other users with tenda modems and similar issues.
see my first post on page 1
|
|
|