Nice vid! A raw sockets video would be super! Also, it would be awesome to do a deep dive into the network stack, perhaps sk_buff?
@rico_1617Ай бұрын
Legend, literally posted this the day my networking course starts and there's an assignment with UDP lol
@mehregankbiАй бұрын
Would love a video about unix and raw sockets.
@Barakatic2 ай бұрын
Very nice repeating so keep formula solid in your mind with time .
@BLSrr2 ай бұрын
Testing can also be done with socat or nc, both sending and receiving.
@Albert-yd1wh2 ай бұрын
I think it is useful to include continuous receiving packets in the tutorial. Because it is used more often than receiving a single packet.
@esrx7a2 ай бұрын
Super, is TCP coming up?
@JacobSorber2 ай бұрын
I have a few stream socket examples that use TCP. Or are you hoping for a deep dive into the details of TCP?
@esrx7a2 ай бұрын
@@JacobSorber TCP demystified
@ahmadshami58472 ай бұрын
Cool video, but I've been always curious about the different ways to handle data coming through the network when it is larger than the defined the buffer. I do have an idea about maybe using fgets whith stdin for example to handle undefined data size but idk if it's the same case with data coming through a network socket.
@gunar3939Ай бұрын
Need socket timeout also other method to remove blocking functionality
@LarryEvilsizer2 ай бұрын
Thanks for your videos. My current main project is a network simulator so I'm generally interested in socket examples. I'm wondering what happened to the datagram sent around 11:10? It wasn't received by the receiver program.
@CosmicCoder2 ай бұрын
I was wondering the same thing. Perhaps they were on different instances of virtual machines?
@Gr4cer2 ай бұрын
That's the beauty of UDP, it's "fire-and-forget". So you can just blast UDP pakets into the void, if theres no one listening, the message is just discarded by any connected node. Even though, as a sender you'll never know if someone or anyone has received the UDP paket. While TCP is doing a lot of handshakes such like regular heartbeats to check if the peer is still alive and connected, an acknowledge for each sent packet, packet resend features etc. which cause some overhead but UDP does none of those things on UDP-Protocol level. Many Applications that use UDP do have some counter included in their procotol so the receiving application can notice if there was a packet dropped.
@CosmicCoder2 ай бұрын
@Gr4cer Ah! If there is no "active" listener bound to the port, the datagram is just discarded.
@LarryEvilsizer2 ай бұрын
@@CosmicCoder Thank you very much for your response
@LarryEvilsizer2 ай бұрын
@@Gr4cer Thanks for your response and excellent explanation.
@MathematicsStudent2 ай бұрын
I seem to remember reading somewhere that connect can still be called for datagram sockets and that it has the effect of setting the default address for sending on that socket. Is that true?
@JacobSorber2 ай бұрын
It is, indeed. I personally don't love using connect with UDP sockets, because it seems (at least to me) to imply a connection (like you have with TCP) where there isn't one. Could confuse some people reading the code, but yes, it does work that way.
@adsfaedaer2 ай бұрын
++(wire shark)
@AaronMatlock2 ай бұрын
The check in this example needs to close the socket.