drew137
Well-Known Member
You can disable it which I have done, not really interested in someone else managing my router
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
Telkom D-Link modems causing Internet connection problems
drew137
Well-Known Member
So I upgraded my Telkom Dlink router to retail firmware version 1.70 and changed all the access passwords as indicated, disabled the TR-069 found in Advanced-> Network Tools-> TR-069 and so far my connection has been up for 12 hours no disconnects as before.
See screenshots... Still some intrusions but not much I can do about that I guess at least the connection is stable.
See screenshots... Still some intrusions but not much I can do about that I guess at least the connection is stable.
Attachments
Bern
Expert Member
You can disable it which I have done, not really interested in someone else managing my router
Good to know you can, some of the firmware implementations don't allow you to - haven't seen how Telkom has done theirs.
Drew not everything your router identifies as a kernel intrusion is a hack attempt.
You may have software on your system that you have allowed (knowingly or not) to probe specific ports, and that is what your router may be detecting.
There is a way, to block those probes on your router, by blocking the IP you suspect as being a hacker. Have a look in the log, trace route the destination and source IP of each event.
Use IP filtering , generally you would not block IPs that belong to your own ISP, generally...as they should not be hacking into your router.
One at a time.
You may have software on your system that you have allowed (knowingly or not) to probe specific ports, and that is what your router may be detecting.
There is a way, to block those probes on your router, by blocking the IP you suspect as being a hacker. Have a look in the log, trace route the destination and source IP of each event.
Use IP filtering , generally you would not block IPs that belong to your own ISP, generally...as they should not be hacking into your router.
One at a time.
Last edited:
drew137
Well-Known Member
DeSLAM, indeedy. The DST IP is always that of the router, I'll have another fiddle later this evening and hopefully there have been no disconnects during today :S