Is there a way to select an ipv4 connection in SyncTerm? I
recently encountered an address that doesn't have ipv6 and
there was a problem connecting.
Is there a way to select an ipv4 connection in SyncTerm? I
recently encountered an address that doesn't have ipv6 and
there was a problem connecting.
mark lewis scribbled to Jon Justvig <=-
On 2017 Aug 19 22:39:00, you wrote to All:
Is there a way to select an ipv4 connection in SyncTerm? I
recently encountered an address that doesn't have ipv6 and
there was a problem connecting.
your OS' network stack should try IPv6 first and then drop back to IPv4
if there's no IPv6 available for that destination domain... that's provided that the domain has both AAAA and A records...
Digital Man scribbled to Jon Justvig <=-
@VIA: VERT
@MSGID: <599A10A9.71813.sync@vert.synchro.net>
@REPLY: <599904D3.588.dove-syncdisc@vintagebbsing.com>
@TZ: c1e0
Re: ipv4
By: Jon Justvig to All on Sat Aug 19 2017 10:39 pm
Is there a way to select an ipv4 connection in SyncTerm? I
recently encountered an address that doesn't have ipv6 and
there was a problem connecting.
Run syncterm with the "-4" option. This might only work with the 1.1
beta (current).
Digital Man scribbled to Jon Justvig <=-
@VIA: VERT
@MSGID: <599A10A9.71813.sync@vert.synchro.net>
@REPLY: <599904D3.588.dove-syncdisc@vintagebbsing.com>
@TZ: c1e0
Re: ipv4
By: Jon Justvig to All on Sat Aug 19 2017 10:39 pm
Is there a way to select an ipv4 connection in SyncTerm? I
recently encountered an address that doesn't have ipv6 and
there was a problem connecting.
Run syncterm with the "-4" option. This might only work with the 1.1 beta (current).
Adding -4 as a parameter when running SyncTerm just popped up a help
screen (in terminal mode) without launching the actual program. However, yeah, I'm running v0.9.5b currently. I'll see if I can grab the 1.1 beta version for Linux (if it's available).
Is there a way to select an ipv4 connection in SyncTerm? I recently
encountered an address that doesn't have ipv6 and there was a
problem connecting.
your OS' network stack should try IPv6 first and then drop back to
IPv4 if there's no IPv6 available for that destination domain...
that's provided that the domain has both AAAA and A records...
Do you know how I might be able to accomplish this in Linux (Debian)?
It's possible that the domain doesn't have both those records as a
ping showed the IPv6 address than a IPv4 address.
There is another sub-domain name he mentioned and it showed the IPv4 address and I was able to connect to it just fine.
mark lewis wrote to Jon Justvig <=-
Do you know how I might be able to accomplish this in Linux (Debian)?
AFAIK, it is built into all current network stacks... it is
automatic...
if they only have a A record, then they only offer IPv4 on that
domain... if they only have an AAAA record, then they only offer IPv6
on that domain... if they have both, then they offer both on that domain...
that's the nature of the beast(s)...
There is another sub-domain name he mentioned and it showed the IPv4 address and I was able to connect to it just fine.
that sounds proper...
mark lewis scribbled to Jon Justvig <=-
On 2017 Aug 20 18:34:00, you wrote to me:
if they only have a A record, then they only offer IPv4 on that
domain... if they only have an AAAA record, then they only offer IPv6
on that domain... if they have both, then they offer both on that domain...
that's the nature of the beast(s)...
There is another sub-domain name he mentioned and it showed the IPv4 address and I was able to connect to it just fine.
that sounds proper...
if they only have a A record, then they only offer IPv4 on that
domain... if they only have an AAAA record, then they only offer IPv6
on that domain... if they have both, then they offer both on that
domain...
that's the nature of the beast(s)...
Yeah, I don't think it has anything to do at a remote end...
There is another sub-domain name he mentioned and it showed the IPv4
address and I was able to connect to it just fine.
that sounds proper...
I guess I'll have to use the other sub-domain name for now...
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 09:33:56 |
Calls: | 510 |
Messages: | 220574 |