[Wine] Problem setting up a server on UDP port 59

Steve Ramm Steve.Ramm at imgtec.com
Mon Feb 9 11:24:13 CST 2009


Thanks, yes - running as root solves that problem but uncovers
another... actually in this case I can tell the program to use another
port & it is not a problem. 
I will report on the other issue when I have some sensible debug output.

Steve

-----Original Message-----
From: Austin English [mailto:austinenglish at gmail.com] 
Sent: 09 February 2009 17:19
To: Steve Ramm
Cc: wine-users at winehq.org
Subject: Re: [Wine] Problem setting up a server on UDP port 59

On Mon, Feb 9, 2009 at 10:35 AM, Steve Ramm <Steve.Ramm at imgtec.com>
wrote:
> I have a program that sets up a server on UDP port 59; it runs with no
> problem under windows XP. Under wine it fails, the log shows
"Permission
> denied" for the WS_bind function.
>
> Has anyone else seen this? Does anyone know how to work around this?
>
>
>
> trace:winsock:WSAStartup succeeded
>
> trace:winsock:WS_socket af=2 type=1 protocol=0
>
> trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW      created 0048
>
> trace:winsock:WS_bind socket 0048, ptr 0x32fbec { family 2, address
> 127.0.0.1, port 0 }, length 16
>
> trace:winsock:WS_listen socket 0048, backlog 3
>
> trace:winsock:WS_getsockname socket: 0048, ptr 0x32fc0c, len       10
>
> trace:winsock:DllMain 0x7ee60000 0x2 (nil)
>
> trace:winsock:WS_socket af=2 type=1 protocol=0
>
> trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW      created 0054
>
> trace:winsock:WS_connect socket 0054, ptr 0x7e85169c { family 2,
address
> 127.0.0.1, port 56208 }, length 16
>
> trace:winsock:DllMain 0x7ee60000 0x3 (nil)
>
> trace:winsock:WS_select read 0x8210b0, write (nil), excp (nil) timeout
> 0x32fb9c
>
> trace:winsock:__WSAFDIsSet (72,0x8210b0(1))
>
> trace:winsock:WS_accept socket 0048
>
> trace:winsock:WS_getpeername socket: 004c, ptr 0x32fbfc, len 00000010
>
> trace:winsock:WS_closesocket socket 0048
>
> trace:winsock:WS_select read 0x8210b0, write (nil), excp (nil) timeout
> 0x32fb6c
>
> trace:winsock:WS_socket af=2 type=2 protocol=0
>
> trace:winsock:WSASocketA af=2 type=2 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW af=2 type=2 protocol=0 protocol_info=(nil)
> group=0 flags=0x1
>
> trace:winsock:WSASocketW      created 0048
>
> trace:winsock:WS_bind socket 0048, ptr 0x32fbe4 { family 2, address
> 0.0.0.0, port 59 }, length 16
>
> warn:winsock:WS_bind failure - errno = 13
>
> warn:winsock:wsaErrno errno 13, (Permission denied).
>
> trace:winsock:WS_closesocket socket 0048
>
> -
> This message is subject to Imagination Technologies' e-mail terms:
http://www.imgtec.com/e-mail.htm
> -
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
http://www.winehq.org/pipermail/wine-users/attachments/20090209/466a04e6
/attachment.htm
>

Port 59 is reserved for root on Linux.

You could use POSIX capabilities to work around it, or install/run the
program as root (not recommended for most apps, except circumstances
like these, because it gives the application access to your entire
system).

-- 
-Austin
-
This message is subject to Imagination Technologies' e-mail terms: http://www.imgtec.com/e-mail.htm
-




More information about the wine-users mailing list