Hi Everyone,
I just installed a brand new completely default OpenBSD 4.0/i386 system.
I have not changed any settings on it other than X, install bash, etc,
ie, nothing that should bother the network. It's connect to my network
where I have a OpenWRT router handing out dhcp(dnsmasq) and the
linux/windows/mac/etc machines on the network all work fine.

During install I netbooted and installed from ftp seemingly with no
problems. However, when installing packages from ports I noticed that it
took a long time to start to download the package, leading me to think
there was maybe a DNS problem. Upon investigations with lynx, ftp, and
ssh I found out that DNS takes a very long time (>60s) to resolve.
However, dig and ping both return IPs immediately. With some help from
#openbsd, I stumbled on the -4 option for ssh, without the option it
takes a very long time to ask my password, with -4 the password prompt
appears in <.5 seconds. This leads me to think there is some ipv6 problem...

I haven't touched the network settings on this machine and am not doing
anything with ipv6 on my router/network. Any ideas? This is a really
aggravating bug.

Thanks so much
Mike

Michael Dombrowski <legodudenein@hammycorp.com> wrote:

> I just installed a brand new completely default OpenBSD 4.0/i386 system. I
> have not changed any settings on it other than X, install bash, etc, ie,
> nothing that should bother the network. It's connect to my network where I
> have a OpenWRT router handing out dhcp(dnsmasq) and the
> linux/windows/mac/etc machines on the network all work fine.
> During install I netbooted and installed from ftp seemingly with no
> problems. However, when installing packages from ports I noticed that it
> took a long time to start to download the package, leading me to think
> there was maybe a DNS problem. Upon investigations with lynx, ftp, and ssh
> I found out that DNS takes a very long time (>60s) to resolve. However,
> dig and ping both return IPs immediately. With some help from #openbsd, I
> stumbled on the -4 option for ssh, without the option it takes a very long
> time to ask my password, with -4 the password prompt appears in <.5
> seconds. This leads me to think there is some ipv6
> problem... I haven't touched the network settings on this machine and am
> not doing anything with ipv6 on my router/network. Any ideas? This is a
> really aggravating bug.

What is in /etc/resolv.conf? 'npd -a' could be interesting, too.

Helmut

Helmut Schneider wrote:
> Michael Dombrowski <legodudenein@hammycorp.com> wrote:
>
>> I just installed a brand new completely default OpenBSD 4.0/i386 system. I
>> have not changed any settings on it other than X, install bash, etc, ie,
>> nothing that should bother the network. It's connect to my network where I
>> have a OpenWRT router handing out dhcp(dnsmasq) and the
>> linux/windows/mac/etc machines on the network all work fine.
>> During install I netbooted and installed from ftp seemingly with no
>> problems. However, when installing packages from ports I noticed that it
>> took a long time to start to download the package, leading me to think
>> there was maybe a DNS problem. Upon investigations with lynx, ftp, and ssh
>> I found out that DNS takes a very long time (>60s) to resolve. However,
>> dig and ping both return IPs immediately. With some help from #openbsd, I
>> stumbled on the -4 option for ssh, without the option it takes a very long
>> time to ask my password, with -4 the password prompt appears in <.5
>> seconds. This leads me to think there is some ipv6
>> problem... I haven't touched the network settings on this machine and am
>> not doing anything with ipv6 on my router/network. Any ideas? This is a
>> really aggravating bug.
>
> What is in /etc/resolv.conf? 'npd -a' could be interesting, too.
>
> Helmut
>
>

Hi Helmut,
Here is my resolv.conf, npd was not found on my system...?

-bash-3.1$ cat /etc/resolv.conf
search lan
nameserver 192.168.0.1
lookup file bind


Thanks
Mike

Helmut Schneider wrote:
> Michael Dombrowski <legodudenein@hammycorp.com> wrote:
>> problems. However, when installing packages from ports I noticed that it
>> took a long time to start to download the package, leading me to think
>> there was maybe a DNS problem. Upon investigations with lynx, ftp, and ssh
>> I found out that DNS takes a very long time (>60s) to resolve. However,
>> dig and ping both return IPs immediately. With some help from #openbsd, I
>> stumbled on the -4 option for ssh, without the option it takes a very long
>> time to ask my password, with -4 the password prompt appears in <.5
>> seconds. This leads me to think there is some ipv6
>> problem... I haven't touched the network settings on this machine and am
>> not doing anything with ipv6 on my router/network. Any ideas? This is a
>> really aggravating bug.

> What is in /etc/resolv.conf? 'npd -a' could be interesting, too.

This sounds a lot like the typical problem of when system has IPv6
capability but no actual IPv6 network links. The system does a DNS query
and gets back an AAAA record for a host and then, because it has no IPv6
link, it times out waiting for a response to an IPv6 connection to the
returned address. Could this also be Mr. Dombrowski's problem?

Cory Albrecht wrote:
> Helmut Schneider wrote:
>> Michael Dombrowski <legodudenein@hammycorp.com> wrote:
>>> problems. However, when installing packages from ports I noticed that it
>>> took a long time to start to download the package, leading me to think
>>> there was maybe a DNS problem. Upon investigations with lynx, ftp, and ssh
>>> I found out that DNS takes a very long time (>60s) to resolve. However,
>>> dig and ping both return IPs immediately. With some help from #openbsd, I
>>> stumbled on the -4 option for ssh, without the option it takes a very long
>>> time to ask my password, with -4 the password prompt appears in <.5
>>> seconds. This leads me to think there is some ipv6
>>> problem... I haven't touched the network settings on this machine and am
>>> not doing anything with ipv6 on my router/network. Any ideas? This is a
>>> really aggravating bug.
>
>> What is in /etc/resolv.conf? 'npd -a' could be interesting, too.
>
> This sounds a lot like the typical problem of when system has IPv6
> capability but no actual IPv6 network links. The system does a DNS query
> and gets back an AAAA record for a host and then, because it has no IPv6
> link, it times out waiting for a response to an IPv6 connection to the
> returned address. Could this also be Mr. Dombrowski's problem?

Hi Cory,
That sounds exactly what we concluded on IRC... it's a dead giveaway
when I force ssh to just use ipv4 it behaves exactly as expected. The
problem is that I don't know how to fix it... I didn't touch any network
settings when installing it and don't have ipv6 on my network anywhere
so I don't know why it would be trying to use it.

Thanks
Mike

Cory Albrecht <coryalbrecht+news@hotmail.com> wrote:

> This sounds a lot like the typical problem of when system has IPv6
> capability but no actual IPv6 network links. The system does a DNS query
> and gets back an AAAA record for a host and then, because it has no IPv6
> link, it times out waiting for a response to an IPv6 connection to the
> returned address.

No. This only happens if there is an actual IPv6 route.

--
Christian "naddy" Weisgerber naddy@mips.inka.de