Click here to Skip to main content
15,886,110 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: WSO CCC OTD 2022-02-02 Pin
Peter_in_27801-Feb-22 22:38
professionalPeter_in_27801-Feb-22 22:38 
GeneralRe: WSO CCC OTD 2022-02-02 Pin
pkfox1-Feb-22 23:05
professionalpkfox1-Feb-22 23:05 
GeneralRe: WSO CCC OTD 2022-02-02 Pin
Greg Utas2-Feb-22 0:30
professionalGreg Utas2-Feb-22 0:30 
GeneralRe: WSO CCC OTD 2022-02-02 - Winner Pin
Randor 1-Feb-22 22:40
professional Randor 1-Feb-22 22:40 
Generalnetwork security Pin
Calin Negru1-Feb-22 9:20
Calin Negru1-Feb-22 9:20 
GeneralRe: network security Pin
OriginalGriff1-Feb-22 9:28
mveOriginalGriff1-Feb-22 9:28 
GeneralRe: network security Pin
Calin Negru1-Feb-22 9:41
Calin Negru1-Feb-22 9:41 
GeneralRe: network security Pin
trønderen1-Feb-22 10:30
trønderen1-Feb-22 10:30 
OriginalGriff wrote:
two messages you sent to teh same server at the same time may take wildly different routes to get there.
Yeah, that is what my university textbook said, too.

If some swordfish decides to cut a transatlantic fiber cable, the automatic rerouting of IP packets in the Internet will ensure that all your packets immediately will be routed along alternate paths.

Uh, not. While that would be according to the principles - and you can easily set up a model network to "prove that it works that way, it doesn't work that way in practice. In theory, there is no difference between theory and practice, but in practice, there is.

In theory, every IP packet is routed independently, regardless of the routing of the previous packet (or the following one) between the same two endpoints, requiring a complete evaluation to be made by every single router for every single IP packet. In low-capacity you usually have no options: You have only a single line to your ISP; there is no significant routing decision to be made. Once the packet gets out on the highway, the routers handle millions of packets every second. There is no time to give each packet individual treatment. Every packet to the same destination - and for long hauls, we are not talking about end nodes, but end subnets, are routed exactly the same way, according to routing tables that are far more static, and far more manually managed, than internet people like to admit.

Certainly there is no galvanic connection between endpoints. Certainly the connection doesn't have a cable by itself. It doesn't even have a given timeslot to itself, the way phone connections had in the pre-ip-phone days. IP packets are statistically multiplexed on on huge capacity line. But for all practical purposes, they do all go on the same line, the same cable.

I guess that if you pay for five separate ISP connections, which are connected to five different backbone networks managed by five huge, competing companies each running their own transatlantic cables, and your local router distributes your packages evenly, evert fifth package to each ISP, you will succeed in breaking up your packet stream. Yet the five partial streams may be collected into one stream (although not ordered in sequence) long before the packets reach their destination. Unless your peer has a similar setup, you may expect the reply packets to come in on a single one of your five ISP connections.

Everything about distributing packets on separate links is perfectly well within TCP/IP standards, and any IP stack will handle it without problems. Yet, that is not how it normally operates today. For reasons of speed and performance, all packets follow the same route.
GeneralRe: network security Pin
englebart5-Feb-22 4:20
professionalenglebart5-Feb-22 4:20 
GeneralRe: network security PinPopular
dandy721-Feb-22 10:49
dandy721-Feb-22 10:49 
GeneralThe sticky is back Pin
Tony Hill1-Feb-22 8:07
mveTony Hill1-Feb-22 8:07 
GeneralRe: The sticky is back Pin
Eddy Vluggen1-Feb-22 9:48
professionalEddy Vluggen1-Feb-22 9:48 
GeneralRe: The sticky is back Pin
Sander Rossel1-Feb-22 21:28
professionalSander Rossel1-Feb-22 21:28 
Generalhow to handle my old modem? Pin
Southmountain1-Feb-22 7:55
Southmountain1-Feb-22 7:55 
GeneralRe: how to handle my old modem? Pin
Mike Hankey1-Feb-22 7:59
mveMike Hankey1-Feb-22 7:59 
GeneralRe: how to handle my old modem? Pin
Rick York1-Feb-22 8:00
mveRick York1-Feb-22 8:00 
GeneralRe: how to handle my old modem? Pin
MKJCP2-Feb-22 1:41
MKJCP2-Feb-22 1:41 
GeneralRe: how to handle my old modem? Pin
Mike Hankey2-Feb-22 1:53
mveMike Hankey2-Feb-22 1:53 
GeneralRe: how to handle my old modem? Pin
Kirk 103898212-Feb-22 8:02
Kirk 103898212-Feb-22 8:02 
GeneralRe: how to handle my old modem? Pin
dandy721-Feb-22 8:56
dandy721-Feb-22 8:56 
GeneralRe: how to handle my old modem? Pin
Southmountain1-Feb-22 10:13
Southmountain1-Feb-22 10:13 
GeneralRe: how to handle my old modem? Pin
dandy721-Feb-22 10:53
dandy721-Feb-22 10:53 
GeneralRe: how to handle my old modem? Pin
Peter_in_27801-Feb-22 12:11
professionalPeter_in_27801-Feb-22 12:11 
GeneralRe: how to handle my old modem? Pin
Wizard of Sleeves1-Feb-22 21:22
Wizard of Sleeves1-Feb-22 21:22 
GeneralRe: how to handle my old modem? Pin
rob tillaart1-Feb-22 22:25
rob tillaart1-Feb-22 22:25 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.