Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 12 of 12
Originally Posted by gumaheru Actually on the server side don't put a src ip at first. Let's just see if there is any traffic coming in. So it would be ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Apr 2010
    Posts
    5

    Quote Originally Posted by gumaheru View Post
    Actually on the server side don't put a src ip at first. Let's just see if there is any traffic coming in. So it would be "tcpdump -i eth0:1"
    The responde to command tcpdump -i eth0:1 is

    10:36:42.338308 IP web.saresoft.com.ssh > 80.81.103.180.rapi: P 2331264:2331508( 244) ack 9985 win 8576
    10:36:42.338383 IP web.saresoft.com.ssh > 80.81.103.180.rapi: P 2331508:2331656( 14 ack 9985 win 8576
    10:36:42.355897 IP 80.81.103.180.rapi > web.saresoft.com.ssh: P 9985:10037(52) a ck 2314544 win 64091

    18340 packets captured
    18340 packets received by filter
    0 packets dropped by kernel

  2. #12
    Just Joined!
    Join Date
    Jun 2007
    Posts
    12
    Is this the output you got from the ssh attempt? If so then it looks like you are hitting the virtual nic. Time to run ssh in debug mode on the ssytem. Run another instance of sshd from the commmand line but make sure that you specific debug and another port.
    Example:
    /usr/sbin/sshd -d -p 1153

    Then try to connect with ssh to port 1153. You should see some output from the ssh debug session. Also have a tcpdump session on both ends just to watch the traffic. Make sure that you specify port 1153 on both tcpdumps. This should give you more then enough information on what is going on.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

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