If I run
NetNameResolver localHostAddress
 in a 5.2 image on my iMac it returns  #[0 0 0 0]. On a Pi it returns the more appropriate #[192 168 1 42] sort of answer.
On an 86 linux it also gives the wrong answer; so it doesn't seem like a purely Mac vm bug. The image says useOldNetwork is true (which seems like something we've been fudging for a long while now) in all cases. If I set the preference to use the ipv6/new network stuff I get a less bad answer on the Mac of  192.168.1.65(192.168.1.65),0(0) - but I don't think it is quite what the rest of the system wants since trying (from PersonalSqueakSource)
(NetNameResolver nameForAddress: (NetNameResolver localHostAddress) timeout: 5)
		ifNil: [NetNameResolver localAddressString]
results in a prim failure in NetNameResolver class>>#nameForAddress:timeout:
Sigh.

Anybody got any brilliant ideas on what is going wrong here?

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
A sad tale that brings a lump to the eye and a tear to the throat.