IPv6
< Newer Topic
:: Older Topic >
#41 Jan 20, 2025 12:09 am
Black Hand
GroupAdministrators
Posts3,705
JoinedJan 1, 2002
Also for the record I've now gotten AFKMud to compile under Cygwin again (damn libraries) and confirmed that even on my Windows 10 Home PC that the code bound both addresses and accepted a connection from another PC in the house. Neither of which get assigned IPv6 addresses because our router is so backward it doesn't even support it at all.
I don't think portability is an issue here. It's just a matter of getting the DNS resolver process to play along now.
I don't think portability is an issue here. It's just a matter of getting the DNS resolver process to play along now.
#42 Jan 20, 2025 12:38 pm
Last edited Jan 20, 2025 12:48 pm by GatewaySysop
Conjurer
GroupMembers
Posts428
JoinedMar 7, 2005
Fair enough.
I'll agree to disagree on portability, since I thought the principle argument against a dual stack socket was that not all (legacy) OS would support it, instead requiring an approach with multiple sockets (like the RFC was showing). That said, it's not my base to maintain and I suppose few people will try and compile and run this on hardware that ancient. Guess we'll find out if they do, should they find themselves here asking for support.
I'll agree to disagree on portability, since I thought the principle argument against a dual stack socket was that not all (legacy) OS would support it, instead requiring an approach with multiple sockets (like the RFC was showing). That said, it's not my base to maintain and I suppose few people will try and compile and run this on hardware that ancient. Guess we'll find out if they do, should they find themselves here asking for support.