The problem is that dynamic dns don't necessarily solve any problems.
The address is bound at start, and if the resolution in DNS changes at
some later point, that won't get reflected unless pydecnet would redo
the name lookup, close and reopen the listening socket bound to the new
address.
Changing the last byte of an address to 0 have no special significance.
It's not like it would be a wildcard or something. And no, a socket
binding do not include any netmask.
Iain might have been able to get it running by just skipping the host
part. Basically:
circuit mul-123 Multinet :15001:listen --cost 8 --t3 120
But I haven't tested it, so I didn't want to suggest it.
Johnny
On 2022-04-26 18:39, Thomas DeBellis wrote:
I wound up using Dynamic DNS, but I'm not sure
that a host name could be
parsed there. Otherwise, you need a static IP.
Your second example is interesting. I don't suppose it would accept
something clever like:
circuit mul-123 Multinet 207.123.123.*0*:15001:listen --cost 8 --t3 120
Or
circuit mul-123 Multinet 207.123.123.*0/24*:15001:listen --cost 8 --t3 120
On 4/26/22 12:04 PM, Iain Hardcastle wrote:
Hi all,
Is there way to have PDR accept arbitrary TCP Multinet connections?
This works:
circuit mul-123 Multinet 207.123.123.123:15001:listen --cost 8 --t3 120
While this does not:
circuit mul-123 Multinet 0.0.0.0:15001:listen --cost 8 --t3 120
I’m sure I’ve had it working before..
Problem is, that remote 207 address is dynamic.
Cheers,
iain
_______________________________________________
HECnet mailing list --hecnet(a)lists.dfupdate.se
To unsubscribe send an email tohecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol