Re: Bug#80503: ssh: default configuration breaks IPv6

[Dancer Vesperman <dancer@zeor.simegen.com>]

I'm actually starting to feel a trifle guilty about submitting this bug 
(almost...what...a year ago?) in the first place, considering the 
wrangle it seems to be causing now.

Put simply: At the time, openssh defaulted to working 'out of the box' 
for ipv6 and ipv4...that is, the configuration worked fine for v4-only 
machines, and v6/v4 machines without having to modify the conf 
distributed with the package. Hooray.

Then I got the next version, and the conf file broke that clean default 
behaviour. That's why I submitted the report originally. You had to mess 
with it to make it go on anything other than v4-only boxen. It seemed 
like a sudden (and accidental) step backwards.

D

horape@tinuviel.compendium.net.ar wrote:

> ¡Hola!
>
>
> > > Really, i don't believe that's that way. There is an upstream package, a 
> > > "mediumstream" package and debian package. The "mediumstream" patch
> > > breaks something. Maybe debian should fix what "mediumstream" has broken.
> >
> > Well, you must consider that the upstream package is a pure openbsd
> > package which will not work on any other OS. So the openssh-developers
> > ake the source and add all the stuff that is necessary to support other
> > OS and add features. Also the developers are not the same, so there are
> > difference between the people working on openssh on openbsd and for the
> > other OS. So I would call the sources that we use here upstream, since
> > the bugs and problems that we notice are mostly coming from the port.
>
>
> Ok, point taken.
>
>
> > > > > Options are: 
> > > > > (a) ListenAddress set: IPv4 works, IPv6 doesn't.
> > > > > (b) ListenAddress unset: IPv4 works the very same way, IPv6 works.
>
> > > > Would this cause first an IPv6 lookup for the IP and then a IPv4 lookup?
>
> > > [I assume lookup = dns lookup, else i don't understand the question]
> >
> > Yes.
>
>
> > > No. That's a bind(2) call. There is no dns lookup anywhere.
>
> > Are you sure? I think there's also a dns-lookup involved as otherwise
> > you won't know the IP-address of the host that ssh should connect to.
>
>
> Remember that we're talking about the server. The dns lookups are done
> just at connection time. The only dns lookup made by the server should
> be an inverse lookup against the address where the connection is originated
> from.
>
>
> > > Yep, but that's something I regret. I've been a debian user for more than
> > > five years, but when i needed to work seriously with IPv6 I had to install
> > > some BSDs (and we're FAR behind them, FBSD even allows installing over
> > > the 6bone)
> >
> > Hm, what's the 6bone? Where can I get more information about it?
>
>
> (From www.6bone.net: )
>
>    The 6bone is an IPv6 Testbed that is an outgrowth of the IETF IPng project
>    that created the IPv6 protocols intended to eventually replace the current
>    Internet network layer protocols known as IPv4.
>   
>    The 6bone started as a virtual network (using IPv6 over IPv4
>    tunneling/encapsulation) operating over the IPv4-based Internet to support
>    IPv6 transport, and is slowly migrating to native links for IPv6 transport.
>
> More info at http://www.6bone.net/
>
>
> > Ciao
> >      Christian
>
>
> Saludos,
> 					HoraPe
> ---
> Horacio J. Peña
> horape@compendium.com.ar
> horape@uninet.edu
> bofh@puntoar.net.ar
> horape@hcdn.gov.ar
>
>
> --  
> To UNSUBSCRIBE, email to debian-ipv6-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org