Re: Building ayttm 0.6.3 (current git version) on Fedora 23 x86_64
Philip Tellis <[email protected]> Wed, 30 Mar 2016 11:28:55 -0400
| Newsgroups | gmane.network.instant-messaging.ayttm.user |
|---|---|
| Message-ID | <CAJ4Gv_Z3qg-JXm1gyWtkfJ+dp1o_Ub1cEPyneoD2c629huNXQg@mail.gmail.com> |
--===============2744848497522637220== Content-Type: multipart/alternative; boundary=001a11471f86cdb150052f45cdf4 --001a11471f86cdb150052f45cdf4 Content-Type: text/plain; charset=UTF-8 On 30 Mar 2016 10:43 a.m., "Detlef Graef" <[email protected]> wrote: > > The following happens, described (simplified) in own words: > > > DNS query: vcs2.msg.yahoo.com type A ipv4 > DNS query: vcs2.msg.yahoo.com type AAAA ipv6 > > http request to: http://vcs2.msg.yahoo.com/capacity > > http Response: > COLO_CAPACITY=1 > CS_IP_ADDRESS=66.196.114.227 > > new tcp session to: 66.196.114.227 destination port 5050 > [snip] > > The difference seems to be in the http://vcs2.msg.yahoo.com/capacity > request. Connection to port 5050 is made to the ip address from > http://vcs2.msg.yahoo.com/capacity > Yes, it looks like they are now doing load balancing via the first request. This probably explains why you got a 999 by connecting to SCS. Changes will have to be made in libyahoo2, and if you do make those changes, then also submit them to the libyahoo2 project. Thanks for investigating. Philip --001a11471f86cdb150052f45cdf4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p dir=3D"ltr"><br> On 30 Mar 2016 10:43 a.m., "Detlef Graef" <<a href=3D"mailto:d= [email protected]">[email protected]</a>> wrote:<br> ><br> > The following happens, described (simplified) in own words:<br> ><br> ><br> > DNS query:=C2=A0 =C2=A0 =C2=A0 <a href=3D"http://vcs2.msg.yahoo.com">v= cs2.msg.yahoo.com</a>=C2=A0 =C2=A0 =C2=A0 type A ipv4<br> > DNS query:=C2=A0 =C2=A0 =C2=A0 <a href=3D"http://vcs2.msg.yahoo.com">v= cs2.msg.yahoo.com</a>=C2=A0 =C2=A0 =C2=A0 type AAAA ipv6<br> ><br> > http request to:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"ht= tp://vcs2.msg.yahoo.com/capacity">http://vcs2.msg.yahoo.com/capacity</a><br= > ><br> > http Response:<br> > COLO_CAPACITY=3D1<br> > CS_IP_ADDRESS=3D66.196.114.227<br> ><br> > new tcp session to:=C2=A0 =C2=A066.196.114.227=C2=A0 destination port = 5050<br> ><br> [snip]<br> ><br> > The difference seems to be in the <a href=3D"http://vcs2.msg.yahoo.com= /capacity">http://vcs2.msg.yahoo.com/capacity</a><br> > request. Connection to port 5050 is made to the ip address from<br> > <a href=3D"http://vcs2.msg.yahoo.com/capacity">http://vcs2.msg.yahoo.c= om/capacity</a><br> ></p> <p dir=3D"ltr">Yes, it looks like they are now doing load balancing via the= first request. This probably explains why you got a 999 by connecting to S= CS. </p> <p dir=3D"ltr">Changes will have to be made in libyahoo2, and if you do mak= e those changes, then also submit them to the libyahoo2 project. </p> <p dir=3D"ltr">Thanks for investigating. </p> <p dir=3D"ltr">Philip<br> </p> --001a11471f86cdb150052f45cdf4-- --===============2744848497522637220== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 --===============2744848497522637220== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ayttm-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ayttm-users --===============2744848497522637220==--