It seems like I've managed to get 2:203/0 working again for incoming calls. Work in progress for outgoing calls.




..

--- 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)

26 Mar 18 11:23, you wrote to all:

It seems like I've managed to get 2:203/0 working again for incoming

So it seems. Nice!

Did you get the he.net tunnel work over your 3G?

'Tommi

---
* Origin: ================================== (2:221/360)

Hello Bjorn,

On Monday March 26 2018 11:23, you wrote to All:

It seems like I've managed to get 2:203/0 working again for incoming calls.

+ 12:27 [616] call to 2:203/0@fidonet
12:27 [616] trying eljaco.se [2001:470:27:302::2]:24555...
12:27 [616] connected
+ 12:27 [616] outgoing session with eljaco.se:24555 [2001:470:27:302::2]
- 12:27 [616] OPT CRAM-MD5-a5b14ec22385627750954b1a5f1314ee
+ 12:27 [616] Remote requests MD mode
- 12:27 [616] SYS Felten's Sharp System
- 12:27 [616] ZYZ Bjorn Felten
- 12:27 [616] LOC Save, Sweden
- 12:27 [616] NDL 115200,TCP,BINKP
- 12:27 [616] TIME Mon, 26 Mar 2018 12:27:33 +0200
- 12:27 [616] VER binkd/1.1a-65/Win32 binkp/1.1

Yep! Congratulations.

Work in progress for outgoing calls.

- 26 Mar 12:24:38 [200] incoming from 2001:470:27:302::2 (2332)
+ 26 Mar 12:24:39 [2168] incoming session with
bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net [2001:470:27:302::2]
- 26 Mar 12:24:39 [2168] SYS Felten's Sharp System
- 26 Mar 12:24:39 [2168] ZYZ Bjorn Felten
- 26 Mar 12:24:39 [2168] LOC Save, Sweden
- 26 Mar 12:24:39 [2168] NDL 115200,TCP,BINKP
- 26 Mar 12:24:39 [2168] TIME Mon, 26 Mar 2018 12:24:49 +0200

Check!



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

So it seems. Nice!

Thanks.

Did you get the he.net tunnel work over your 3G?

No, that's just it. My ISP finally (after a month) managed to get my ADSL working. So incoming IPv6 is coming in on my ADSL line.

I'm kinda reluctant to change my outgoing calls to the ADSL line considering
that my 3G line works so much better -- more than twice the speed and so far no
connection problems (that would render me a new IP number).

So, for now, I think I'll await my fibre to be connected before I'll be IPv6
outgoing ready. It'll probably take a few weeks more before my fibre installation is completed. The ISP keeps postponing the end date over and over again. Big surprise, eh? 8-)

I would also like to say that I'm extremely impressed by the he.net guys. It
took only a few minutes after I changed my end IP address on their site before the first IPv6 calls came in. Kudos he.net!


..

--- 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)

MvdV> - 26 Mar 12:24:38 [200] incoming from 2001:470:27:302::2 (2332)
MvdV> + 26 Mar 12:24:39 [2168] incoming session with
MvdV> bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net [2001:470:27:302::2]
MvdV> - 26 Mar 12:24:39 [2168] SYS Felten's Sharp System
MvdV> - 26 Mar 12:24:39 [2168] ZYZ Bjorn Felten
MvdV> - 26 Mar 12:24:39 [2168] LOC Save, Sweden
MvdV> - 26 Mar 12:24:39 [2168] NDL 115200,TCP,BINKP
MvdV> - 26 Mar 12:24:39 [2168] TIME Mon, 26 Mar 2018 12:24:49 +0200

MvdV> Check!

WOW. That was kinda unsuspected. It seems I'm better on this than I thought I was. 8-)






..

--- 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)

Hello Bjorn,

On Monday March 26 2018 11:40, you wrote to Tommi Koivula:

Did you get the he.net tunnel work over your 3G?

No, that's just it. My ISP finally (after a month) managed to get
my ADSL working. So incoming IPv6 is coming in on my ADSL line.

Aha!.

I'm kinda reluctant to change my outgoing calls to the ADSL line considering that my 3G line works so much better

I don't know if it is accidental or deliberate, but you ARE making outgoing connections over IPv6,

So, for now, I think I'll await my fibre to be connected before
I'll be IPv6 outgoing ready. It'll probably take a few weeks more
before my fibre installation is completed. The ISP keeps postponing
the end date over and over again. Big surprise, eh? 8-)

No surprise but I suppose now that your ADSL is working again and you have the 3G as a backup, you can ride it out for another a couple of weeks.

So will you have full Dual Stack IP over the fiber?

I would also like to say that I'm extremely impressed by the he.net guys. It took only a few minutes after I changed my end IP address on their site before the first IPv6 calls came in. Kudos he.net!

They do a really good job!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

MvdV> So will you have full Dual Stack IP over the fiber?

That's what I expect. The ISP of my choice happens to be the one that's been
running all the end IPv6 tunnels in Sweden for all those years.




..

--- 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)

Hello Bjorn,

On Monday March 26 2018 11:42, you wrote to me:

MvdV>> - 26 Mar 12:24:38 [200] incoming from 2001:470:27:302::2 (2332)
MvdV>> + 26 Mar 12:24:39 [2168] incoming session with
MvdV>> bfelten-1-pt.tunnel.tserv24.sto1.ipv6.he.net
MvdV>> [2001:470:27:302::2]

WOW. That was kinda unsuspected. It seems I'm better on this than I thought I was. 8-)

Coming to think of it... if you have installed the tunnel to accept incoming IPv6 from your ADSL line, and so the interface for the ADLS line has an IPv6 address, I do not see how you can stop applications from making outgoing IPv6 connections via that interface, unless you explicitly configure the application
to not do so.

So unless you tell binkp not to make outhoing IPv6 call, it will use the tunnel
and the ADSL line for outgoing IPv6.

I suspect the same goes for your browser. What does ipv6-test.com say?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

MvdV> What does ipv6-test.com say?

It's all green. 20/20.

Interesting...



..

--- 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)

MvdV> So unless you tell binkp not to make outgoing IPv6 call, it will use the
MvdV> tunnel and the ADSL line for outgoing IPv6.

That seems logical. And by the look of it even practical.

So, have I now earned my brownies, so my system can once again be listed as fully operational? 8-)



..

--- 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)

Hello Bj%rn!

26 Mar 18 14:11, you wrote to Michiel van der Vlist:

That seems logical. And by the look of it even practical.

So, have I now earned my brownies, so my system can once again be listed as fully operational? 8-)

If you go on like that, you will have a brown nose. ;)

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

26 Mar 18 11:40, you wrote to me:

So it seems. Nice!

Thanks.

Did you get the he.net tunnel work over your 3G?

No, that's just it.

Damn. No sage t-shirt for you.

I would also like to say that I'm extremely impressed by the he.net guys. It took only a few minutes after I changed my end IP address on their site before the first IPv6 calls came in. Kudos he.net!

Well it takes only milliseconds after you tell them your ipv4 end address. Nothing like dns changes, only the tunnel needs to start.

'Tommi

---
* Origin: ================================== (2:221/6.10)

Hello Bjorn,

On Monday March 26 2018 14:11, you wrote to me:

So, have I now earned my brownies, so my system can once again be listed as fully operational? 8-)

Done!

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)