I just started my 2nd BBS apart from Another F-ing BBS, it's called Bog Box
of Raspberry Pi.

I want to add fsx_net to the new BBS, but I wonder about getting/sending messages on BinkP... Maybe I'm not thinking this through, but do I have to use a different BinkP address on my new BBS so it won't collide with my 1st BBS?

In other words, BBS 1 uses BinkP Port as 24554. Do I have to have a
different BinkP address for BBS 2 because they are both on my home
network/IP?

If anyone who runs 2 BBS's on the same network/IP.... Can you tell me if I
have to run BBS 2 using a different BinkP address as BBS 1????

Many Tanx
Gary Crunk

----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

I want to add fsx_net to the new BBS, but I wonder about getting/sending messages on BinkP... Maybe I'm not thinking this through, but do I have
to use a different BinkP address on my new BBS so it won't collide with
my 1st BBS?

If you wanted to open Binkp to be open to the internet, then it would need to be a different port.

Another option would be to setup your second system as a point off of
Another F-ing BBS. In which case the second system should be fine on 24554, and could just contact your main system internally.

Scott Miller
---Quickshot
----Troybbs.com

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Troy's Den * troybbs.com (21:2/134)

need to be a different port.

I kind of thought so...

Another option would be to setup your second system as a point off of Another F-ing BBS. In which case the second system should be fine on 24554, and could just contact your main system internally.

Hmmm Interesting. I don't know how to do that... My 1st BBS is running
Mystic on Windows XP. The 2nd one is running Mystic on a Raspberry PI
running Raspian.... I've no idea on how to make the PI BBS interface with
the Windows XP version...

I know... I am probably making all of this too complicated...

Gary

----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

Hmmm Interesting. I don't know how to do that... My 1st BBS is running Mystic on Windows XP. The 2nd one is running Mystic on a Raspberry PI running Raspian.... I've no idea on how to make the PI BBS interface with the Windows XP version...

I know... I am probably making all of this too complicated...

It is actually not that complicated to setup. You are running Mystic, and
that has everything you need.

On your Pi system setup for echomail, just like you would for your main
system. With the only difference of adding a point. such as 21:2/105.1 for the PI system. Under session options set it up to contact your main system. Setup your password tic session etc to what you want. Here is what it looks like on my test system.

Description Troy Test system Zone 21
Active Yes Net 2
Archive Type ZIP Node 134
Export Type Crash Point 1
AllFix PW **** Domain fsxnet
PKT Password
Session Type BinkP
Route Info 21:*
Max PKT Size 512
Max ARC Size 2048
Use FileBox No
FileBox
TIC Password **** Session Options

Session Options BINKP

Host troybbs.com
Password ****
TimeOut 30
BlockSize 16384
CRAM-MD5 Yes
Hide AKAs Yes

Now on your main system, you would setup an echomail node for your Point.
Here is what my test system looks like. *** Notice that there is nothing in the Route....

Description Troy Test system Zone 21
Active Yes Net 2
Archive Type ZIP Node 134
Export Type Crash Point 1
AllFix PW **** Domain fsxnet
PKT Password
Session Type BinkP
Route Info
Max PKT Size 512
Max ARC Size 2048
Use FileBox No
FileBox
TIC Password **** Session Options

Session Options BINKP

Host test.troybbs.com
Password ****
TimeOut 30
BlockSize 16384
CRAM-MD5 Yes
Hide AKAs Yes


Now once that is all set up, you can simply setup netmail on your PI system, and AREAFIX from there to you main system. Mystic Magic will handle the rest.

Scott Miller
---Quickshot
----Troybbs.com

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Troy's Den * troybbs.com (21:2/134)

that has everything you need.

Many Thanks ... I will get with my Hub to see how he wants to work my situation....

Again, Many thanks for the info... VERY Helpful...

----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

Ohh, and thank you to Dan, at Castle Rock, for teaching this to me :)

Scott Miller
---Quickshot
----Troybbs.com

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: Troy's Den * troybbs.com (21:2/134)

On 08/30/17, quickshot said the following...

Ohh, and thank you to Dan, at Castle Rock, for teaching this to me :)

Ah, shucks. T'weren't nothing... ;)

You're welcome. That's what we are all here for, to help each other. :)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 08/30/17, garycrunk said the following...

If you wanted to open Binkp to be open to the internet, then it would need to be a different port.

I kind of thought so...

I've actually got three systems running over here, and they each have access
to the outside internet for various reasons. I'm using 24554, 24555 and 24556.

Another option would be to setup your second system as a point off of Another F-ing BBS. In which case the second system should be fine on 24554, and could just contact your main system internally.

Hmmm Interesting. I don't know how to do that... My 1st BBS is running Mystic on Windows XP. The 2nd one is running Mystic on a Raspberry PI running Raspian.... I've no idea on how to make the PI BBS interface with the Windows XP version...

What I do here, for binkd connections between the systems, is just use the internal ip address of the computer. For example, the main board is on 192.168.0.15, and it would connect to 192.168.0.3 or 192.168.0.11, depending
on which system it wants to connect with.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 08/30/17, garycrunk said the following...

I just started my 2nd BBS apart from Another F-ing BBS, it's called Bog Box of Raspberry Pi.
I want to add fsx_net to the new BBS, but I wonder about getting/sending messages on BinkP... Maybe I'm not thinking this through, but do I have
to use a different BinkP address on my new BBS so it won't collide with
my 1st BBS?

