I wonder if an option for forcing IPv4 or IPv6 polling would be worth adding?
I noted the change to default to IPv4 when using nodelist but then the thought becomes how to force an IPv6 only attempt?
So if MIS POLL came with a -4 or -6 switch that might be a good idea?
Not sure, but thought I'd throw that out for discussion.
So if MIS POLL came with a -4 or -6 switch that might be a good idea?
Not sure, but thought I'd throw that out for discussion.
Being able to force poll everything with IPv4 with a -4 flag would make things easier than going into ./mystic -cfg to switch the node to IPv4
and then running ./mis poll
That being said, if an IPv6 poll doesn't work, isn't it supposed to fall back to IPv4? I've not seen that be the case.
Its supposed to work that way which would mean the -4 and -6 would not
be all that useful. But...
It *is* coded to fallback/function like "Happy Eyeballs" as Alisha mentioned earlier when set to "Default IPV6" or "IPV6+IPV4", but its broken. Not surprising since I coded IPV6 support way back in day
without having IPV6 myself.
For now I have changed the nodelist-lookup-based connections to use IPV4 in the latest build until I can figure out what is going wrong. With
any luck I'll get some time to fix it up this weekend.
For now I have changed the nodelist-lookup-based connections to use PH> g0> I
in the latest build until I can figure out what is going wrong. PH> g0> With
any luck I'll get some time to fix it up this weekend.
the joys of debugging huh? :)
I was able to fix it today. The bug has been around for so long that I
am slightly worried that the fix could break something else.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 16 (0 / 16) |
Uptime: | 00:16:18 |
Calls: | 500,919 |
Calls today: | 6 |
Files: | 109,372 |
D/L today: |
14,479 files (2,298M bytes) |
Messages: | 305,052 |
Posted today: | 7 |