Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: A strange IP address in my network!!

  1. #11
    My life is this forum thorin's Avatar
    Join Date
    Jan 2010
    Posts
    2,629

    Default

    Well I might make the following shade of grey suggestion. IANAL but I'd argue the following.

    192.168.x.x falls within RFC1918 therefore you should have no exectation of it being a remote system (you should fully expect it to be local) therefore knowing that it has telnet running there's no reason you shouldn't attempt to telnet to the device/system. If once you telnet you receive a banner saying "authorized people only...." kind thing then obviously disconnect but the telnet banner might give you some useful info as to who/what the device/system is.

    @ Gitsnik et al re: Law WRT port scanning etc
    The following might help:
    Canadian Criminal Code (C-46, Code Section 326) Theft of Telecomunication Services
    Canadian Criminal Code (C-46, Code Section 430) Mischief in relation to data
    State Hacking Laws
    10 ways you might be breaking the law with your computer
    I'm a compulsive post editor, you might wanna wait until my post has been online for 5-10 mins before quoting it as it will likely change.

    I know I seem harsh in some of my replies. SORRY! But if you're doing something illegal or posting something that seems to be obvious BS I'm going to call you on it.

  2. #12
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    12

    Default

    But what if you think this device maybe the embedded telnet application in some of your machines? Thats why you do trace route.

    Quote Originally Posted by thorin View Post
    Well I might make the following shade of grey suggestion. IANAL but I'd argue the following.

    192.168.x.x falls within RFC1918 therefore you should have no exectation of it being a remote system (you should fully expect it to be local) therefore knowing that it has telnet running there's no reason you shouldn't attempt to telnet to the device/system. If once you telnet you receive a banner saying "authorized people only...." kind thing then obviously disconnect but the telnet banner might give you some useful info as to who/what the device/system is.

    @ Gitsnik et al re: Law WRT port scanning etc
    The following might help:

  3. #13
    Good friend of the forums spawn's Avatar
    Join Date
    Jan 2010
    Posts
    280

    Default

    Quote Originally Posted by streaker69 View Post

    Chances are, your ISP is doing some funky NAT work using the 192.168.x.x network
    I agree too

  4. #14
    My life is this forum thorin's Avatar
    Join Date
    Jan 2010
    Posts
    2,629

    Default

    Quote Originally Posted by generaluser View Post
    But what if you think this device maybe the embedded telnet application in some of your machines? Thats why you do trace route.
    If I thought it was one of my machines (which is a reasonable assumption based on RFC1918 address space), I'd simply go ahead and connect. No need to traceroute.
    I'm a compulsive post editor, you might wanna wait until my post has been online for 5-10 mins before quoting it as it will likely change.

    I know I seem harsh in some of my replies. SORRY! But if you're doing something illegal or posting something that seems to be obvious BS I'm going to call you on it.

  5. #15
    Just burned his ISO
    Join Date
    Oct 2009
    Posts
    10

    Default Well

    Considering the ports, Ip and data received that most probably is Wifi acces point.
    And about port scanning in finland that is a criminal offense equal to tresspassing.
    running actual exploits would be = to breaking an entry.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •