Getting a "bad packet" report on the SAME pkt each and every time I poll with this thing. Just checking if at least this will get sent and if I even get regular pkts despite the constant error.
--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)

august abolins wrote to All:

Getting a "bad packet" report on the SAME pkt each and every time I poll with this thing. Just checking if at least this will get sent and if I

Looks good here. I hpe you canresolve your bad packet issue somehow.

Ttyl :-),
Al

... At a store: In God we trust; all others pay cash.

--- MBSE BBS v1.0.8 (Linux-x86_64)
* Origin: Equinox BBS - Penticton, BC Canada (1:153/757.2)

Hello, august abolins.
On 08/11/2022 22.08 you wrote:

Getting a "bad packet" report on the SAME pkt each and every time I poll with this thing. Just checking if at least this will get sent and if I even get regular pkts despite the constant error.
--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)

As I wrote in email, try to locate the bad pkt and remove. Would be nice to investigate it too.

--
Tommi
--- Hotdoged/2.13.5/Android
* Origin: ----. .---- .---- (2:221/1.911)

Originally from Alan Ianson to august abolins (08 Nov 2022 19:14):

august abolins wrote to All:

Getting a "bad packet" report on the SAME pkt each and every time I poll
with this thing. Just checking if at least this will get sent and if I

Looks good here. I hpe you canresolve your bad packet issue somehow.

One solution is to reset data in Aftershock android settings but then you lose all.. I did that when upgraded to this .11 version.

--- AfterShock/Android 1.6.11
* Origin: .... ... .. . .. ... .... (2:221/6.60)

Hola August!

08 Nov 22 22:08, august abolins dijo a All:

@MSGID: 2:221/1.59 636b19a0
@TZUTC: -0500
@CHRS: CP437

Getting a "bad packet" report on the SAME pkt each and every time I poll with this thing. Just checking if at least this will get sent and if I even get regular pkts despite the constant error.
--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)
SEEN-BY: 103/705 124/5016 153/757 154/10 203/0 221/1 6 360 230/150 240/1120
SEEN-BY: 240/5832 280/464 5003 5555 292/854 8125 301/1 310/31 341/66 SEEN-BY: 341/234 396/45 423/81 120 460/58 633/280 712/848 770/1
@PATH: 221/1 280/464

Looks good here

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

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

09 Nov 2022 07:18, Tommi Koivula wrote to you:

Getting a "bad packet" report on the SAME pkt each and every time
I poll with this thing. Just checking if at least this will get
sent and if I even get regular pkts despite the constant error.

As I wrote in email, try to locate the bad pkt and remove. Would be
nice to investigate it too.

Yes, it would be nice if you moved the pkt elsewhere and perhaps send it to Tommi so that he can check it, just in case there's something to be reported to Aftershock's author.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada point (2:341/234.1)

09 Nov 2022 07:28, you wrote to Alan Ianson:

One solution is to reset data in Aftershock android settings but then
you lose all.. I did that when upgraded to this .11 version.

I guess you tried to upgrade from 1.6.8 (the one that wasn't in the play store).

I also had to remove everything when upgrading to 1.6.9. But it happened the same to me when I upgraded from an older version to that 1.6.8. It had something different in format, structure or whatever.

I suppose that there shouldn't be issues if upgrading from 1.6.7 (or older) to 1.6.9, .10 or .11.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada point (2:341/234.1)

Getting a "bad packet" report on the SAME pkt each and every time I poll with this thing. Just checking if at least this will get sent and if I even get regular pkts despite the constant error.

You didn't happen to send a ping message to a Mystic system did you?

JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

One solution is to reset data in Aftershock android settings but then you
lose all.. I did that when upgraded to this .11 version.

Do you lose all config settings? ..or just the echo data?

As far as I know it's everything.

JD
--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

Originally from August Abolins to Tommi Koivula (10 Nov 2022 03:53):

Hi Tommi...

Originally from Alan Ianson to august abolins (08 Nov 2022 19:14):

august abolins wrote to All:
Looks good here. I hpe you canresolve your bad packet issue somehow.

One solution is to reset data in Aftershock android settings but then you
lose all.. I did that when upgraded to this .11 version.

Do you lose all config settings? ..or just the echo data?

Everything, but it is not very big job to setup again. However, I wouldn't like to do it every day. ,)

'Tommi

--- AfterShock/Android 1.6.11
* Origin: .... ... .. . .. ... .... (2:221/6.60)

Hi John...

Hello John!
** On Wednesday 09.11.22 - 23:30, you wrote to me:
Huh?

There is a bug in a specific version of Mystic BBS that returns a bad packet if you ping it.
JD

I do not recall building a specific message for ping purposes, no.

Ciao!
/|ug (https://t.me/aabolins)

--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hello Carlos!

As I wrote in email, try to locate the bad pkt and
remove. Would be nice to investigate it too.

Yes, it would be nice if you moved the pkt elsewhere and
perhaps send it to Tommi so that he can check it, just in
case there's something to be reported to Aftershock's
author.

And.. THIS particular message did not seem to show up at all.

I think I need a more capable "Files" app than the default one
on the Android so that I can search for the pkt and move it.
Any suggestions?


--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello John!

** On Wednesday 09.11.22 - 23:30, you wrote to me:

You didn't happen to send a ping message to a Mystic system did you?

Huh?

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello John!

** On Wednesday 09.11.22 - 23:30, you wrote to me:

You didn't happen to send a ping message to a Mystic system did you?

Huh?

There is a bug in a specific version of Mystic BBS that returns a bad packet if you ping it.

JD

--- AfterShock/Android 1.6.8
* Origin: FireCat Mobile (4:920/1.1)

On 10.11.2022 7:52, August Abolins -> Carlos Navarro :

Hello Carlos!

TK>> As I wrote in email, try to locate the bad pkt and
TK>> remove. Would be nice to investigate it too.

CN> Yes, it would be nice if you moved the pkt elsewhere and
CN> perhaps send it to Tommi so that he can check it, just in
CN> case there's something to be reported to Aftershock's
CN> author.

And.. THIS particular message did not seem to show up at all.

I think I need a more capable "Files" app than the default one
on the Android so that I can search for the pkt and move it.
Any suggestions?

Total Commander is pretty good.

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
* Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Total Commander is pretty good.

The one by Ghisler? It says that it contains ads.


--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)

Hi august.

10 Nov 22 09:20:02, you wrote to me:

Total Commander is pretty good.

The one by Ghisler?

Yes.

It says that it contains ads.

Not too much.

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/1)

As I wrote in email, try to locate the bad pkt and
remove. Would be nice to investigate it too.

Yes, it would be nice if you moved the pkt elsewhere and
perhaps send it to Tommi so that he can check it, just in
case there's something to be reported to Aftershock's
author.

And.. THIS particular message did not seem to show up at all.

I think I need a more capable "Files" app than the default one
on the Android so that I can search for the pkt and move it.
Any suggestions?

This is just and reply/quote test to see if this version of Aftershock had issues quoting messages from OpenXP.

--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)

Hi August,


18 Nov 22 21:23, august abolins schrieb an August Abolins:

@REPLY: 1:153/757.21@fidonet 024d90e1
@MSGID: 2:221/1.59 63783e14
@TZUTC: -0500
@CHRS: CP437

As I wrote in email, try to locate the bad pkt and
remove. Would be nice to investigate it too.

Yes, it would be nice if you moved the pkt elsewhere and
perhaps send it to Tommi so that he can check it, just in
case there's something to be reported to Aftershock's
author.

And.. THIS particular message did not seem to show up at all.

I think I need a more capable "Files" app than the default one
on the Android so that I can search for the pkt and move it.
Any suggestions?

This is just and reply/quote test to see if this version of Aftershock
had issues quoting messages from OpenXP.

--- AfterShock/Android 1.6.11
* Origin: Mobile Pix (2:221/1.59)
SEEN-BY: 30/0 203/0 221/1 6 360 230/150 240/1120 1634 8002 8005
280/464 5003
SEEN-BY: 280/5555 291/111 292/854 301/1 313/41 335/364 371/0 382/147 423/81
SEEN-BY: 530/204 3634/12
@PATH: 221/1 240/1120

Tschuesz,

Siggi

--- GoldED+/LNX 1.1.5--b20170303
* Origin: Powert by *Fidian* > kuehlbox.wtf/fidian (2:240/1120.1210)

18 Nov 2022 21:23, you wrote to you:

This is just and reply/quote test to see if this version of Aftershock
had issues quoting messages from OpenXP.

It's ok, but that is because Tommi's hpt sends you the packets without the LF's.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada point (2:341/234.1)

It's ok, but that is because Tommi's hpt sends you the packets without
the LF's.

Excellent. Thx for that technical detail!

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)