On 01 Dec 2019 at 09:55p, Black Panther pondered and said...

LinkDefaults begin
ArcmailSize 10000
PktSize 2500

I think these are too big. Well at least compared to what we had set in
Mystic they are. The defaults for nodes was 2048 and 512 respectively. 10
megs and 2.5 megs seem big to me Dan.

allowEmptyPktPwd on

why did you opt to use this, docs suggest 'off' is the best and is the
default state, so the keyword could be omitted.

allowPktAddrDiffer off

The default setting for this, according to the docs is off, so this could be omitted I think

Packer none

So you're opting to send every node raw packets?
Wouldn't that negate the arc size stuff earlier?
I'm still going to compress NET 1 into arc bundles except for nodes that expressly asked for raw packets..

Level 200

need to suss this

ForwardRequests off
AutoCreate on
CreateAreasCase Upper
areafixName Areafix
ArcNetmail on
packNetmail off
EchomailFlavour crash
netMailFlavour crash
Flavour crash
AutoAreaCreateSubdirs off
filefixName FileFix
FileEchoFlavour Normal
AutoFileCreateSubdirs off
LinkDefaults end

i've lost the will at this point :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 07 Dec 2019, Avon said the following...

ArcmailSize 10000
PktSize 2500

I think these are too big. Well at least compared to what we had set in Mystic they are. The defaults for nodes was 2048 and 512 respectively. 10 megs and 2.5 megs seem big to me Dan.

Yeah, it is a bit big... I could bring that down a bit... Or a lot... :)

allowEmptyPktPwd on

why did you opt to use this, docs suggest 'off' is the best and is the default state, so the keyword could be omitted.

Of the nodes on hub 4, there is only one that is using a packet password.
With this set, the packets won't be put in the unsecure inbound.

allowPktAddrDiffer off

The default setting for this, according to the docs is off, so this
could be omitted I think

It looks nice there. ;) I'll be going through the config and doing some cleaning, now that things are working right.

Packer none

So you're opting to send every node raw packets?
Wouldn't that negate the arc size stuff earlier?
I'm still going to compress NET 1 into arc bundles except for nodes that expressly asked for raw packets..

That started when I was having some issues with un/zip on Windows. I just haven't changed it back yet.

Level 200

need to suss this

Make sure your uplinks, in this case, 1/100, is set to a higher level than nodes. I have 1/100 set at 200, and all the nodes set to 100. Also, 1/100 is the only one set up to allow auto-creating of echos. I figured it would be a bit redundant to have all nodes set that way.

filefixName FileFix
FileEchoFlavour Normal
AutoFileCreateSubdirs off
LinkDefaults end

i've lost the will at this point :)

Most of these, do exactly what they sound like they should. :) It's really
not too bad once you get one set up, you can copy/paste for others.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 06 Dec 2019 at 09:04p, Black Panther pondered and said...

allowEmptyPktPwd on

why did you opt to use this, docs suggest 'off' is the best and is th default state, so the keyword could be omitted.

Of the nodes on hub 4, there is only one that is using a packet password. With this set, the packets won't be put in the unsecure inbound.

Ah OK, thanks :)

allowPktAddrDiffer off

The default setting for this, according to the docs is off, so this could be omitted I think

It looks nice there. ;) I'll be going through the config and doing some cleaning, now that things are working right.

:)

Make sure your uplinks, in this case, 1/100, is set to a higher level
than nodes. I have 1/100 set at 200, and all the nodes set to 100. Also, 1/100 is the only one set up to allow auto-creating of echos. I figured
it would be a bit redundant to have all nodes set that way.

Yes the whole levels thing and read/write thing is something I have yet to fully suss. Thanks for this info :)

Most of these, do exactly what they sound like they should. :) It's
really not too bad once you get one set up, you can copy/paste for
others.

:)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06 Dec 2019 at 09:04p, Black Panther pondered and said...

allowEmptyPktPwd on

why did you opt to use this, docs suggest 'off' is the best and is th default state, so the keyword could be omitted.

Of the nodes on hub 4, there is only one that is using a packet password. With this set, the packets won't be put in the unsecure inbound.

Docs have this to say

[snip]

Syntax:
allowEmptyPktPwd <off|secure|on>
Example:
allowEmptyPktPwd on

This flag is useful if you want to generate packet passwords for this link,
but do not want to check the packet passwords that your link sends to you.
This is sometimes necessary as a workaraound if your link sends you netmail packets without packet passwords, for example.

The default state is off. In this case the incoming packet password must
match the packet password that you defined. This is the most secure option.

If you set this switch to secure, packets that do not contain a packet
password and are received in the protected inbound will be processed. You can use this if your uplink sometimes sends you packets without packet passwords, as a workaround until the uplink has fixed his system. Still, if you receive packets with wrong packet passwords, they will be rejected.

The setting on works like the secure setting, with the difference that
packets without packet passwords are allowed even in the unprotected inbound directory. It is not recommended to use this setting.

This statement can only be repeated for different links.

[snip]

I'm not sure I'm interpreting this the same way you are..

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On Sat, 7 Dec 2019 19:10:07 +1300
"Avon -> Black Panther" <0@101.1.21> wrote:

Docs have this to say

[snip]

Syntax:
allowEmptyPktPwd <off|secure|on>
Example:
allowEmptyPktPwd on

[...]

The setting on works like the secure setting, with the difference that packets without packet passwords are allowed even in the unprotected inbound directory. It is not recommended to use this setting.

This statement can only be repeated for different links.

[snip]

I'm not sure I'm interpreting this the same way you are..

I think the description a pretty clear. "allowEmptyPktPwd on" would allow everyone to sneak in forged packets.

I also don't understand the reason for not using packet passwords.

---
* Origin: (21:1/151)

Hello Avon,

Level 200

need to suss this

I have used this in the past but currently just use groups.

I might use it again if need be but I currently don't need it.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)