Timeline for How a VPS processes an incoming packet (conceptually)
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 28, 2022 at 23:01 | comment | added | user7088941 | 2) "you could figure out that there are lots and lots of routes client -> multiple hops -> same AWS server -> individual servers" why would that indicate that it is an AWS erver - and how would you figure out that there are lots and lots of router? (Sorry if my questions are so basic, I'm still a beginner, trying to learn how different networking components fit together) | |
| Dec 28, 2022 at 22:59 | comment | added | user7088941 | Thanks for the insightful answer. I'm still puzzled by a few things: 1) "The VPS will have set up routing information just like a normal server would, except it has given the same routing information for many virtualised servers." So how does (say) AWS do the packet forwarding to my specific VPS instance? Does every VPS that receives (say) an http packet use a different socket internally (i.e. a packet for myawesomerents.com comes in on socket 80, but AWS redirects it to (say) socket 1234, where my VPS is sitting)? | |
| Dec 20, 2022 at 17:51 | history | answered | gnasher729 | CC BY-SA 4.0 |