MSGID: 2:203/2 5d03c30e
REPLY: 1:3634/12.73 5d03bb56
PID: JamNNTPd/Win32 1
CHRS: CP437 2
TZUTC: 0200
TID: CrashMail II/Win32 0.71
ml> i'll give you props for the nice try at attempting to confuse the
ml> postings and what they state at certain points of the conversation...
Methinks it's you that are trying to confuse the discussion. This is
exactly what you wrote as a comment to what I posted:
On 2019 Jun 11 21:35:42, you wrote to Michiel van der Vlist:
BF> Since I got a new IP every time I reconnected -- and often even
BF> when I
BF> *was* connected -- I never could use it for any kind of server
BF> functions (such as binkd), only for outgoing traffic.
really??? i've always done that as long as i've had a public IP address... it
was a simply matter of updating my DDNS entry and that was done by running a
tool that stayed in the background and handled the updates automatically...
yes, i ran servers on my dialup... most of the time, the new IP spread through
the network within minutes... no problem and it worked quite well...
"most of the time, the new IP spread through the network within minutes"
"no problem and it worked quite well"
Remember? No mention at all of two weeks with the same IP.
Alas, this has very little to do with IPv6 (that you don't even seem to
have), so EOD from me. Sorry Mr. Moderator.
..
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)
SEEN-BY: 1/123 15/2 154/10 201/0 203/0 2 124 211/37 221/0 1 226/17
SEEN-BY: 229/354 426 1014 230/0 240/5832 249/206 317 400 280/464 5003
SEEN-BY: 280/5006 5555 292/854 310/31 317/3 320/219 322/757 342/200
SEEN-BY: 393/68 423/81 120 633/280 712/848 770/1 2452/250 3634/24
SEEN-BY: 3828/7 5020/545
PATH: 203/2 0 280/464 229/426
|
