one? 2) I have SBBS up and running, have everything setup, I've been trying to setup BinkD with SBBS. here is what I'm trying to do (and what I have set up so far) I have Mystic and SBBS running on the same box (Ubuntu/X64). I have SBBS set up as a point off of Mystic. I want to send/recieve maill between the 2. I changed the default port for binkD to (54554), I use the 'default' port for Mystic. I have the echos set up on both systems, to transfer between the 2. First problem. I followed the directions for setting up BinkD to boot in my init.d it won't boot. (i'll figure that out), but when I try to manually poll when I DO load up binkD, with Mystic, BinkD either isn't loaded, or won't read the port I set it up to use. I changed everything on my router, so the port is open, but, mystic fails like it can't connect.
Thanks for ANY help!
Charles Stephenson wrote to All <=-
in my init.d it won't boot. (i'll figure that out), but when I try to manually poll when I DO load up binkD, with Mystic, BinkD either isn't loaded, or won't read the port I set it up to use. I changed everything
on my router, so the port is open, but, mystic fails like it can't connect.
Mystics mailer should be able to contact binkd at localhost:54554
You don't need to open the port unless you want your binkd contactable from the net. Mystics mailer should be able to contact binkd at localhost:54554 or your private lan ip 192.168.?.?:54554 from any connected machines you have there on your local network.
I suspect that binkd is not running or not listening on port 54554. When you start binkd the log will tell you what port it is listening on.
I hope that helps.. :)
I think you may have a problem with "hairpinning" - accessing a device behind the same router using the router's public IP address. Not all routers support that. Use the private IP address for comminication between BBSs on your LAN.
Make sure in binkd, you have the Mystic BBS's private IP in the node
line, and on Mystic, make sure the address of the binkd node is the private IP. Of course, if both are on the same machine, you can use "127.0.0.1:<port>".
My setup is actually a little more complicated, because although I have both on the one machine, they have separate public IP addresses and both use standard ports, which means there's a lot more configuration of
SBBS, Mystic and binkd involved. But the communication side is simplified, because there's no NAT router involved, it's all done on public IPs.
Mystics mailer should be able to contact binkd at localhost:54554
you misspelled 24554 which is the default binkp port...
I'm trying to run everything (Syncrho/BinkD) and (Mystic) from the same machine... Will that be a problem with BinkD and Mystic Mail connections? I did change the port for BinkD. I DO have to figure out why it won't load at boot, instead of having to manually load it.
I suspect that binkd is not running or not listening on port 54554.
When you start binkd the log will tell you what port it is listening
on.
That's the problem excatly. I have time today to figure out why it's not loading at boot.
Charles Stephenson wrote to Tony Langdon <=-
I did edit the port forwarding and added openings for BinkD,
Mystic/BinkD too. they are on different UDP ports. I think I have to
read up on how to actually USE binkD. I've been reading the manual, and doing it as I go. Think I need to do a more intensive reading to understand it. 'hairpinning'?? After Telling you my step-up, is that
what my problem is?
That's sorta how I have it Not the 127.x.x.x:<port> but I have a
different localhost address. It's how I load up 2 other BBS's from my Mystic Matrix log in (magickaBBS/linux & Searchlight/DOS). I'm actually running WWIV, and Enigma (both linuux) at boot, along with Mystic, Magicka, and Syncrhonet all on one linux machine. Planning on making Magicka, WWIV, and Syncrho 'public' for my users to log in to from my matrix as well.
My setup is actually a little more complicated, because although I have both on the one machine, they have separate public IP addresses and both use standard ports, which means there's a lot more configuration of
SBBS, Mystic and binkd involved. But the communication side is simplified, because there's no NAT router involved, it's all done on public IPs.
Sounds similar to what I'm doing too.. I just envoke port forwarding
and open ports as needed.
Mystics mailer should be able to contact binkd at localhost:54554
you misspelled 24554 which is the default binkp port...
Charles has his Mystic mailer running on port 24554 so he needs his
binkd to run on another port.
Mystics mailer should be able to contact binkd at localhost:54554
you misspelled 24554 which is the default binkp port...
Mystics mailer should be able to contact binkd at localhost:54554
you misspelled 24554 which is the default binkp port...
And does it start with a capital 2 or a lower-case 2?
And does it start with a capital 2 or a lower-case 2?
And does it start with a capital 2 or a lower-case 2?
Aha -- the letter 2!
"I never learned how to read..."
Celebrity Jeopardy, that was one of my favorite SNL skits. :)
No problem. I run BinkIT here on port 24554 along with other software on other ports for testing things out. Sounds like much what you are
doing.. just with different software.
I suspect that binkd is not running or not listening on port 54554.
When you start binkd the log will tell you what port it is listening
on.
With binkd you need to use the iport keyword in binkd.conf to change the listening port..
iport 54554
If you have a setup like this:
BBS1 --------------+
192.168.1.2 | 192.168.1.1 1.2.3.4 (mybbs.com)
+--------------Router-------------Internet
|
BBS2 --------------+
192.168.1.3
Now assume BBS1 has binkp on port 24554, BBS2 has binkp on 24555, with port forwarding for those ports setup on the router.
Now, if you attempt to access BBS2's bink from BBS1 using
mybbs.com:24555, this resolves to 1.2.3.4:24555 (the router's external IP), it may not work, because this is what we call "hairpinning"
Charles Stephenson wrote to Tony Langdon <=-
On 06/03/18, Tony Langdon said the following...
If you have a setup like this:
BBS1 --------------+
192.168.1.2 | 192.168.1.1 1.2.3.4 (mybbs.com)
+--------------Router-------------Internet
|
BBS2 --------------+
192.168.1.3
Now assume BBS1 has binkp on port 24554, BBS2 has binkp on 24555, with port forwarding for those ports setup on the router.
Now, if you attempt to access BBS2's bink from BBS1 using
mybbs.com:24555, this resolves to 1.2.3.4:24555 (the router's external IP), it may not work, because this is what we call "hairpinning"
That's exactly how I have it set up. One BBS (Mystic: is 192.168.11:23) and Syncrhonet is 192.168.9:2333. I suppose I AM 'hairpinning"
I think it will work, I think my issue is setting up binkd.conf right.
I know I had some things in there wrong, I got a 'blueprint' config
from someone a few days ago, I was hoping I'd have time to play with it this weekend, gonna hafta wait/hope I can this comming weekend.
I know this is off-topic to your thread, but I LOVE your handle! :)
Depends what address you have in the configs on each end. For best results, use the 192.168 internal addresses. As I said, some routers don't support hairpinning. I never know if mine do, because I always configure the most direct network path where possible. :)
Yeah, you just gotta get it right, and all will be sweet. :)
This is the sysops echo, and we're sysops, so it's on topic. And, thanks!
Charles Stephenson wrote to Tony Langdon <=-
I'm HOPING my router does support it, but it's a rather old router.
I'll know this weekend. :)
Charles Stephenson wrote to Tony Langdon <=-
I'm HOPING my router does support it, but it's a rather old router.
I'll know this weekend. :)
If your old router is one of those blue Linksys WRT54G routers, check out DD-WRT - it's open source firmware for those old routers that is stable and add a ton of features. It's supported by a lot of routers, but
WRT54Gs were the first.
Charles Stephenson wrote to poindexter FORTRAN <=-
On 06/10/18, poindexter FORTRAN said the following...
If your old router is one of those blue Linksys WRT54G routers, check out DD-WRT - it's open source firmware for those old routers that is stable and add a ton of features. It's supported by a lot of routers, but
WRT54Gs were the first.
That's exactly what it is... I'll have to download that and play around with it.
I still use my first router, a WRT54G that I got as a FON access point in 2004 or so, as a backup router - it's been running DD-WRT for at least 10 years.
I still use my first router, a WRT54G that I got as a FON access point in 2004 or so, as a backup router - it's been running DD-WRT for at least 10 years.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495940:21:33 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,975 |