Lets say a sysOp wanted to help with testing and USING TALISMAN BBS...

I never want to drive traffic away from my main, so if I wanted to run TALISMAN as a door/telnet out from my Mystic BBS, what might be the easiest way to doso?

On first TALISMAN install, I am connecting to it via localhost:6969; all I changed was the telnet port in talisman.ini. Since users are already on my Mystic BBS, could I just use a Telnet IR menu command to localhost:6969? Or, should I set TALISMAN to its own IP address/port and connect that way?

I was hoping to run TALISMAN on the same system as my Mystic BBS. (It's a Pi 4, dunno if it will have enough juice - but think so.)

Any ideas, from ya'll Mystic/TALISMAN sysOps? I want to help beta this software... it looks nice as heck for being put together as fast as apam does, and I wanna support member of our BBS Scene 2020. :P Thanks...



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On first TALISMAN install, I am connecting to it via localhost:6969;
all I changed was the telnet port in talisman.ini. Since users are
already on my Mystic BBS, could I just use a Telnet IR menu command to localhost:6969? Or, should I set TALISMAN to its own IP address/port
and connect that way?

I thought I replied to this, but not seeing it in my message base... so
I'll reply again :)

That should work fine, if you only want people to connect via your mystic board. The only problem you may have is file transfers may not work. I
don't know the current state of the mystic telnet bridge, but it used to
not work due to "double telnet escaping".

I was hoping to run TALISMAN on the same system as my Mystic BBS.
(It's a Pi 4, dunno if it will have enough juice - but think so.)

It should be fine, especially if it's one of the higher end Pi 4s. Mystic doesn't use much memory, Talisman shouldn't use too much. Processing
power wouldn't be a problem I don't think.

Andrew


--- Talisman v0.6-dev (Linux/x86_64)
* Origin: Talisman BBS - telnet://talismanbbs.com:11892/ (21:1/126)

On first TALISMAN install, I am connecting to it via localhost:6969; all I changed was the telnet port in talisman.ini. Since users are already on my Mystic BBS, could I just use a Telnet IR menu command to localhost:6969? Or, should I set TALISMAN to its own IP address/port and connect that way?

I thought I replied to this, but not seeing it in my message base... so I'll reply again :)
That should work fine, if you only want people to connect via your mystic board. The only problem you may have is file transfers may not work. I don't know the current state of the mystic telnet bridge, but it used to not work due to "double telnet escaping".

Thanks for replying. I guess the smarter way would be to assign a port, even if I don't [or do] make it public, and telnet from 20forbeers.com TO 20forbeers.com.... it'll work all the same, I think. And, for those who WANT to and are saavy enough to see it, users can telnet into TALISMAN only if they so chooose.

LOL - most likely, no one will ever see it. HA! Although my board is actually gaining users and eyeballs, I sometimes think a lot of what I do for the board is more for ME than any users. :P

You know, I logged into the PIMP [MeaTLoTioNs Phone in my Pocket BBS] today and helped get a One Plus cell phone to 10 full nodes. It was one of the best moments of my weekend. LOL. BBSes are a lot more to me than just FidoNet posts and LORD.

I was hoping to run TALISMAN on the same system as my Mystic BBS.
(It's a Pi 4, dunno if it will have enough juice - but think so.)

It should be fine, especially if it's one of the higher end Pi 4s. Mystic doesn't use much memory, Talisman shouldn't use too much. Processing
power wouldn't be a problem I don't think.

LOL - I currently run a Pi 4 1gb model; but I was just talking on another FTN about what it'll take to switch to the 8gb. I think I'll do that this week - some sysOps don't think I'll have to change ANYTHING... I have a couple 8gb laying around, I just thought I'd have to do a bunch of IP stuff.

Anyway, THANK YOU apam... for the reply and all the suggestions.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

LOL - I currently run a Pi 4 1gb model; but I was just talking on
another FTN about what it'll take to switch to the 8gb. I think I'll
do that this week - some sysOps don't think I'll have to change
ANYTHING... I have a couple 8gb laying around, I just thought I'd have
to do a bunch of IP stuff.

Depends on how your Pi gets it's IP. If it's static, you should just be
able to swap the SD card over and that's it. If it's assigned via DHCP (I
do this, static IPs assigned via DHCP) it might go off your Pi's MAC
address which will be different.

But yeah, if you can get the IP assigned the same IP, it should just be
an sd card swap :)

Andrew


--- Talisman v0.6-dev (Linux/armv7l)
* Origin: HappyLand v2.0 - telnet://happyland.zapto.org:11892/ (21:1/126.1)

Depends on how your Pi gets it's IP. If it's static, you should just be able to swap the SD card over and that's it. If it's assigned via DHCP (I do this, static IPs assigned via DHCP) it might go off your Pi's MAC address which will be different.

But yeah, if you can get the IP assigned the same IP, it should just be
an sd card swap :)

Understood... my Pi has a static IP; but I think I can work some magic to make sure my router names the new Pi that same .14 address....

Thanks, I'll get it ironed... :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)