• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

IPPROTO_TCP vs IPPROTO_IP

J

jitspoe

Senior member
I have a server browser that downloads a list of server ip's from a website. It works fine for most people, but some individuals are having problems -- getting error codes like "WSAECONNABORTED". I whipped up a test app with libCURL, and that works, but I'm trying to keep the bloat down as much as possible (and libcurl like quadrouples the size of my executable). I followed through the code to see what curl did differently, and the key thing I noticed was that it used IPPROTO_IP for its call to socket() while I was using IPPROTO_TCP. Could somebody explain the difference between the two?
 
ip is addressing
tcp is transfer

so you pack the package in tcp, add ip to it so it knows where its going
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top