Michiel discovered a couple of days ago that I no longer called him IPv6.

I know that incoming IPv6 calls work, but how about outgoing?

Can you all please confirm that my system no longer calls IPv6?






..

--- 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)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bj||rn,

On 13 Dec 16 01:31, Bj||rn Felten wrote to All:

Michiel discovered a couple of days ago that I no longer called him
IPv6.

I know that incoming IPv6 calls work, but how about outgoing?

Can you all please confirm that my system no longer calls IPv6?

Both are confirmed here all day today. My calls to you are IPv6, but your calls to me have indeed been via IPv4.

Also, I sent you a netmail yesterday regarding JamNNTPd. Did you get it?

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20160827
# Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bjorn,

On Tuesday December 13 2016 01:31, you wrote to All:

Michiel discovered a couple of days ago that I no longer called him
IPv6.

I know that incoming IPv6 calls work, but how about outgoing?

Can you all please confirm that my system no longer calls IPv6?

Still only incoming IPv4 from you:

- 13 Dec 01:33:05 [3744] incoming from 90.231.158.147 (3737)
+ 13 Dec 01:33:05 [3804] incoming session with 90.231.158.147
- 13 Dec 01:33:05 [3804] SYS Felten's Sharp System
- 13 Dec 01:33:05 [3804] ZYZ Bjorn Felten
- 13 Dec 01:33:05 [3804] LOC Save, Sweden

It is not a basic flaw at he.net. I ran a he.net tunnel for five years and had no problems with outgoing IPv6. It must be something in your configuration.

How about web browsing? Do you see the turtle dancing at http://www.kame.net/ ?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
# Origin: he.net certified sage (2:280/5555)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

MvdV> It is not a basic flaw at he.net. I ran a he.net tunnel for five years
MvdV> and had no problems with outgoing IPv6. It must be something in your
MvdV> configuration.

Well, if it worked initially, I don't see how my configuration suddenly can make it not work any more. Especially since it still works on incoming calls.

MvdV> How about web browsing? Do you see the turtle dancing at
MvdV> http://www.kame.net/ ?

It's not that easy. As I may have said, I'm running an XP Mini on my inbound router/fidonet computer. I don't have any browser installed on it.

But I'll see what netsh may have changed without me knowing about it -- it's not like it would be the first time netsh is playing games with
me... :(


..

--- 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)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Re: Problems here after changing to he.net?
By: Bjorn Felten to All on Tue Dec 13 2016 01:31:26

Michiel discovered a couple of days ago that I no longer called him IPv6.

I know that incoming IPv6 calls work, but how about outgoing?

Can you all please confirm that my system no longer calls IPv6?

Just watched an incoming from you and it only showed an IP number, thus IPv4 only
--- SBBSecho 3.00-Win32
# Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Can you all please confirm that my system no longer calls IPv6?

Just watched an incoming from you and it only showed an IP number, thus IPv4 only

Darn! But thanks anyway.

I just "reloaded" my netsh script and hope that it will make some difference.

netsh -f PATH_AND_FILENAME.txt

And if you want to save your working setting, here's how to save it for the above reload:

netsh -c interface dump > PATH_AND_FILENAME.txt

Just in case anyone of y'all is interested... 8-)

The resulting textfile is actually easier to manually edit than going over all the netsh shit...

..

--- 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)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bj||rn,

On 13 Dec 16 05:32, Bj||rn Felten wrote to Joe Delahaye:

I just "reloaded" my netsh script and hope that it will make some difference.

FYI, it looks like you sent this out about 6 minutes ago. I had an incoming call from you one minute later and it was still IPv4.

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20160827
# Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

FYI, it looks like you sent this out about 6 minutes ago. I had an incoming call from you one minute later and it was still IPv4.

Thanks. And darn!

Why must this entire IPv6 be so complicated...?



..

--- 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)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bj%rn,

On 13 Dec 16 05:50, Bj%rn Felten wrote to Nicholas Boel:

Thanks. And darn!

No problem. I'll let you know if it changes.

Why must this entire IPv6 be so complicated...?

I know you absolutely don't want to hear it. But I would be willing to bet upgrading Windows would make things a lot easier for you (ie: no netsh commands to run, as IPv6 is enabled and supported already).

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20160827
# Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bj%rn!

13 Dec 16 05:50, you wrote to Nicholas Boel:

FYI, it looks like you sent this out about 6 minutes ago. I had an
incoming call from you one minute later and it was still IPv4.

Thanks. And darn!

Why must this entire IPv6 be so complicated...?

Ipv6 is not complicated, the way you use it is.

Kees

--- GoldED+/LNX 1.1.5
# Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Re: Problems here after changing to he.net?
By: Bjorn Felten to Joe Delahaye on Tue Dec 13 2016 05:32:00

Can you all please confirm that my system no longer calls IPv6?

Just watched an incoming from you and it only showed an IP number,
thus IPv4 only

Darn! But thanks anyway.

I just "reloaded" my netsh script and hope that it will make some difference.

netsh -f PATH_AND_FILENAME.txt

And if you want to save your working setting, here's how to save it for the above reload:

netsh -c interface dump > PATH_AND_FILENAME.txt

Just in case anyone of y'all is interested... 8-)

The resulting textfile is actually easier to manually edit than going
over all the netsh shit...

At 09:51 this morning in my logs, your entry still shows an IPv4 IP

... She drowned at the end of her life.
--- SBBSecho 3.00-Win32
# Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bjorn,

On Tuesday December 13 2016 04:55, you wrote to me:

Still no IPv6 coming from you:

- 13 Dec 16:12:59 [3744] incoming from 90.231.158.147 (4572)
+ 13 Dec 16:12:59 [4028] incoming session with 90.231.158.147
- 13 Dec 16:12:59 [4028] SYS Felten's Sharp System
- 13 Dec 16:12:59 [4028] ZYZ Bjorn Felten
- 13 Dec 16:12:59 [4028] LOC Save, Sweden

MvdV>> It is not a basic flaw at he.net. I ran a he.net tunnel for
MvdV>> five years and had no problems with outgoing IPv6. It must be
MvdV>> something in your configuration.

Well, if it worked initially, I don't see how my configuration
suddenly can make it not work any more. Especially since it still
works on incoming calls.

Murphy's law, art 13.5: "Nothing was changed", changes to "something was changed, but that should not affect it" and then to "Hmmm, it seems something was changed after all"...

I can't explain it either, but I can see that it is not working as planned...

MvdV>> How about web browsing? Do you see the turtle dancing at
MvdV>> http://www.kame.net/ ?

It's not that easy. As I may have said, I'm running an XP Mini on
my inbound router/fidonet computer. I don't have any browser installed
on it.

But I'll see what netsh may have changed without me knowing about
it -- it's not like it would be the first time netsh is playing games
with me... :(

Well, Nick Boel advised you to upgrade your Windows version. He may have a point, Win XP's IPv6 implementation is incomplete. It doesn't matter for Auntie Abbie who just does a bit of browsing and e-mail, but when you start doing more advanced things, you may run into some problems.

I'll go a bit furth, my advice is: stop trying to use Windows as a router. It was never designed for that and everyone who has ever tried it, reports problems. If you /must/ use a standard desk top as a router, go Linux. But I go one step furhter and say: use something that has hardware designed and optimised for being a router. And just that. OpenWrt has facilities for hosting he.net type tunnels and that will give you a much more stable situation. Plus that all the devices in your LAN that are IPv6 capable will automatically be assigned an IPv6 address from the /64 or /48 subnet you get from he.net. It really is much easier than fighting Windows.

My WRT54GL running OpenWrt has been oprating that way for five years on an "install and forget" basis. I sidetracked it because I got naitive IPv6 and that worked only with the modem/router from the ISP.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
# Origin: he.net certified sage (2:280/5555)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bjorn!

13 Dec 16 01:31, you wrote to all:

Michiel discovered a couple of days ago that I no longer called him
IPv6.

I know that incoming IPv6 calls work, but how about outgoing?
Can you all please confirm that my system no longer calls IPv6?

I found 2 connects from you in my logs in December; both were IPv4. My connections to you continue to be IPv6.

Andrew

--- GoldED+/LNX 1.1.5-b20160322
# Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Bjorn Felten wrote to All <=-

Michiel discovered a couple of days ago that I no longer called him
IPv6.

I know that incoming IPv6 calls work, but how about outgoing?

Can you all please confirm that my system no longer calls IPv6?

Here ya go...

- 16:58 [7084] incoming from 90.231.158.147 (4920)
+ 16:58 [5192] incoming session with 90-231-158-147-no236.tbcn.telia.com [90.231.158.147]
- 16:58 [5192] SYS Felten's Sharp System
- 16:58 [5192] ZYZ Bj=rn Felten
- 16:58 [5192] LOC SSve, Sweden
- 16:58 [5192] NDL 115200,TCP,BINKP
- 16:58 [5192] TIME Tue, 13 Dec 2016 23:01:49 +0100
- 16:58 [5192] VER binkd/1.1a-65/Win32 binkp/1.1
+ 16:58 [5192] addr: 2:203/0@fidonet
+ 16:58 [5192] addr: 2:20/0@fidonet
+ 16:58 [5192] addr: 2:2/2@fidonet
+ 16:58 [5192] addr: 2:203/2@fidonet
- 16:58 [5192] OPT NDA EXTCMD CRYPT
+ 16:58 [5192] Remote supports asymmetric ND mode
+ 16:58 [5192] Remote supports EXTCMD mode
+ 16:58 [5192] Remote requests CRYPT mode
- 16:58 [5192] TRF 669 0
+ 16:58 [5192] Remote has 669b of mail and 0b of files for us
+ 16:58 [5192] pwd protected session (MD5)
- 16:58 [5192] session in CRYPT mode
- 16:58 [5192] receiving 58506ff9.pkt (669 byte(s), off 0)
+ 16:58 [5192] 58506ff9.pkt -> c:\fd\secure\58506ff9.pkt
16:58 [5192] got *.pkt, delayed creating c:\sbbs\data\fidoin.now
16:58 [5192] got *.PKT, delayed creating c:\sbbs\data\fidoin.now
+ 16:58 [5192] rcvd: 58506ff9.pkt (669, 669.00 CPS, 2:203/0@fidonet)
+ 16:58 [5192] done (from 2:203/0@fidonet, OK, S/R: 0/1 (0/669 bytes))

No IPv6 :(


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 3.00-Win32
# Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Bj=rn!

13 Dec 2016 05:50, Bj=rn Felten wrote to Nicholas Boel:

Why must this entire IPv6 be so complicated...?

bah, ipv4 is just the working backup


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.9.0-gentoo (i686))
# Origin: openvpn on its way here (1:261/38.20)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Kees!

13 Dec 2016 11:53, Kees van Eeten wrote to Bj%rn Felten:

Ipv6 is not complicated, the way you use it is.

well i can make it complicated, but i like to not make that route yet

proxy ipv6 to ipv4 here, som would like to make this for ipv6 only fidonet hosts, how big is the problem ?

basicly do not make ipv4 only hostname, do not make ipv6 only hostname, make a single hostname pr fidonet node


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.9.0-gentoo (i686))
# Origin: openvpn on its way here (1:261/38.20)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Benny Pedersen wrote to Bj=rn Felten <=-

