[En-Nut-Discussion] HTTP problem

[Francois Rademeyer]

Hi Harald,

Thanks for the feedback.

> The providers we tried recently didn't route our browser
> requests via Intranet-DLS-Internet-GPRS-Ethernut.
You have to request a public IP from your provider as they all tend to have
the GPRS units behind a firewall.
They will most probably give you a new APN, username and password and then
also charge you for a static IP.

With a single html page and one picture I get an error almost every 5th
request.  My simple CGI pages have not given any problems yet.

I do have logging on the 2nd UART and also use ethereal on the browser side.

Regards,
Francois

----- Original Message -----
From: "Harald Kipp" <harald.kipp at egnite.de>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Wednesday, February 18, 2004 12:15 PM
Subject: Re: [En-Nut-Discussion] HTTP problem


> Hi Francois,
>
> HTTP adds some difficulties like parallel connections
> and connects/disconnects at high rates. All applications we
> tested with GPRS had been single connections, established
> for a longer period.
>
> What I can say is, that troughput is no real problem, PPP
> seems to work quite reliable at higher data rates. But
> parallel connections may disclose bugs, which had been
> undiscovered during our test.
>
> The providers we tried recently didn't route our browser
> requests via Intranet-DLS-Internet-GPRS-Ethernut. So we
> only tested connecting the other way round, GPRS->DSL.
> No idea, why this is routed and DSL->GPRS isn't, because
> from the IP layers view there is no difference. Modern
> routers are quite intelligent, though.
>
> So this test would require to write a specific application,
> a multiconnect client, which we don't have right know.
>
> I'd welcome, if you are able to further investigate the
> problem. You can trace Ethernut's TCP traffic, but it
> requires to have the second UART connected. Let me know,
> if we can help in any way.
>
> Regards,
> Harald
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>