Re: [Agnx80211driver-devel] tcpdump report access google with delay mode via ethernet

[YanBo <dre...@gm...>]

>
> On Dec 23, 2007 2:03 PM, YanBo <dre...@gm...> wrote:
> >
> >
> >
> > On Dec 23, 2007 12:45 PM, far seer <se...@gm...> wrote:
> > > YanBo,
> > > Below is tcpdump report, though google does not send fin package after
> three
> > > handshake.
> > >
> > > 12:41:19.157286 IP 192.168.1.122.50637 > jp-in-f147.google.com.http: S
> > > 2707899440:2707899440(0) win 5840 <mss 1460,sackOK,timestamp 500377
> > > 0,nop,wscale 4>
> > > 12:41: 19.267147 IP jp-in-f147.google.com.http > 192.168.1.122.50637: S
> > > 3578420469:3578420469(0) ack 2707899441 win 5672 <mss
> 1430,sackOK,timestamp
> > > 3714633827 500377,nop,wscale 6>
> > > 12:41:19.267183 IP 192.168.1.122.50637 > jp-in-f147.google.com.http: .
> ack 1
> > > win 365 <nop,nop,timestamp 500487 3714633827>
> > > 12:41:20.267347 IP 192.168.1.122.50637 > jp-in-f147.google.com.http: P
> > > 1:32(31) ack 1 win 365 <nop,nop,timestamp 501487 3714633827>
> > > 12:41:20.377030 IP jp-in-f147.google.com.http > 192.168.1.122.50637: .
> ack
> > > 32 win 89 <nop,nop,timestamp 3714634938 501487>
> > > 12:41:20.419030 IP jp-in-f147.google.com.http > 192.168.1.122.50637 : .
> > > 1:1419(1418) ack 32 win 89 <nop,nop,timestamp 3714634974 501487>
> > > 12:41:20.419041 IP 192.168.1.122.50637 > jp-in-f147.google.com.http: .
> ack
> > > 1419 win 546 <nop,nop,timestamp 501639 3714634974>
> > > 12:41:20.424256 IP jp-in-f147.google.com.http > 192.168.1.122.50637: .
> > > 1419:2837(1418) ack 32 win 89 <nop,nop,timestamp 3714634974 501487>
> > > 12:41:20.424291 IP 192.168.1.122.50637 > jp-in-f147.google.com.http : .
> ack
> > > 2837 win 727 <nop,nop,timestamp 501644 3714634974>
> > > 12:41:20.428219 IP jp-in-f147.google.com.http > 192.168.1.122.50637: P
> > > 2837:4255(1418) ack 32 win 89 <nop,nop,timestamp 3714634974 501487>
> > > 12:41:20.428249 IP 192.168.1.122.50637 > jp-in-f147.google.com.http: .
> ack
> > > 4255 win 908 <nop,nop,timestamp 501648 3714634974>
> > > 12:41:20.532164 IP jp-in-f147.google.com.http > 192.168.1.122.50637 : .
> > > 4255:5673(1418) ack 32 win 89 <nop,nop,timestamp 3714635087 501639>
> > > 12:41:20.532218 IP jp-in-f147.google.com.http > 192.168.1.122.50637: FP
> > > 5673:5675(2) ack 32 win 89 <nop,nop,timestamp 3714635087 501639>
> > > 12:41:20.532279 IP 192.168.1.122.50637 > jp-in-f147.google.com.http : .
> ack
> > > 5673 win 1089 <nop,nop,timestamp 501752 3714635087>
> > > 12:41:20.532380 IP 192.168.1.122.50637 > jp-in-f147.google.com.http : F
> > > 32:32(0) ack 5676 win 1089 <nop,nop,timestamp 501752 3714635087>
> > > 12:41: 20.643053 IP jp-in-f147.google.com.http > 192.168.1.122.50637: .
> ack
> > > 33 win 89 <nop,nop,timestamp 3714635203 501752>
> > >
> > >
> > Hi far.
> > For the agnx card, google send fin packet because after finished three
> > handshake,  it wait for a while but still can't receive the http
> > request from the client, so it think this tcp session is timeout,
> > hence it sent the fin packet to terminal this tcp session, but in
> > above situation google get the correctly http request after three
> > handshake, so it will not send fin packet.
> >
> > lyb
> >
>
>
On Dec 23, 2007 2:09 PM, far seer <se...@gm...> wrote:
> The case is delaying 1s to submit http request after three handshake. If so,
> google server should timeout too. The http_get code is like:
> // connect to google server
> // sleep(1)

Please try sleep(10) or sleep(20).

> // send the http request to google server (this is a get command, just
> request default web)
>
>
lyb