On 29.01.2014, at 22:12, Chris Muller ma.chris.m@gmail.com wrote:
I thought we had it enabled in the 4.4 release, but I just downloaded and checked: we didn't.
So should we enable this at the last second of this release or first second of next release or did it get tested all during this release and its okay?
Pleas enable it after the release. Reasoning is following: - We use squeak in class and encourage our students to at least try images on their own, hence, they should look into the then-to-be-stable 4.5. - As pointed out, our squeaksource is primarily advertised in DNS as IPv6 (which we cannot and won’t change) - If the IPv6 support can produce the spontaneous error as I indicated (and have reproduced with other people at HPI), the students would just be driven away.
Best -Tobias
I have the feeling that the IPv6 support is not yet working right. I wanted to use our local SqueakSource, which is primarily available via IPv6 though the HPI.
The first time, I got a "connection refused" error, Socket was unable to open a connection to our site.
I tried this (low-level connect) (SocketAddressInformation forHost: '2001:638:807:204::8d59:e178' service: '80' flags: 0 addressFamily: SocketAddressInformation addressFamilyINET6 socketType: SocketAddressInformation socketTypeStream protocol: 0) first connect And it worked.
Then I tried monticello again, and it worked. Then again, the "connection refused" error.
Since the error is spontaneous, I don't know how to debug :(