i got today a badly formated pkt file from 2:203/0from
in this pkt it was not valid msg that could not be tossed here, it was
2:292/854
if logs are needed to help finding the bug on dbrigde i can provide it
i got today a badly formated pkt file from 2:203/0
in this pkt it was not valid msg that could not be tossed here, it was from 2:292/854
if logs are needed to help finding the bug on dbrigde i can provide it
2:203/0 Is not running d'Bridge!
When incomming pkt files area
tossed, new pkt files are created for the links!
So if 2:203/0 sends
you bad pkt files,
that's where they are created, and not some random
node down the line...
I also got a ton of old messages today, directly from Ward's system.
So there is (or was) a problem there but, not with badly formated pkt files!
How is this a D'Bridge bug?
2:203/0 create big pkt files, imho not limited so more small files when alo of msgs are comming, possible this system can create files over 2GB barrier with imho make it impossible to toss it on msdos partion
in husky i limit pkt size to 32 Kb
that's where they are created, and not some random
node down the line...
okay, you say no nodes forward bad pkt file creating ?
filesI also got a ton of old messages today, directly from Ward's system.
could this be triggered by some nodes that does not limit size of pkt
?
with gives out of mem problems on downlinks ?
So there is (or was) a problem there but, not with badly formated
pkt files!
logs does not lie
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,037 |
Nodes: | 15 (0 / 15) |
Uptime: | 47:28:41 |
Calls: | 7 |
Calls today: | 7 |
Files: | 95,180 |
D/L today: |
13,733 files (1,858M bytes) |
Messages: | 465,420 |