W5500 Rules for changing UDP port numbers?
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: W5500 Rules for changing UDP port numbers?
by Coccoliso ·
Hi,
configurations are TX ie “client mode” or RX ie “server mode”.
In both cases, you should start from the condition of closed socket just because the buffer pointers must start from this condition.
In client mode performs a transmission to another peer and define your own output port, peer IP address and the receiving port.
In server mode you define your receiving port and the package that you receive in the first bytes contain the IP address of the peer and his receiving port.
I understand you want a server “active” once received a package change its port as it happens in some protocols like the remote run command (RPC) where the server uses a default port for receiving new client and then use a different port to establish flow data.
I think the easiest way is to use a second socket that it opens to the peer of a new random port … however the protocol must make from scratch because I have not seen such examples.