commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jieryn (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NET-238) RCommandClient wrongly attempts to use local socket with priviledged port (specifically >511 && <1024)
Date Tue, 04 Nov 2008 20:00:48 GMT

    [ https://issues.apache.org/jira/browse/NET-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645059#action_12645059
] 

jieryn commented on NET-238:
----------------------------

Actually, correct that - I see that my source address port is 1023. Sorry, I read the wrong
line from netstat -a.

However, I am still not able to connect with the commons-net RLoginCommand client.

> RCommandClient wrongly attempts to use local socket with priviledged port (specifically
>511 && <1024)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NET-238
>                 URL: https://issues.apache.org/jira/browse/NET-238
>             Project: Commons Net
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Linux x86_64, Eclipse 3.4, commons-net-2.0
>            Reporter: jieryn
>
> I see a few instances of this around:
>         int localPort;
>         localPort = MAX_CLIENT_PORT;
>         for (localPort = MAX_CLIENT_PORT; localPort >= MIN_CLIENT_PORT; --localPort)
>         {
>             try
>             {
>                 _socket_ =
>                     _socketFactory_.createSocket(host, port, localAddr, localPort);
>             }
>             catch (SocketException e)
>             {
>                 continue;
>             }
>             break;
>         }
>         if (localPort < MIN_CLIENT_PORT)
>             throw new BindException("All ports in use or insufficient permssion.");
> Yet, this seems to be an error. I can manually issue the rlogin command on my shell and
everything just works. After doing it directly from my shell, a netstat -a reveals that I'm
using an unpriviledged port on my client side.... why is RCommandClient attempting to use
a priviledged port??

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message