UDP source port number when using RAW socket??

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
Hello Everyone

I have created an application that runs as a client on a ADSL modem
and communicates with a server on a Windows/MAC using as RAW socket
        sk = socket(PF_INET, SOCK_PACKET, htons(ETH_P_ALL));

With this socket I can send RAW data to the server that listens on
62828 . When I send I create my own ethernet, IP and UDP and send it
out on my eth0 interface. This all works fine and my server receives
the data correctly and responds. However now I have a question what
number to assign to my source port number on UDP when creating my
packet on the client??

From what I understand when using a UDP socket and having the network
stack creating the message the UDP source port number is taken from an
internal list. This ensures that no applications will select the same
port numbers when sending out data. But since I create my own packets
and send them out using RAW socket I can just give and number as UDP
source port number and I feel that this is not correct. If I am
unlucky I will create a conflict having 2 applications(my client) and
another one both sending out on the same port.

So my question is:
1) How do I get "hold" of a valid UDP port number that I can assign to
my RAW packet?
2) Is there some sort of API I can call and if so what?
3) What are the implications/problems if one for some reason have two
applications sending out data on the same port number?

Any input and advice is greatly appreciated.


Re: UDP source port number when using RAW socket??
Quoted text here. Click to load it

Why are you bothering with raw packets if you're redoing all of the
work that the IP and UDP code does?

Quoted text here. Click to load it

Maintain the same list, like the UDP code does.

Quoted text here. Click to load it

Probably not.

Depends on the protocol.  If the other end uses the port you're sending
from as a place to send its data, you'll have to figure out how to
differentiate the two types of traffic.  If the remote has a hardcoded
port that it sends to, then it doesn't matter what source port you
Steve Watt KD6GGD  PP-ASEL-IA          ICBM: 121W 56' 57.8" / 37N 20' 14.9"
 Internet: steve @ Watt.COM                         Whois: SW32
We've slightly trimmed the long signature. Click to see the full one.

Site Timeline