UDP network question

[death pax]

Ive been looking through the help file at the udp network functions and from what i have seen its possible to specify the destination port, but not the source port, I am trying to connect to my game server and recieve a status message from it. So i was wondering if anyone could tell me how to set the sourceport, thnx in advance

Edited February 9, 2006 by death pax

[greenmachine]

It appears that UDPBind() does what you're looking for. Helpfile info for UDPBind: Create a socket bound to an incoming connection.

Your destination port would then be declared with UDPOpen(), which says this: Open a socket connected to an existing server.

Edited February 9, 2006 by greenmachine

[Helge]

I'm interested in what game you're talking about, because I've done some

small tests with a game myself and I'm thinking of putting them on my fileman...

[death pax]

Its for an unreal engine game, the original Unreal, incidentally

[death pax]

ive tried several things with it, but udp bind seems to specify what port to listen for data on, not what port to send data through... im starting to wonder if it wouldnt be easier to find the dllcalls for winsock

[death pax]

heres my code:

#include <Array.au3>
$IP_Server = "66.148.81.124"

UDPStartup()
$socket=UDPBind(@IPAddress2,2000)
_ArrayDisplay ( $socket, "Server" )
If $Socket = -1 Then Exit
$sendsocket=UDPOpen($IP_Server,9978)
_ArrayDisplay ( $sendsocket, "Client" )
If $sendSocket = -1 Then Exit
    
$bytes=UdpSend($sendsocket,"/info/")
msgbox(1,"bytes",$bytes)
while 1
    $data=UDPRecv($socket,100)
    If $data <> "" Then
        ConsoleWrite($data)
    EndIf
    sleep(100)      
WEnd
Func OnAutoItExit()
    UDPCloseSocket($socket)
    UDPCloseSocket($sendsocket)
    UDPShutdown()
EndFunc

ive checked this from packet sniffer and its still sending that data on a random port, in this case it was port 2222

x.x

[flaxcrack]

I'm interested in what game you're talking about, because I've done some

small tests with a game myself and I'm thinking of putting them on my fileman...

I have a question about this as well.... Is it possible to recieve game packets analize them and redirect them back to the appropiate port with AutoIT? I would really like to analize some information before it hits the game client on my machine.

[death pax]

probably not without c++

and more on the point, does anyone know how to set the source port?

[flaxcrack]

probably not without c++

and more on the point, does anyone know how to set the source port?

UDPBind

--------------------------------------------------------------------------------

Create a socket bound to an incoming connection.

;SERVER!! Start Me First !!!!!!!!!!!!!!!
$g_IP = "127.0.0.1"

; Start The UDP Services
;==============================================
UDPStartUp()

; Create a Listening "SOCKET"
;==============================================
$socket = UDPBind($g_IP, 65432)
If @error <> 0 Then Exit

Taken from the help file.

[death pax]

#include <Array.au3>
$IP_Server = "66.148.81.124"

UDPStartup()
$socket=UDPBind(@IPAddress2,2000)

I already had that and it isnt working

[The Kandie Man]

Are you trying to send messages to the to the script within the script? I am not sure what you are doing. The reason it may not be working if you are in fact trying to do this is because the UDPBind () and the UDPSend() don't seem to have the same IP or port number. This is obvious, but i thought i just might point it out. Is there another script you are also using?

Here is a version that works if you are just trying to send UDP packets to the script itself:

#include <Array.au3>
;~ $IP_Server = "66.148.81.124"
$IP_Server = @IPAddress1

UDPStartup()
$socket=UDPBind(@IPAddress1,2000)
_ArrayDisplay ( $socket, "Server" )
If $Socket = -1 Then Exit
;~ $sendsocket=UDPOpen($IP_Server,9978)
$sendsocket=UDPOpen($IP_Server,2000)
_ArrayDisplay ( $sendsocket, "Client" )
If $sendSocket = -1 Then Exit
    
$bytes=UdpSend($sendsocket,"/info/")
msgbox(1,"bytes",$bytes)
while 1
    $data=UDPRecv($socket,100)
    If $data <> "" Then
        ConsoleWrite($data)
    EndIf
;~   sleep(100)     
WEnd
Func OnAutoItExit()
    UDPCloseSocket($socket)
    UDPCloseSocket($sendsocket)
    UDPShutdown()
EndFunc

[death pax]

No, this is an external game server. the script would send \info\ to the game server, then the server should send back the response on the same port number that the script sent the \info\ on (provided it is within the the port range 2000-2500 or something like that), this is why i need to designate the source port to use

Edited February 10, 2006 by death pax

[death pax]

x.x im at my wits end... i think ill start researching dllcalls for winsock... maybe that will help me...

[flaxcrack]

x.x im at my wits end... i think ill start researching dllcalls for winsock... maybe that will help me...

Why UDP and not TCP?

[death pax]

Because that is what protocol the game uses, its not like i can change it

[PsaltyDS]

Because that is what protocol the game uses, its not like i can change it

I am not absolutely sure about this, but I think you are up against the UDP spec, as implemented in Windows' IP stack. UDP being a connectionless "packet lite" kind of protocol uses any send port of opportunity by design, IIRC. Controlling the source port might be equivelent to writing a new IP stack.

[death pax]

ugh>.<, then is there anyway of telling what source port it used?, because if i can tell what source port it used, i could test and see if the recieving data is incoming on that port

[theguy0000]

whats an IP stack?

[PsaltyDS]

whats an IP stack?

The software modules that handle the various layers of the OSI seven layer model. The whole thing is the "TCP/IP Stack", and layers three and below are the "IP stack". Port addressing is actualy higher than layer three and so I should have said "TCP/IP Stack".

UDP ports are at layer four, and the source port is an optional field.

My point was that the source port is usually considered irrelevant in UDP (of course the destination port is critical). I have not used AutoIT UDP capabilities at all, but assuming it uses calls to Windows' included TCP/IP stack, you may not have any control or access to UDP source ports. I'm not an expert though, and always ready to be corrected.

[death pax]

ugh, maybe i should just use another programming language then... or see if i can use DllCall with winsock.dll