118765 - Slow loads under DHCP

Status: RESOLVED WORKSFORME

(NSPR :: NSPR, defect)

Description

[lecompte]

If I allow DHCP to get a lease, it takes 2 minutes for Warpzilla to
display the browser window upon startup.  If I supply the IP address
and default router automatically, this takes seconds.  It appears
to be related to the fact that OS/2 Warp does not initialize the
loopback interface automatically under DHCP; if I enable 127.0.0.1 
by hand, the load time is back to normal.

Still, it doesn't seem to me that waiting 2 minutes for 127.0.0.1 
to time out is what you want.

Comment 1

[Matthias Versen [:Matti]]

AFAIK Mozilla use 2 loopback connections itself.
CC Mkaply

Comment 2

[Erik Hensema]

The loopback should always run. Applications expect that. Sounds like an OS/2
bug to me.

Comment 3

[Mike Kaply [:mkaply]]

That's what I am thinking too, although a two minute timeout and then still 
functioning seems a little excessive.

Comment 4

[Mike Kaply [:mkaply]]

I disabled loopback on my OS/2 machine and the browser came up as normal.

I verified that loopback was disabled by pinging 127.0.0.1 and it failed.

Can trying bringing up your machine with a static IP and no loopback and see 
what happens?

Comment 5

[Mike Kaply [:mkaply]]

Do you have any updates for us?

Comment 6

[Mike Kaply [:mkaply]]

I'm going to close this one for lack of interest if I don't here anything more.

Please see my updates about my experience with loopback.

What version of OS/2 are you on?

Comment 7

[Mike Kaply [:mkaply]]

Closed for lack of response. Please reopen if you continue to see the problem.

Comment 8

[benc]

-> NSPR.
That is where the connections come from, as I understand it.