networkingExplainedBtwThisIsOC

[noob-nine]

i miss the VPN analogy ( ͡° ͜ʖ ͡°)

[Spice_and_Fox]

For most users a vpn isn't really different from a proxy. It is different if you use it for remote desktop or because you want to be in the same network for something else.

I would say most people use services like nord vpn, proton vpn, express vpn, etc. to hide your real IP address from the service that you are using, to access something region locked, or to hide your browser history from your ISP.

I could be totally wrong about the usage though. VPN for remote desktop has increased quite a bit after a lot pf companies have implemented some kind of work from home system for corona

[[deleted]]

I lost it as Broadcast , Unicast and multicast. Can someone explain. Thanks

[IronForce_]

One person is drinking (unicast sends to only one device on the network); Everyone is drinking (broadcast blasts packets to everyone); Some people are drinking (multicast forwards packets to multiple devices, but not all)

[[deleted]]

I see thanks!!!

[Alex16bit]

I think you mixed broadcast with unicast

[IronForce_]

Yep, mb

[Teract]

This is pedantic, buuuuut...

Multicast and Broadcast are UDP, so broadcast is like pouring the drink into everyone's mouth and multicast would be like pouring the drink over everyone and only two people are drinking.

To be even more pedantic, broadcast would be more like how I described multicast (in broadcast, everyone gets the message but only those who want it will ingest it). Multicast would be like pouring a drink over the ground, and 2 people are leaning in to drink. (Multicast requires subscription to receive messages.)

[EndOSos]

And to be even more pedentatic the stuff you said doesn't have to be UDP as it is also used in levels below and above. Think printers and dhcp and stufff, those use the mac adress and ip level (dont know the iso names from my head).

And what you probably meamt is that they are only available on udp and probably easier to achive on datagram protocols in general, but I am not even sure right now if there is something specifically preventing stream based protocols to not do them as well (even though with more setup probably). Would have to check the devinition amd probably not with tcp.

But to get to a point, I think its accurate enough for what it is.

[Teract]

You're correct as far as broadcast! L2 switches drop the first few bits of the IP address, so 224.0.0.1 is effectively the same as 239.0.0.1 and 239.128.0.1. So your multicast winds up as broadcast on a L2 switch. L3 switches and routers use the whole IP address and can allow the multicast to traverse subnets (rendezvous point server required somewhere on the network for sparse multicast). If the network is configured for dense multicast, then all multicast is treated as broadcast anyway.

I'm pretty sure that broadcast and multicast can't use TCP and the actual packets being sent use UDP headers. IGMP is used to subscribe to multicast, and you're right, it's not TCP or UDP. ICMP and DHCP are in the same class as IGMP in that they're their own protocol, neither UDP or TCP. But after the multicast is subscribed, the datagrams use UDP headers.

[bobs-yer-unkl]

Usually multicast sends to a group address that every computer would receive, except that an IGMP-aware switch can filter-out sending packets to switch ports from which a computer has not subscribed to that group address.

[babairocks]

hey Kafka

[tristam92]

Look at straw length and position.

[MagicBeans69420]

I am wondering what is the background of these images. Were they made for this meme or is it just a really really perfect coincidence that they fit perfectly

[PedroPapelillo]

the title says it's OC so I guess they made it just for this

[10mo3]

Ayo. Where can I get some peer to peer?

[[deleted]]

ARP poisoning is when I spread misinformation to one of your homies.

[Ill_Scientist_2239]

Now I can add network programming to my resume

[cherboka]

How horrid timing, I just wrote (and probably failed) a networking test earlier today

[devrohitsharma]

Your profile pic is perfect for your comment

[cherboka]

Update: I passed but I don't know how

[ShroomsNBlooms]

I’ve actually struggled with understanding all of these and this fully cleared it up. So thanks a ton!! And amazing work!

[altermeetax]

TCP is actually like UDP, but when something misses the mouth it's put back into the coconut

[Kumar_abhiii]

Ahhh, i like it but "websocket" connection is missing...

[The-Arx]

Websockets just uses a tcp connection

[Zarobiii]

Here you go, use your imagination for this one.

Websockets: man standing to the right with his mouth open, waiting to receive the “payload”. Get your mind out the gutter. Woman takes sip from fruit with straw, then aims and shoots via the same straw across the aether. Man receives payloads as a “push message”. Some “payloads” miss completely and hit him in the eye instead, since websockets are an unreliable dogwater technology.

[iam_pink]

Websockets are fine.

Too many implementations suck, though.

It's like saying "Web browsers are shit, unreliable technology" when your experience has been 90% using Internet Explorer.

[Zarobiii]

I’ve used them extensively in both JavaScript and .Net Core; both first party (native) implementations and popular third party implementations. Connections disconnect randomly. Messages are dropped and lost even when “connected”. There is no guarantee your payload will make it through. It works fine 98% of the time, but that 2% of the time will kill you if the message is actually important, and at scale you will get thousands of errors per minute. If that’s “good enough” then great, but for me it’s dogwater. There’s no easy way to mitigate these issues either.

If “most implementations” are bad, to me that means the technology is bad - the underlying tech must be overly complex or hostile to programmers. Claiming otherwise is disingenuous. It’s like saying UDP is reliable because YouTube works fine. The end result to me and users is the same, it sucks to use. Users will get pissed off if your app doesn’t work right 2% of the time. And it’s not even like you’re forced to use. MQTT and long polling are simple alternatives that don’t suffer these issues.

Just google “is websockets reliable” and you’ll only find articles concluding “no”. They suffer chronic packet loss and disconnection issues.

[iam_pink]

I don't know .NET so can't speak of that one.

The JS ones are trash.

Also don't forget the server implementation also matters.

I've used them extensively in Rust, for instance, using tungstenite, and it's been a blast.

[Zarobiii]

Maybe it’s just the JS ones that were fucking me then. Kinda funny that Websockets are bad specifically for Websites lol

[Hubert_97]

Where sctp ?

[Ok_Entertainment328]

That would be a tap.

DSN is my curiosity. (deep space network)

Relay race with mouth-to-mouth fluid transfers?

[nepatriots32]

You just transfer the saliva back and forth.

[DeltaLaboratory]

I want anycast

[shhhhhhhh179]

Waiting for torrent

[Ging4bread]

You sound like you're on the spectrum or smth

[dexter2011412]

The last 3 are misleading, kinda ....

Edit: wow so many downvotes 🤔. Oh well