default http client and ipv6

[Vasiliy Tolstov]

Hello. I find small issue. For example i have domain www.test.com that
have 2 A records and 2 AAAA records.

When in go i'm try to http.Get("http://www.test.com") and does not
have ipv4 address configured on interface i have error, that says
about unable to connect to ipv4 address of domain. I'm try to use
DualStack in dialer transport, but this is not helps.
Now i manually resolve records and walk, but does it possible to
automatic determine destination address if ipv4/ipv6 addresses not
exists?

--
Vasiliy Tolstov,
e-mail: v.to...@selfip.ru
jabber: va...@selfip.ru

[Brad Fitzpatrick]

Mikio? Shouldn't this work out of the box?

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mikio Hara]

can you tell us what happens when you run http://play.golang.org/p/ehvPanPT5t ?

On Thu, Aug 21, 2014 at 8:47 AM, Brad Fitzpatrick <brad...@golang.org> wrote:

> Mikio? Shouldn't this work out of the box?

yes--if he has a concrete ipv6 connectivity for both control and
forwarding planes.

no--i'm afraid of something went wrong with the techniques such as
map-t/e, ds-lite, 464xlat, 6rd, nat64/dns64, blah blah.

[Mikio Hara]

ah, perhaps he needs a convenient solution for the plain-old 6-6-6 (client-transport-server) case with single dial call not using dualstack toggle, hm.

[Vasiliy Tolstov]

Sorry for screenshot. As for note - i'm compile without CGO (static
binary). And i'm try to use dualstack but in this use case it not
works.
Because in absence of ipv4 client tries to connect to ipv4 address.

[James Bardin]

Does it work if you only Dial for IPv6?

Maybe DualStack is failing when there's no local IPv4 connectivity at all.

[Vasiliy Tolstov]

2014-08-21 18:26 GMT+04:00 James Bardin <j.ba...@gmail.com>:
> Does it work if you only Dial for IPv6?
> Maybe DualStack is failing when there's no local IPv4 connectivity at all.

I can't see difference if i switch dualstack true/false.

[James Bardin]

On Thu, Aug 21, 2014 at 10:49 AM, Vasiliy Tolstov <v.to...@selfip.ru> wrote:

2014-08-21 18:26 GMT+04:00 James Bardin <j.ba...@gmail.com>:

> Does it work if you only Dial for IPv6?
> Maybe DualStack is failing when there's no local IPv4 connectivity at all.

I can't see difference if i switch dualstack true/false.

I know, because IPv4 is what's failing. Try dialing for IPv6 *only* (not DualStack)

[Vasiliy Tolstov]

2014-08-21 18:54 GMT+04:00 James Bardin <j.ba...@gmail.com>:
> I know, because IPv4 is what's failing. Try dialing for IPv6 *only* (not
> DualStack)

In case of http client i can't understand how can i do that.

[James Bardin]

On Thu, Aug 21, 2014 at 10:55 AM, Vasiliy Tolstov <v.to...@selfip.ru> wrote:

2014-08-21 18:54 GMT+04:00 James Bardin <j.ba...@gmail.com>:

> I know, because IPv4 is what's failing. Try dialing for IPv6 *only* (not
> DualStack)

In case of http client i can't understand how can i do that.

Ah, ok

You should be able to try this out by giving the Transport a Dial function like so:

func DialTCP6(network, addr string) (net.Conn, error) {

return net.Dial("tcp6", addr)

}

 

[Vasiliy Tolstov]

2014-08-21 19:04 GMT+04:00 James Bardin <j.ba...@gmail.com>:
> Ah, ok
>
> You should be able to try this out by giving the Transport a Dial function
> like so:
>
> func DialTCP6(network, addr string) (net.Conn, error) {
> return net.Dial("tcp6", addr)
> }

i'm always get no suitable address found error

[Mikio Hara]

On Thu, Aug 21, 2014 at 9:21 PM, Vasiliy Tolstov <v.to...@selfip.ru> wrote:

> Sorry for screenshot. As for note - i'm compile without CGO (static binary).

looks like it's a bug of builtin dns stub resolver. can you please
file an issue, thanks.

http://golang.org/project/
https://code.google.com/p/go/issues/entry

[Mikio Hara]

hi,

have you already filed an issue? as the screenshot described, you are
using non-global routable ipv6 address (fed0::/64?) so we can assume
that you have implemented nptv6 (known as nat66) or similar stuff and
builtin dns stub resolver had some trouble with that stuff. we cannot
dig up the issue without your help.

[Vasiliy Tolstov]

2014-08-22 13:20 GMT+04:00 Mikio Hara <mikioh...@gmail.com>:
> hi,
>
> have you already filed an issue? as the screenshot described, you are
> using non-global routable ipv6 address (fed0::/64?) so we can assume
> that you have implemented nptv6 (known as nat66) or similar stuff and
> builtin dns stub resolver had some trouble with that stuff. we cannot
> dig up the issue without your help.

No i don't file issue. This is ipv6 address i'm assign via qemu user
network. Packets from virtual machine goes to qemu process and routed
to external world.
I'm try with global routed address but nothing changed.

[Mikio Hara]

On Fri, Aug 22, 2014 at 8:21 PM, Vasiliy Tolstov <v.to...@selfip.ru> wrote:

> No i don't file issue.

is there any reason?

[Vasiliy Tolstov]

2014-08-22 15:52 GMT+04:00 Mikio Hara <mikioh...@gmail.com>:
> is there any reason?


I have no time =), sorry. Today i'm file a issue.

[Vasiliy Tolstov]

i'm file issue https://code.google.com/p/go/issues/detail?id=8573