Member Avatar for jwala

I have a server to which clients are connected using TCP connection.

All the clients broadcast to each other using UDP braodcasting.I want to disconnect one of the client from the UDP connections from server.

what can be the possible ways to do this?

please suggest.

  • 3 Contributors
  • 3 Replies
  • 284 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by jwala

Dani AI

Generated

Following and , here are practical, concrete ways to achieve the effect of “disconnecting” one UDP-speaking client. UDP itself has no session to tear down, so you must either instruct the client to stop sending, or make the server/network ignore that client.

If you control the client (recommended): use the existing TCP control channel to tell the client to stop broadcasting and close its DatagramSocket (or leave the multicast group). That is clean and immediate:

// client stops broadcasting
udpSocket.close();

If you cannot rely on the client, implement server-side filtering. Keep a small ban list of IP/port (or application ID carried inside UDP payloads) and drop packets from banned entries before processing:

Set<SocketAddress> banned = Collections.synchronizedSet(new HashSet<>());
// receive loop
DatagramPacket p = new DatagramPacket(new byte[4096], 4096);
socket.receive(p);
SocketAddress src = new InetSocketAddress(p.getAddress(), p.getPort());
if (banned.contains(src)) continue; // drop silently
handlePacket(p);

Other approaches to consider:

  • Move to a server-relay model: clients send to server; server forwards only to authorized peers. Then “disconnect” = stop forwarding. This scales and gives server control.
  • If you used multicast, ask the client to leaveGroup(...) (server still cannot force it).
  • At host level you can drop packets from an IP/port (iptables / Windows Firewall) but that requires admin rights and is brittle with NAT/dynamic IPs.

Notes and cautions: blocking by IP/port can be spoofed; NAT may change source ports; multicast/broadcast behavior depends on the network. For stronger guarantees, use authenticated transport (DTLS/TCP + application-level tokens) so a banned peer cannot impersonate another client.

Recommended Answers

All 3 Replies

Member Avatar for masijade

Uhm, have that client close its socket?

Member Avatar for JamesCherrill

UDP is a connectionless protocol. What exactly do you mean by "disconnect the client" when there is no connection?

ps Are you thinking of the connect method in DatagramSocket? - that just simplifies the syntax for sending messages by pre-determining the addresses. From the server end you can ignore that. If you want, for some reason, the client to execute a disconnect() then I think you will have to make the server send a request to the client for the client to "disconnect". However, even if you do that the client can still send datagrams to the server, so if the intention is to prevent further messages from the server you will have to implement some kind of filter on the messages that he server receives.

Edited by JamesCherrill because: ps
Member Avatar for jwala

thank u that was really helpful

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.