Hey NuSkooler!

I'm testing out ENiGMA on a second PC but having some troubles I need to
check with you... Is there a problem in current branch running the BBS as a POINT?
Got ENiGMA set up as a point to my main fsxNet bbs but getting funny errors like: "Error: No local configuration for packet addressed to 21:4/136.1"

config says:
ftn: {
network: {
fsxnet: {
localAddress: "21:4/136.1"
}
}
}

Can't say it's not my fault since I usally don't know what I'm doing ;)

//ToTAL

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: ToTAL LoST BBS (21:4/136)

On Monday, November 12th ToTAL muttered...

I'm testing out ENiGMA on a second PC but having some troubles I need to check with you... Is there a problem in current branch running the BBS as a POINT? Got ENiGMA set up as a point to my main fsxNet bbs but getting funny errors like: "Error: No local configuration for packet addressed to 21:4/136.1"

Are you on the 0.0.9-alpha branch?


On Monday, November 12th ToTAL was heard saying...

Can't say it's not my fault since I usally don't know what I'm doing ;)

Honestly, it's mostly untested territory, so YMMV :X
Is the packet in question for sure addressed to 21:4/136.1? If so, if you don't
mind please create a issue on the GitHub tracker and attach a sample packet file if you can + notes & expectations. At least for *receiving*, I can't think
why it would not work off the top of my head.






--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.13.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

Are you on the 0.0.9-alpha branch?

Yes, did a fresh pull from GiT and verified it in the logs (btw, --version doesn't work well at my end)

Honestly, it's mostly untested territory, so YMMV :X
Is the packet in question for sure addressed to 21:4/136.1? If so, if
you don't mind please create a issue on the GitHub tracker and attach a sample packet file if you can + notes & expectations. At least for *receiving*, I can't think why it would not work off the top of my head.

Sure, will do! I'll try to get as much useful information as possible.

//ToTAL

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: ToTAL LoST BBS (21:4/136)

11/12/18, ToTAL said the following...

Sure, will do! I'll try to get as much useful information as possible.

Let me know how far you get with this as I'm pretty much doing the same thing to test ENiG..

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Eggy BBS (21:4/143)

On Monday, November 12th ToTAL was heard saying...

Yes, did a fresh pull from GiT and verified it in the logs (btw, --version doesn't work well at my end)

Do you mean ./main.js --version ?



--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.13.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

Do you mean ./main.js --version ?

Both main.js and oputils.js.
main.js doesn't show version but starts the server as normal.

oputil.js gives and error for package.json:

./oputil.js --version
module.js:478
throw err;
Error: Cannot find module '../package.json'
//ToTAL

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: ToTAL LoST BBS (21:4/136)

On Thursday, November 15th ToTAL muttered...

oputil.js gives and error for package.json:

Doh, you're right.

'./main.js --version' should work fine, however.

I'll fix the oputil.js version tonight. Broken when I moved stuff around.


--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.13.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)