The best is to make it a point off the original. The binkp port doesn't
matter as they are independent systems, they can both use the same port (like ssh on port 22 talks to ssh on another system's port 22). Keep the main
address and add a point for the new one (like .1), so the new one would be: 21:2/105.1 it's hub would be 21:2/105. You'd add with AreaFix & FileFix they work by default. The 21:2/105 hub will now also send to 21:2/105.1 as well as 21:2/100 (or whatever it is), so it sends in two directions. It knows how to
do that. That way you don't need any more full addresses and don't need to
add to the nodelist in an official way. That way the points can come and go.
I run my old mystic 1.11 version as .1 (at port 2324) and this AlphaTest (at 2323) as .2 still with only one main address. It just saves official node
space and makes it more flexible for you, other than that it runs exactly the same as adding another system off yours. I'm the NH USA Hub for RetroNet and would Hub new systems in NH the same way I send/receive from the point
systems. I'd just have to help add them to the nodelist officially unless
they just wanted to be points. It helps to experiment and figure out how everything works.
On your Hub you keep EchoMail Addresses the same, under EchoMail Nodes you
add the point systems for both each net your part of (if you want the point
to be part of all the networks). Also under Message Base Editor you add the points under Export To (2 nodes with one point, 3 nodes with two points).
The same sort of thing with files, except you need to add fileboxes for each point system and only need to send to them from the Hub.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 08/30/17, Black Panther pondered and said...

Ah, shucks. T'weren't nothing... ;)

You're welcome. That's what we are all here for, to help each other. :)

Pat on the back from me too :)

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 08/30/17, Black Panther pondered and said...

What I do here, for binkd connections between the systems, is just use
the internal ip address of the computer. For example, the main board is
on 192.168.0.15, and it would connect to 192.168.0.3 or 192.168.0.11, depending on which system it wants to connect with.

Same here, use internal IP and/or different BinkP port if that is what has
been set up.

Another option is to use Directory file transfer if you want to send files to different shared directories on the same network.

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 08/31/17, Avon said the following...

Same here, use internal IP and/or different BinkP port if that is what
has been set up.

Another option is to use Directory file transfer if you want to send
files to different shared directories on the same network.

I tried doing that, but was having issues with maintaining mapped drives between Windows and Linux systems. For some reason, Windows will only keep
the drive mapped for a short time, then it isn't able to access it... I
figured I'd just use binkp for transfering between them. :)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

garycrunk wrote to All <=-

I just started my 2nd BBS apart from Another F-ing BBS, it's called Bog Box of Raspberry Pi.

I want to add fsx_net to the new BBS, but I wonder about
getting/sending messages on BinkP... Maybe I'm not thinking this
through, but do I have to use a different BinkP address on my new BBS
so it won't collide with my 1st BBS?

In other words, BBS 1 uses BinkP Port as 24554. Do I have to have a different BinkP address for BBS 2 because they are both on my home network/IP?

Yes, they will need to appear on different ports. You can hvae both binkd instances on different ports on your network or on the same ports (on different hosts), but the public side of the router must have different ports forwarded to each BBS.

If anyone who runs 2 BBS's on the same network/IP.... Can you tell me
if I have to run BBS 2 using a different BinkP address as BBS 1????

Will be the same hostname, different port.

I cheated, I actually tunnel in a /29 via a VPN, so each of my boards has its own public IP. :)


... 10.0 times 0.10 is hardly ever 1.00.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

quickshot wrote to garycrunk <=-

Another option would be to setup your second system as a point off of Another F-ing BBS. In which case the second system should be fine on 24554, and could just contact your main system internally.

That would work too, just means all communication with the second system has to come through the boss node.


... Time between slipping on a peel and falling = one bananosecond
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

garycrunk wrote to quickshot <=-

need to be a different port.

I kind of thought so...

Another option would be to setup your second system as a point off of Another F-ing BBS. In which case the second system should be fine on 24554, and could just contact your main system internally.

Hmmm Interesting. I don't know how to do that... My 1st BBS is running Mystic on Windows XP. The 2nd one is running Mystic on a Raspberry PI running Raspian.... I've no idea on how to make the PI BBS interface with the Windows XP version...

I know... I am probably making all of this too complicated...

My guess is you're overthinking it. :) It's simple. On BBS 1, set BBS 2 up as a point (same FTN address with a non zero point number), with the binkp address <internal IP>:port, similarly for BBS 2, set the FTN address for that link to your node address, and make its binkp host the IP of BBS 1:port.


... If you don't go to other people's funerals, they won't come to yours.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Black Panther wrote to quickshot <=-

@TZ: 4168
On 08/30/17, quickshot said the following...

Ohh, and thank you to Dan, at Castle Rock, for teaching this to me :)

Ah, shucks. T'weren't nothing... ;)

You're welcome. That's what we are all here for, to help each other. :)

Yep, feel free to ask questions.


... Tagline stolen while sipping coffee.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Black Panther wrote to garycrunk <=-

What I do here, for binkd connections between the systems, is just use
the internal ip address of the computer. For example, the main board is
on 192.168.0.15, and it would connect to 192.168.0.3 or 192.168.0.11, depending on which system it wants to connect with.

That works. As I said, I cheated. I have a VPN that tunnels a /29, gave each BBS its own public IP. :)


... Coffee - the drink of the wired generation.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)