Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,597 of 14,669    |
|    Jorgen Grahn to Elton    |
|    Re: Solicited vs. Unsolicited TCP/IP pac    |
|    16 Sep 10 18:56:06    |
      5f79101a       From: grahn+nntp@snipabacken.se              On Thu, 2010-09-16, Elton wrote:       >> Sure, but that blocks a lot of traffic that may well be requested by       >> something you did on your end. It's comparable to ISP's that block       >> "spoofed traffic", but what they mean by "spoofed" is not that the       >> origin is invalid or incorrect but simply that it's not the one *they*       >> assigned. Shoot at the wall, towards the target, and call whatever you       >> can hit the bullseye.       >       > So TCP SYNs can also be the result of a request by me, and a new       > connection starts to create as a result of this request.              Yes!              > But then how do ISPs find out if it was a packet sent to me as a       > result of a request (solicited packet), or if they are TCP SYN packets       > sent to my computer without I requesting it (unsolicited packets) ?              Well, like Morten writes elsewhere in the thread, they can't. Unless       they get to define the meaning of "solicited" on your behalf.              (By the way, I have never heard of ISPs that do crazy stuff like       that.)              /Jorgen              --        // Jorgen Grahn |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca