First message sent via echomail is a VERY long time. Just checking that all is ok before I break it. :)


---
* Origin: -={ The Digital Post }=- (1:266/420)

Hello Scott,

@MSGID: 1:266/420 61494cd3
@PID: GED+LNX 1.1.5-b20180707
@CHRS: UTF8 2
@TZUTC: -0400
@TID: hpt/lnx 1.9.0-cur 2021-05-15
First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

---
* Origin: -={ The Digital Post }=- (1:266/420)
SEEN-BY: 15/0 19/36 106/201 116/18 120/302 331 124/5009 129/12 102 125
160 165
SEEN-BY: 153/757 7715 218/700 222/2 230/150 152 240/1120 250/1 261/1
38 100 220
SEEN-BY: 261/1466 266/32 75 420 512 618 267/152 154 155 275/100
282/1056 1060
SEEN-BY: 291/100 111 301/1 320/119 219 340/400 341/66 396/45 640/1321 712/848
SEEN-BY: 801/161 189 3634/12 5020/1042
@PATH: 266/420 512 261/38

Looks OK to me.. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Scott,

On Monday September 20 2021 23:07, you wrote to All:

First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

+ 09:18 [2416] call to 1:266/420@fidonet
09:18 [2416] trying f420.n266.z1.binkp.net [2601:48:c500:9340::1899]...
? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
10060} Connection timed out
09:18 [2416] trying f420.n266.z1.binkp.net [68.84.122.190]...
? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
10060} Connection timed out


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Michiel,

On 2021-09-21 09:19:13, you wrote to Scott Street:

First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

MvdV> + 09:18 [2416] call to 1:266/420@fidonet
MvdV> 09:18 [2416] trying f420.n266.z1.binkp.net
MvdV> [2601:48:c500:9340::1899]...
MvdV> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV> 10060} Connection timed out
MvdV> 09:18 [2416] trying f420.n266.z1.binkp.net [68.84.122.190]...
MvdV> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV> 10060} Connection timed out

Confirmed:

+ 21 Sep 12:52:15 [16607] call to 1:266/420@fidonet
21 Sep 12:52:16 [16607] trying digitalpost.freeddns.org [2601:48:c500:9340::6cf4]...
? 21 Sep 12:54:23 [16607] connection to 1:266/420@fidonet failed: Connection timed out
21 Sep 12:54:23 [16607] trying digitalpost.freeddns.org [68.84.122.190]:24554...
? 21 Sep 12:56:30 [16607] connection to 1:266/420@fidonet failed: Connection timed out


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Tuesday September 21 2021 12:58, you wrote to me:

MvdV>> [2416] trying f420.n266.z1.binkp.net
MvdV>> [2601:48:c500:9340::1899]...
^^^^

[16607] trying digitalpost.freeddns.org
2601:48:c500:9340::6cf4]...

^^^^

Different IPv6 address...

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Michiel,

On 2021-09-21 14:10:43, you wrote to me:

MvdV>>> [2416] trying f420.n266.z1.binkp.net
MvdV>>> [2601:48:c500:9340::1899]...
MvdV> ^^^^

[16607] trying digitalpost.freeddns.org
2601:48:c500:9340::6cf4]...

MvdV> ^^^^

MvdV> Different IPv6 address...

It must have been updated, because now:

# host f420.n266.z1.binkp.net
f420.n266.z1.binkp.net is an alias for digitalpost.freeddns.org. digitalpost.freeddns.org has address 68.84.122.190
digitalpost.freeddns.org has IPv6 address 2601:48:c500:9340::6cf4


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hola Scott!

20 Sep 21 23:07, Scott Street dijo a All:

@MSGID: 1:266/420 61494cd3
@PID: GED+LNX 1.1.5-b20180707
@CHRS: UTF8 2
@TZUTC: -0400
@TID: hpt/lnx 1.9.0-cur 2021-05-15
First message sent via echomail is a VERY long time. Just checking that all is ok before I break it. :)

---
* Origin: -={ The Digital Post }=- (1:266/420)
SEEN-BY: 15/0 19/36 106/201 116/18 120/302 331 124/5009 129/12 102 125 160 165
SEEN-BY: 153/757 7715 218/700 222/2 230/150 152 240/1120 250/1 261/1 38 100 220
SEEN-BY: 261/1466 266/32 75 420 512 618 267/152 154 155 275/100 282/1056 1060
SEEN-BY: 291/100 111 301/1 320/119 219 340/400 341/66 396/45 640/1321 712/848
SEEN-BY: 801/161 189 3634/12 5020/1042
@PATH: 266/420 512 261/38

Ok here :)

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20180707 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Scott,

First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

It made it to Arkansas.

Daryl

... Support bacteria. It's the only culture some people have.
=== MultiMail/Win v0.52
--- SBBSecho 3.14-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:2320/33)

20 Sep 2021 23:07, you wrote to All:

@MSGID: 1:266/420 61494cd3
@PID: GED+LNX 1.1.5-b20180707
@CHRS: UTF8 2
@TZUTC: -0400
@TID: hpt/lnx 1.9.0-cur 2021-05-15
First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

Looks ok. I would only suggest you change your CHRS kludge to UTF-8 (with a dash).

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

* Carbon copied to Scott Street 1:266/420

Hi Scott,

On 2021-09-21 09:19:13, Michiel van der Vlist wrote to you:

First message sent via echomail is a VERY long time. Just checking
that all is ok before I break it. :)

MvdV> + 09:18 [2416] call to 1:266/420@fidonet
MvdV> 09:18 [2416] trying f420.n266.z1.binkp.net
MvdV> [2601:48:c500:9340::1899]...
MvdV> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV> 10060} Connection timed out
MvdV> 09:18 [2416] trying f420.n266.z1.binkp.net [68.84.122.190]...
MvdV> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV> 10060} Connection timed out

Still no connect possible to 1:266/420. My system has been trying every 2 hours since above date...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Wilfred!

01 ®ªâ 21 15:45, Wilfred van Velzen -> Scott Street:

MvdV>> + 09:18 [2416] call to 1:266/420@fidonet
MvdV>> 09:18 [2416] trying f420.n266.z1.binkp.net
MvdV>> [2601:48:c500:9340::1899]...
MvdV>> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV>> 10060} Connection timed out
MvdV>> 09:18 [2416] trying f420.n266.z1.binkp.net [68.84.122.190]...
MvdV>> ? 09:18 [2416] connection to 1:266/420@fidonet failed: {W32 API error
MvdV>> 10060} Connection timed out

Still no connect possible to 1:266/420. My system has been trying every 2 hours since above date...

[fido@host-187 ~]$ host f420.n266.z1.binkp.net
f420.n266.z1.binkp.net is an alias for digitalpost.freeddns.org. digitalpost.freeddns.org has address 68.84.122.190
digitalpost.freeddns.org has IPv6 address 2601:48:c500:9340::5477 [fido@host-187 ~]$ ping 68.84.122.190
PING 68.84.122.190 (68.84.122.190) 56(84) bytes of data.
^C
-+- 68.84.122.190 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12268ms

[fido@host-187 ~]$ ping 2601:48:c500:9340::5477
PING 2601:48:c500:9340::5477(2601:48:c500:9340::5477) 56 data bytes
^C
-+- 2601:48:c500:9340::5477 ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 15380ms

Have nice nights.
Stas Mishchenkov.

--- ‘¢®¡®¤­ ï ¡ ¡  ¤®«¦­  ¯®ª §ë¢ âì á¨á쪨. ‡ ¬ã¦­ïï ­¥ ¤®«¦­ ,­® ⮦¥ ¢¯à ¢¥
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

01 Oct 21 15:45, you wrote to me:

Still no connect possible to 1:266/420. My system has been trying
every 2 hours since above date...

After much back and forth with Comcast/Xfinity; I have found that I needed to drop IPv6 support for incoming connections. A shame really, because Comcast's gateways do not support UPNP for IPv6. Oh, and why UPNP? Because the router "calls home" to Comcast periodically (often?) and gets new configuration information and it seems that in my region, the port forwards are not saved. So I discovered a simple workaround for there junk software; now two things happen, first when my DHCP client detects a network change it runs my DNS update script and that script now includes 'upnpc' commands to refresh the port mappings. The script also runs every five hours just in case the gateway's IP address changed without changes on the inside.

I wish I thought of UPNP a week or so ago; would have saved me many hours of hold time and fustration.

Thanks all for reading,
Scott

---
* Origin: -={ The Digital Post }=- (1:266/420)

Hi Scott,

On 2021-10-04 23:54:02, you wrote to me:

Still no connect possible to 1:266/420. My system has been trying
every 2 hours since above date...

After much back and forth with Comcast/Xfinity; I have found that I needed
to drop IPv6 support for incoming connections. A shame really, because Comcast's gateways do not support UPNP for IPv6. Oh, and why UPNP? Because the router "calls home" to Comcast periodically (often?) and gets new configuration information and it seems that in my region, the port forwards are not saved. So I discovered a simple workaround for there junk
software; now two things happen, first when my DHCP client detects a network change it runs my DNS update script and that script now includes 'upnpc' commands to refresh the port mappings. The script also runs every five hours just in case the gateway's IP address changed without changes on
the inside.

Do you have a choice of providers in your area? ;)

I wish I thought of UPNP a week or so ago; would have saved me many
hours of hold time and fustration.

I can confirm it's working now:

+ 05 Oct 04:22:04 [9354] call to 1:266/420@fidonet
05 Oct 04:22:04 [9354] trying digitalpost.freeddns.org [2601:48:c500:9340::da3]...
? 05 Oct 04:24:12 [9354] connection to 1:266/420@fidonet failed: Connection timed out
+ 05 Oct 04:24:12 [9354] holding 1:266/420@fidonet (2021/10/05 05:24:12)
05 Oct 04:24:12 [9354] trying digitalpost.freeddns.org [68.84.122.190]:24554...
05 Oct 04:25:15 [9354] connected
+ 05 Oct 04:25:15 [9354] outgoing session with digitalpost.freeddns.org:24554 [68.84.122.190]
- 05 Oct 04:25:15 [9354] OPT CRAM-MD5-cba663c3464ec014460c6b1685ac3fee
+ 05 Oct 04:25:15 [9354] Remote requests MD mode
- 05 Oct 04:25:15 [9354] SYS The Digital Post
- 05 Oct 04:25:15 [9354] ZYZ Scott Street
- 05 Oct 04:25:15 [9354] LOC Wilmington, DE
- 05 Oct 04:25:15 [9354] NDL 115200,CM,IBN
- 05 Oct 04:25:15 [9354] TIME Mon, 4 Oct 2021 22:25:15 -0400
- 05 Oct 04:25:15 [9354] VER binkd/1.1a-112/Linux binkp/1.1
+ 05 Oct 04:25:15 [9354] addr: 1:266/420@fidonet
- 05 Oct 04:25:16 [9354] TRF 0 0
+ 05 Oct 04:25:16 [9354] Remote has 0b of mail and 0b of files for us
- 05 Oct 04:25:16 [9354] OPT EXTCMD NR GZ BZ2
+ 05 Oct 04:25:16 [9354] Remote supports EXTCMD mode
+ 05 Oct 04:25:16 [9354] Remote requests NR mode
+ 05 Oct 04:25:16 [9354] Remote supports GZ mode
+ 05 Oct 04:25:16 [9354] Remote supports BZ2 mode
- 05 Oct 04:25:16 [9354] we are in NR mode
+ 05 Oct 04:25:16 [9354] done (to 1:266/420@fidonet, OK, S/R: 0/0 (0/0 bytes))
05 Oct 04:25:16 [9354] session closed, quitting...

(Trying IPv6 first was probably a dns cache "issue", when I check your host name now, only a IPv4 address is shown)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Scott,

On Monday October 04 2021 23:54, you wrote to Wilfred van Velzen:

After much back and forth with Comcast/Xfinity; I have found that I needed to drop IPv6 support for incoming connections. A shame really, because Comcast's gateways do not support UPNP for IPv6.

The general consensus among the IPv6 Gurus is that UPNP should not be used for IPv6.

Oh, and why UPNP? Because the router "calls home" to Comcast
periodically (often?) and gets new configuration information and it
seems that in my region, the port forwards are not saved.

Port forwarding is an IPv4 thing. In IPv6 one just creates a hole in the firewall to let the port go through.

So I discovered a simple workaround for there junk software; now two things happen, first when my DHCP client detects a network change it
runs my DNS update script and that script now includes 'upnpc'
commands to refresh the port mappings. The script also runs every
five hours just in case the gateway's IP address changed without
changes on the inside.

I can see why that would not work for IPv6.

I wish I thought of UPNP a week or so ago; would have saved me many
hours of hold time and fustration.

You may want to ask Andrew Leary (1:320/219) for help. He has IPv6 up and running on a Comcast connection. I don't know how he does it, but he obviously has found a way.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hello Scott,

Wednesday October 06 2021 12:52, I wrote to you:

You may want to ask Andrew Leary (1:320/219) for help. He has IPv6 up
and running on a Comcast connection. I don't know how he does it, but
he obviously has found a way.

Two more things come to mind.

1) If you still have ougoing IPv6, I could add you to the list of IPv6 nodes as "OO". (Outgoing Only). Could you poll my system so that I can see if you support outgoing ipv6?
2) You are invited to join the IPv6 echo. There is a lot of expertise there, maybe there is someone that has a solution for your problem.

Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Scott;

Michiel van der Vlist wrote to Scott Street <=-

You may want to ask Andrew Leary (1:320/219) for help. He has IPv6 up
and running on a Comcast connection. I don't know how he does it, but
he obviously has found a way.

I also run IPv6 here at 1:142/103 bbs.n1uro.com:

bbs.n1uro.com has address 44.88.0.9
bbs.n1uro.com has IPv6 address 2001:470:8a1e::3

... and I also am on a comcast connection, but I use Hurricane Electric
as an IPv6 tunnel since Comcast blocks multiple ports on IPv6 as they
do IPv4. A tunnel gets past their filters.

... What If Area 51 was where all the missing odd socks turned up?
--- MultiMail/Linux v0.52
* Origin: SBBS - Carnage! Hartford, Ct (1:142/103)

06 Oct 21 13:34, you wrote to me:

You may want to ask Andrew Leary (1:320/219) for help. He has
IPv6 up and running on a Comcast connection. I don't know how he
does it, but he obviously has found a way.

I will investigate that.

1) If you still have ougoing IPv6, I could add you to the list of IPv6 nodes as "OO". (Outgoing Only). Could you poll my system so that I can
see if you support outgoing ipv6?

Yes indeed, my goal in setting up was to have a IPv6 system and only fall back

+ 06 Oct 14:23:47 [2970] call to 2:280/5555@fidonet
06 Oct 14:23:47 [2970] trying f5555.n280.z2.binkp.net [2001:1c02:1104:5600:f1d0:2:280:5555]... 06 Oct 14:23:47 [2970] connected + 06 Oct 14:23:47 [2970] outgoing session with f5555.n280.z2.binkp.net:24554 [2001:1c02:1104:5600:f1d0:2:280:5555]
...

2) You are invited to join the IPv6
echo. There is a lot of expertise there, maybe there is someone that
has a solution for your problem.

I don't see any echos listed about IPv6 or IP on my feed - is the echo


Scott


---
* Origin: -={ The Digital Post }=- (1:266/420)

Hello Scott,

On Wednesday October 06 2021 17:33, you wrote to me:

1) If you still have ougoing IPv6, I could add you to the list of
IPv6 nodes as "OO". (Outgoing Only). Could you poll my system so
that I can see if you support outgoing ipv6?

Yes indeed, my goal in setting up was to have a IPv6 system and only
fall back

+ 06 Oct 14:23:47 [2970] call to 2:280/5555@fidonet
06 Oct 14:23:47 [2970] trying f5555.n280.z2.binkp.net [2001:1c02:1104:5600:f1d0:2:280:5555]... 06 Oct 14:23:47 [2970] connected + 06 Oct 14:23:47 [2970] outgoing session with f5555.n280.z2.binkp.net:24554 [2001:1c02:1104:5600:f1d0:2:280:5555]

- 06 Oct 20:23:49 [688] incoming from 2601:48:c500:9340::9d70 (39476)
+ 06 Oct 20:23:50 [3236] incoming session with 2601:48:c500:9340::9d70
- 06 Oct 20:23:50 [3236] SYS The Digital Post
- 06 Oct 20:23:50 [3236] ZYZ Scott Street
- 06 Oct 20:23:50 [3236] LOC Wilmington, DE
- 06 Oct 20:23:50 [3236] NDL 115200,CM,IBN
- 06 Oct 20:23:50 [3236] TIME Wed, 6 Oct 2021 14:23:47 -0400
- 06 Oct 20:23:50 [3236] VER binkd/1.1a-112/Linux binkp/1.1
+ 06 Oct 20:23:50 [3236] addr: 1:266/420@fidonet

Yep! you have outgoing IPv6.

2) You are invited to join the IPv6
echo. There is a lot of expertise there, maybe there is someone
that has a solution for your problem.

I don't see any echos listed about IPv6 or IP on my feed - is the echo

It is available from various sources in Z1. You may have to look a bit further than your direct link. It is available at 1:261/38. So you can ask your uplink to link there.


Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)