Find the answer to your Linux question:
Results 1 to 3 of 3
hi all, using local ssh port forwarding as follows: ssh -L [local_port]:[local_host]:[remote_port] [remote_machine] I found the local port 'binded' to IP 127.0.0.1: Example: local_port = 30999 # netstat -nlp | ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2009
    Posts
    2

    Listening on wrong ip - 127.0.0.1 vs. 0.0.0.0


    hi all,
    using local ssh port forwarding as follows:

    ssh -L [local_port]:[local_host]:[remote_port] [remote_machine]

    I found the local port 'binded' to IP 127.0.0.1:

    Example: local_port = 30999

    # netstat -nlp | grep 30999
    tcp 0 0 127.0.0.1:30999 0.0.0.0:* LISTEN 6977/ssh
    tcp 0 0 ::1:30999 :::* LISTEN 6977/ssh

    For certain reasons it is supposed to be bound to the IP: 0.0.0.0, so
    that my desired netstat should look like:

    # netstat -nlp | grep 30999
    tcp 0 0 0.0.0.0:30999 0.0.0.0:* LISTEN 6977/ssh
    ...

    any ideas how this could be achieved?
    tx in advance!

    Peter

  2. #2
    Just Joined! ManishSinha's Avatar
    Join Date
    Dec 2007
    Location
    Manipal,India
    Posts
    28
    If this post is answered then it would clear a lot of my confusions.

    When we bind a port, why is it shown bounded to 0.0.0.0 instead 127.0.0.0 ?
    I mean that the IP of the system is the latter, then why is 0.0.0.0 shown? I have read in my course book that 0.0.0.0 is used as a source address when sending ARP requests, not much has been taught apart from this usage of the address 0.0.0.0

  3. #3
    Just Joined!
    Join Date
    Mar 2009
    Posts
    2

    thread continued here:

    see groups.google.com and search for "Binding TCP ports"

  4. $spacer_open
    $spacer_close

Posting Permissions

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