I noticed there wasn't any new echomail msgs in a while and I found
this li'l stinker.. deleted 90F59CFC.PKT and back to good, but why
would this happen?
why
would this happen?
Sounds like a stinky packet. Do you still have that packet to
inspect?\
Sounds like a stinky packet. Do you still have that packet to inspect?\
Ttyl :-),
Al
Sounds like a stinky packet. Do you still have that packet to
inspect?
I do. I've never inspected a packet; sounds devious. What can we find
in it?
Sounds like a stinky packet. Do you still have that packet to
inspect?
I do. I've never inspected a packet; sounds devious. What can we find in it?
If we are lucky we can find and solve the issue. We don't want tossers just quitting like that.
If you can make that packet available on the web of ftp site I'll have a look and see if I can see any issues with it.
i don't have any net presence besides the BBS. the login is quick w/full access if you want to DL it from the file area 'network' i just added w/the packet. nightvault.fsxnet.nz:2323
I just tried to download it, but it said i don't have access?
oops! i had s25 instead of s20 for the file area... sorry!
If you can make that packet available on the web of ftp site I'll
have a look and see if I can see any issues with it.
i don't have any net presence besides the BBS. the login is quick
w/full access if you want to DL it from the file area 'network' i just added w/the packet. nightvault.fsxnet.nz:2323
I'll come by and grab it in a minute or two..
pktinfo tells me that the fromusername field is empty so the message header is wrong. It is a corrupt packet.
pktinfo tells me that the fromusername field is empty so the message
pktinfo tells me that the fromusername field is empty so the message
header is wrong. It is a corrupt packet.
where do i get pktinfo and pktdump? =)
You can grab my copy here..
http://trmb.synchro.net
pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.
It looks like the packet was written correctly, then re-written over
two bytes off.
So while mystic should discard that packet as you say,
more concerning is whatever the hub is running causing packets like
that?
The message is FROM a synchronet system, but I suspect it's not
synchronet to blame but whatever is in between.
http://trmb.synchro.net/pktdump
Yes, packets like that will not do anyone or any tosser any good.
I doubt it too. I toss packets to and from Synchronet all day. I've
never had any issues with a Synchronet produced packet.
Hello fang-castro,
You can grab my copy here..
You can grab my copy here..
http://trmb.synchro.net/pktdump
I preserved this and posted it to the Fidonet Mystic echo, where
hopefully a more graceful failure can be included in a future version.
There appears to be only one line in the PATH: 895/7 (daryl's node) is he the hub for you two on hobby net?
I noticed there wasn't any new echomail msgs in a while and I found this li'l stinker.. deleted 90F59CFC.PKT and back to good, but why would this happen?
pktinfo tells me that the fromusername field is empty so the message header is wrong. It is a corrupt packet.
http://trmb.synchro.net/pktdump
Hey thanks for this. Hope you don't mind that I grabbed it as well.
I have a separate problem of my own where Mystic is choking on a
packet and it ran fine on my Ubuntu system.
Opening ./9FC80759.PKT
./9FC80759.PKT Packet Type 2+ (prod: 0111, rev: 3.0) from 954:895/1 to 954:895/31 ./9FC80759.PKT 00003A Corrupted Message Header (DateTime)
I preserved this and posted it to the Fidonet Mystic echo, where
hopefully a more graceful failure can be included in a future version.
pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.
I would suggest that fix the tosser so if that happens it defaults to
ALL.
pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.
I would suggest that fix the tosser so if that happens it defaults to ALL.
Every tosser in use would need to be updated to do that and I don't
think that will happen.
No, especially since the pktinfo isn't exactly right, the packet is corrupt, that was just the first thing it tripped up on (the
fromusername wasn't null terminated) even if you changed from to ALL,
it would then have tripped up on the to field being empty, the subject being empty and the entire message being empty because of no null termination between from, to and subject.
A tosser shouldn't attempt to fix a packet, the other tosser shouldn't create dodgy packets.
I think in this instance, mystic tosser needs to be fixed to not
segfault on a dodgy packet, and Platnium Xpress or whatever hobby net
is using needs to be fixed to not create dodgy packets in the first
place.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 09:12:50 |
Calls: | 4,643 |
Calls today: | 6 |
Files: | 8,491 |
Messages: | 348,634 |