[squeak-dev] sqConnectToAddressSize: Address family not supported by protocol

Chris Muller asqueaker at gmail.com
Mon Sep 23 19:01:04 UTC 2013


A tier-2 support specialist from Google just left.  No one was sure
what the precise cause of the issue was, but by changing my IPv6
Method (in Ubuntu's connection editor) from "Automatic" to "Ignore",
and then back to "Automatic", followed by a reboot of the router,
seems to have cleared the issue up.  Everything seems to be working
fine even with Squeak's IPv6 turned on.

Thank you all for the suggestions, I'm glad it was my problem and not Squeak.

On Mon, Sep 23, 2013 at 6:09 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 2013-09-21, at 23:55, Tobias Pape <Das.Linux at gmx.de> wrote:
>
>> Am 21.09.2013 um 22:04 schrieb Chris Muller <asqueaker at gmail.com>:
>>
>>> Using curl for http get produces nearly the opposite results as using squeak.
>>>
>>> Connected to GF:
>>>  curl --ipv6 --get www.yahoo.com
>>>          ("...a bunch of http...")
>>>
>>> Connected to Surewest:
>>>   curl --ipv6 --get www.yahoo.com
>>>          "curl: (7) Failed to connect to 2001:4998:f011:1fe::3000:
>>> Network is unreachable"
>>>
>>
>>
>> are you positive that IPv6 is enables in your image?
>>
>>> On 21 September 2013 18:14, Chris Muller <asqueaker at gmail.com> wrote:
>>>> Name-resolution does not seem to be the issue.  NetNameResolver
>>>> produces a SocketAddress whose printString pretty much matches what I
>>>> get using "host" on the linux command-line.
>>>>
>>>> The issue is that Squeak is unable to use its own SocketAddress
>>>> representation to make the connection.  And it reports this error from
>>>> the VM:
>>>>
>>>>  sqConnectToAddressSize: Address family not supported by protocol
>>>>
>>>> Does anyone know what that means?
>>>
>>> Well, the error is quite clear, or would be if the error told us which
>>> "address family" and "protocol" were involved. What does strace tell
>>> you?
>>>
>>
>> protocol would ipv6 in this case but af might be inet, but should be inet6, iirc.
>>
>> Best
>>       -tobias
>
> Definitely looks like an IPv6 issue, which should work in theory if the VM has the new Socket plugin, but has not been extensively tested.
>
> You could try with Etoys from squeakland.org which used to handle IPv6 just fine, at least under Linux. It was not tested much on other OS either.
>
> Would be nice to get this ironed out (though there is the option of disabling IPv6 in your OS).
>
> - Bert -
>
>
>


More information about the Squeak-dev mailing list