Mark, Glad the suggestion provided a work-around. But please don't drop this.
simh should learn to cope; most distributions enable IPv6, yet most home networks don't have it enabled. (Or have ::1 but no IPv6 interface, or only automatic link-local addresses or ..) So simh should be able to (and the code seems to intend that it) listen on the wildcard IP address for whatever combination of IPv4 and IPv6 is available. I do have a RPi - but it's dedicated to NTP & it does have a full IPv6 network. So I can't debug. But your network config & build options will help Mark (P).
As I noted, simh should also report the errors better.If you only have a DHCP address, presumably you only want console access from the host. So you should be able to use localhost (127.0.0.1) - which improves security and doesn't require an other magic. One might argue that since simh is using telnet, localhost (127.0.0.1 + ::1) should be the default for listening sockets... though that probably requires 1 socket/protocol.
This communication may not represent my employer's views, if any, on the matters discussed. On 23-Apr-13 03:06, Mark Benson wrote:
On 23 Apr 2013, at 00:55, Timothe Litt wrote:FWIW, errno 97 would be address family not supported. (It would be nice if strerror() (or the thread-safe strerror_r() if available) was called instead of just printing the decimal error number.) You didn't say which OS you're running on your RPi. The default is debian.Check the e-mail title :)You probably have an IPv6 configuration issue; the new simh code tries to use it if it thinks its available. From a quick look at the code, you may want to replace the 13900 port number with your ip (v4 1.2.3.4:13900 or v6 [2001:db8::123]:13900).Thanks, that fixed it. I'll pursue fixing that or disabling IPv6, as the unit is on DHCP so doesn't have a fixed IP, thus this needs to work without using the IP address.But I'll leave further diagnosis to Mark, who checked-in the changes to support IPv6. He'll probably need the commands that you used to build simh.No need, I think the issue is external to simh.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
