Jump to content

gu3r1l9

Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by gu3r1l9

  1. side note : i dont believe in all that " Built-in Router Firewall STUFF" . i never had any problems bypassing them , so i usually disable them for my home network , by which im not allowing extra protocols that have many security vulnerabilities effect my connections . plus i usually use this connection for Gaming on Steam , for which using a cable works way better than wireless connections , as it could effect the stability of your ping etc . having said that , if you do not know how to protect yourself manually then u might put your trust in your device software firewall , which i would no
  2. yep , i agree with the most parts. the telnet client is disabled by default on windows 10 , but usually on the Router/Access points that have this feature , its enabled by default and thats why you get this notification in eset >> In order to deal with this issue you have to disable that feature from the web interface of your device AKA "modem settings" . but here`s the problem . when you connect a new device like a router etc , Eset Firewall blocks it by default . specially when you try to change the settings in your router web interface for which it require running certain
  3. thats what i was assuming but since Telnet is no joke i had to make sure . i`l let ya know if i find anything new about this issue.
  4. even tho im using it on a bridge mode , i have the lan dhcp enabled so the modem/router does do the routing automatically . i havent changed the private IP address of the device since i figured im not gonna use it on any wireless connection since i make sure im not getting any telnet attack , they tend to be a bit harsh u know , its not like you getting DDOS. i might have to check Tp Link emulator for this , linux is alot more helpful in these cases comparing to microsoft windows. the blue screen of death made the whole thing more complicated...
  5. first of all thank you for your reply . i did not know there`s a crack version for eset 12 . i do have a one year internet security license which i did paid in full . and about the telnet issue , i almost solved it . but i did get a blue screen in the process . driver power state failure to be exact altho i doubt if it had anything to do with the issue , it would be most likely related to my "killer control center" Driver app for wifi adapter i assume . i will look further into this and post the results in couple of hours.
  6. I recently bought a " Tp-Link Archer D2 (EU) " Router/Access point . im getting this fishy notification even tho the telnet is disabled in the windows , ALG and NAT are disabled in the router settings . currently im using it on bridge mode . i did rescan many times . im still getting this telnet notification and i get these blocked devices in my firewall everytime i connect my modem prior to connecting to internet . am i a victim of a telnet attack ? if not how can i fix this ? FYI : im living in Iran and like most ppl here im not running a Genuine windows 10 so i did exclude the
×
×
  • Create New...