On Mon 09 Sep 2002 at 00:40:53 +0200, Olaf Seibert wrote:
> This could not be related to the IPv6 issues I have read a few times,
> because in that case I would expect not even the first page to work?

Well, now that I have upgraded to 1.6, the "IPv6 issues" also seem to
play a role. mozilla 1.0 broke down, claiming that any website refused
the connection. So I reinstalled 1.1, and I got the same. So I set
sysctl net.inet6.ip6.v6only from 1 to 0 (I thought that issue was fixed
in mozilla?) and then I got at least my first page back. Like before,
other pages did not work, but the error message was different. Under 1.5
it was a timeout, now under 1.6 it is "connection refused". A ktrace
shows this, which is yet again somewhat different to my eyes:

23652 mozilla-bin CALL  socket(0x18,0x1,0)
23652 mozilla-bin RET   socket 29/0x1d
23652 mozilla-bin CALL  fcntl(0x1d,0x3,0)
23652 mozilla-bin RET   fcntl 2
23652 mozilla-bin CALL  fcntl(0x1d,0x4,0x6)
23652 mozilla-bin RET   fcntl 0
23652 mozilla-bin CALL  connect(0x1d,0x1601fb7d0,0x1c)
23652 mozilla-bin RET   connect -1 errno 51 Network is unreachable
    
I can assure you that the network it should be trying to reach was
certainly reachable since it was from the same webserver as the first
page.

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert - rhialto@       -- Woe betide the one who feels
\X/ polderland.nl  -- remorse without sin - Tom Poes, "Het boze oog", 4444.