I run the latest Synchronet for Linux. My problem is when any message packet makes it to the other side it fails to process or get imported. The error we seem to be getting is "Not a type 2 packet." in my echocfg we have it set to type 2+ packet. I have a networked drive to a winxp argus mailer that sends it out. I seem to be getting inbound packets okay. I receive netmails okay and messages okay. I can send netmail out okay. It seems to be getting to the other node. But fail's to process. I don't have a clue why or what to check for. Thanks...
Re: Packet Problem
By: Timesoarer to All on Mon Nov 18 2013 04:28 am
I run the latest Synchronet for Linux. My problem is when any message packet makes it to the other side it fails to process or get imported. The error we seem to be getting is "Not a type 2 packet." in my echocfg we have it set to type 2+ packet. I have a networked drive
to a winxp argus mailer that sends it out. I seem to be getting
inbound packets okay. I receive netmails okay and messages okay. I can send netmail out okay. It seems to be getting to the other node. But fail's to process. I don't have a clue why or what to check for. Thanks...
Okay... so FidoNet packet I assume.
What program is displaying the error "Not a type 2 packet"? Is it possible that program doesn't support type 2+ packets? What is the "other side" in this context?
Re: Packet Problem
By: Timesoarer to All on Mon Nov 18 2013 04:28 am
I run the latest Synchronet for Linux. My problem is when any message packet makes it to the other side it fails to process or get imported. The error we seem to be getting is "Not a type 2 packet." in my echocfg we have it set to type 2+ packet. I have a networked drive to a winxp argus mailer that sends it out. I seem to be getting inbound packets okay. I receive netmails okay and messages okay. I can send netmail out okay. It seems to be getting to the other node. But fail's to process. I don't have a clue why or what to check for. Thanks...
Okay... so FidoNet packet I assume.
yep
What program is displaying the error "Not a type 2 packet"? Is it possible that program doesn't support type 2+ packets? What is the
"other side" in this context?
right now I am helping him, I am running sbbs 3.16 (build date 11/3/13)
win. I am under win. 7 home (32 bit), here a line from the sbbsecho.log
file : 11/17/13 21:50:56 d:\sbbs\taurus\inbox\secure\E17BE35C.PKT is not a type 2 packet (type=30319)
if you would like to see the file (E17BE35C.PKT) let me know and I'll send it over by qwk, in a zip file?
Re: Re: Packet Problem
By: Lord Time to Digital Man on Thu Nov 28 2013 08:45 pm
Re: Packet Problem
By: Timesoarer to All on Mon Nov 18 2013 04:28 am
I run the latest Synchronet for Linux. My problem is when
any message packet makes it to the other side it fails to process or get imported. The error we seem to be getting is "Not a type 2 packet." in my echocfg we have it set to type 2+ packet. I have a networked drive to a winxp argus mailer that sends it out. I
seem to be getting inbound packets okay. I receive netmails okay and messages okay. I can send netmail out okay. It seems to be getting to the other node. But fail's to process. I don't have a clue why or what to check for. Thanks...
Okay... so FidoNet packet I assume.
yep
What program is displaying the error "Not a type 2 packet"? Is it possible that program doesn't support type 2+ packets? What is the "other side" in this context?
right now I am helping him, I am running sbbs 3.16 (build date 11/3/13) win. I am under win. 7 home (32 bit), here a line from the sbbsecho.log file : 11/17/13 21:50:56 d:\sbbs\taurus\inbox\secure\E17BE35C.PKT is not a type 2 packet (type=30319)
Sounds like a corrupted packet.
if you would like to see the file (E17BE35C.PKT) let me know and I'll send it over by qwk, in a zip file?
Sure you send it or upload it (zipped or not, doesn't matter).
Or you can
download ftp://vert.synchro.net/main/bbs/pktdump.exe and use that to check/view the packet header.
It'll likely error-out with a similar error if the packet header is
corrupt.
right now I am helping him, I am running sbbs 3.16 (build date 11/3/13) win. I am under win. 7 home (32 bit), here a line from the sbbsecho.log file : 11/17/13 21:50:56 d:\sbbs\taurus\inbox\secure\E17BE35C.PKT is not a type 2 packet (type=30319)
Sounds like a corrupted packet.
if you would like to see the file (E17BE35C.PKT) let me know and I'll send it over by qwk, in a zip file?
Sure you send it or upload it (zipped or not, doesn't matter).
didn't zip it, it will go over to your bbs, at the same this message goes out
Or you can
download ftp://vert.synchro.net/main/bbs/pktdump.exe and use that to check/view the packet header.
hmm, I won't know what to look for
It'll likely error-out with a similar error if the packet header is corrupt.
hmmm, could be or someelse, only you would know what it is
if you would like to see the file (E17BE35C.PKT) let me know and I'll
send it over by qwk, in a zip file?
Sure you send it or upload it (zipped or not, doesn't matter). Or you
can download ftp://vert.synchro.net/main/bbs/pktdump.exe and use that to check/view the packet header. It'll likely error-out with a similar
error if the packet header is corrupt.
pktdump 01220004.tu0pktdump rev 1.7 - Dump FidoNet Packets
pktdump 01220004.tu1pktdump rev 1.7 - Dump FidoNet Packets
you can download ftp://vert.synchro.net/main/bbs/pktdump.exe and use
that to check/view the packet header.
When/how was this packet copied? Can you confirm if this packet was captured (copied) before it was archived into a bundle and sent between mailers or after?
you can download ftp://vert.synchro.net/main/bbs/pktdump.exe and use
that to check/view the packet header.
That sounds like a really cool utility. I've tried downloading it from 2 different locations and get a error each time. Could you check on that file when you get a chance and see if there's a problem on your end?
go on his bbs and download it. that's what i just did.
Re: Re: Packet Problem
By: Mro to Kurt Weiske on Tue Dec 17 2013 11:00 pm
go on his bbs and download it. that's what i just did.
Weird. You misunderstood. I tried downloading it from DM's FTP site from
two difference locations and it didn't work. This morning I got a 550 file not found error.
go on his bbs and download it. that's what i just did.
Re: Re: Packet Problem
By: Mro to Kurt Weiske on Tue Dec 17 2013 11:00 pm
go on his bbs and download it. that's what i just did.
FYI, I had to use my login account on Vertrauen to download the file. anonymous FTP didn't work.
Re: Re: Packet Problem
By: Digital Man to Lord Time on Sun Dec 01 2013 05:40 pm
if you would like to see the file (E17BE35C.PKT) let me know and I'll
send it over by qwk, in a zip file?
Sure you send it or upload it (zipped or not, doesn't matter). Or you can download ftp://vert.synchro.net/main/bbs/pktdump.exe and use that to check/view the packet header. It'll likely error-out with a similar error if the packet header is corrupt.
It did ERROR out with the exact same error.
pktdump 01220004.tu0pktdump rev 1.7 - Dump FidoNet Packets
Opening 01220004.tu0
01220004.tu0 Packet Type 429 (unsupported packet type)
pktdump 01220004.tu1pktdump rev 1.7 - Dump FidoNet Packets
Opening 01220004.tu1
01220004.tu1 Packet Type 322 (unsupported packet type)
Tested packet on FTN Computer.WinXP..The packet came from Synchronet Linux System.
I couldn't find anything about Pack Type 429 or 322? What could I check
for now?
Re: Re: Packet Problem
By: Timesoarer to Digital Man on Tue Dec 17 2013 09:53 am
you can download ftp://vert.synchro.net/main/bbs/pktdump.exe and use
that to check/view the packet header.
That sounds like a really cool utility. I've tried downloading it from 2 different locations and get a error each time. Could you check on that file when you get a chance and see if there's a problem on your end?
Re: Re: Packet Problem
By: Digital Man to Lord Time on Mon Dec 02 2013 11:21 pm
q
When/how was this packet copied? Can you confirm if this packet was captured (copied) before it was archived into a bundle and sent
between mailers or after?
Okay, the test I ran on a different packet, I shut the FTN mailer down.
Went in a message base wrote a test message. Took the file that it would have sent off to the other bbs. And ran pkdump on it and got the same error. The packet would have been outbound to Time Warp it never had a chance to go through the mailer the packet was transfered from networked Linux box to the Mailer Via samba. I never had this issue before. Is there anything I can do to help figure out what is happening give the word I'll do my best to run what ever tests need to be done. The packet Rob
Sent you was tossed through the mailer far as I know... Thanks--- No problem with inbound. Is there someting in the configuration I can check for? Thanks Again.
What 2 different locations? What's the error? There doesn't seem to be
any problem on this end.
Re: Re: Packet Problem
By: Digital Man to Kurt Weiske on Thu Jan 02 2014 12:22 am
What 2 different locations? What's the error? There doesn't seem to be any problem on this end.
I was able to get it by logging in - anonymous FTP didn't work from home or from my work network.
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 35:12:55 |
Calls: | 15,172 |
Calls today: | 1 |
Files: | 19,859 |
D/L today: |
21 files (4,251K bytes) |
Messages: | 1,692,732 |