Why must this entire IPv6 be so complicated...?

bah, ipv4 is just the working backup

That's true for me. IPv6 is native, IPv4 is tunneled for my BBSs. :)


... I stayed up all night to see where the sun went. Then it dawned on me.
--- MultiMail/Win32 v0.49
# Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Benny Pedersen wrote to Kees van Eeten <=-

basicly do not make ipv4 only hostname, do not make ipv6 only hostname, make a single hostname pr fidonet node

I have two hostnames on one of my BBSs. One is IPv4 only, the other is IPv4/IPv6. The reason for this is the IPv4 only one is given to users, because at this time, the BBS only answers users on IPv4. The other is put into the nodelist, because I run binkd, which is enabled for IPv4 and IPv6.

One day, I hope to be able to put that BBS on IPv6 for users as well, but that needs a software upgrade to a dev version.

The other BBS only has a single hostname (v4/v6), because it runs a dev version of Mystic that answers on both IPv4 and IPv6 for both users and binkp connects.
It's not listed in the IPv6 Fidonet list, simply because it's not a Fidonet node - it is a point on Fidonet and a node on several othernets.


... Flashlight: A case for holding dead batteries.
--- MultiMail/Win32 v0.49
# Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Tony!

15 Dec 2016 08:06, Tony Langdon wrote to Benny Pedersen:

That's true for me. IPv6 is native, IPv4 is tunneled for my BBSs. :)

yes i know users wants ipv6, and i like to get it natively here aswell, i know this will happen when i get fiber optic connection, stay tuned as long its on adsl :=)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.9.0-gentoo (i686))
# Origin: openvpn on its way here (1:261/38.20)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

On 13.12.2016 2:31, Bj%rn Felten wrote:

I know that incoming IPv6 calls work

[3392] outgoing session with eljaco.se:24555 [2001:470:27:302::2]
[3392] SYS Felten's Sharp System

Can you all please confirm that my system no longer calls IPv6?

Confirmed. :(

'Tommi

---
# Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

On 13.12.2016 6:50, Bj%rn Felten wrote:

Why must this entire IPv6 be so complicated...?

No, it is not. Only your XP.. <g>

There is a 'netsh' way to set which address (v4/v6) to use for preferred outgoing. I don't remember it but just do some googling.

'Tommi

---
# Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)