My BBS's MRC client is not able to connect to tbbs.homeip.net port 5000. Is anyone else unable to connect?

Just curious if my IP might have been blacklisted.

--
Karl
The Search BBS

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Search BBS (21:1/161)

On 09/12/16, karl said the following...

My BBS's MRC client is not able to connect to tbbs.homeip.net port 5000. Is anyone else unable to connect?

Just curious if my IP might have been blacklisted.

Nah its not, just woke up to find had a power outage and the system was restarted.

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

Nah its not, just woke up to find had a power outage and the system was

Uh, oh. Hope nothing was damaged.

--
Karl
The Search BBS

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Search BBS (21:1/161)

Nah its not, just woke up to find had a power outage and the system was restarted.

Han Solo: [sounding official] Uh, everything's under control. Situation
normal.
Voice: What happened?
Han Solo: [getting nervous] Uh, we had a slight weapons malfunction, but
uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
Voice: We're sending a squad up.
Han Solo: Uh, uh... negative, negative. We had a reactor leak here now. Give
us a few minutes to lock it down. Large leak, very dangerous.
Voice: Who is this? What's your operating number?
Han Solo: Uh...
[Han shoots the intercom]

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ SIMMAH DOWN NAH! heah SIMMAH DOWN NAH!

--- Mystic BBS v1.12 A31 (Windows)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

On 09/12/16, karl said the following...

Nah its not, just woke up to find had a power outage and the system w

Uh, oh. Hope nothing was damaged.

Everything recovered when I started the machines back up, should be able to reconnect to MRC again. Really apologize for this downtime.

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

Monday September 12 2016 23:09, you wrote to Pequito:

Han Solo: [sounding official] Uh, everything's under control.
Situation normal.
Voice: What happened?
Han Solo: [getting nervous] Uh, we had a slight weapons malfunction,
but uh... everything's perfectly all right now. We're fine. We're all
fine here now, thank you. How are you?
Voice: We're sending a squad up.
Han Solo: Uh, uh... negative, negative. We had a reactor leak here
now. Give us a few minutes to lock it down. Large leak, very
dangerous.
Voice: Who is this? What's your operating number?
Han Solo: Uh...
[Han shoots the intercom]

Truely classic!

--- GoldED+/LNX 1.1.5-b20160322
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110)

On 09/12/16, Caphood said the following...

Nah its not, just woke up to find had a power outage and the system w restarted.

Han Solo: [sounding official] Uh, everything's under control. Situation normal.
Voice: What happened?
Han Solo: [getting nervous] Uh, we had a slight weapons malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
Voice: We're sending a squad up.
Han Solo: Uh, uh... negative, negative. We had a reactor leak here now. Give us a few minutes to lock it down. Large leak, very dangerous.
Voice: Who is this? What's your operating number?
Han Solo: Uh...
[Han shoots the intercom]

hah love that.

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

No need to apologize :-) I am glad nothing on your end was damaged from the outage. Power outages out my way are usually caused by electrical storms
which means that something ends up getting fried. Something always get
plugged into the wrong outlet on the UPS.

--
Karl
The Search BBS

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Search BBS (21:1/161)

Situation normal.
Voice: What happened?

`
Truly relatable.

--
Karl
The Search BBS

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Search BBS (21:1/161)

On 09/12/16, karl said the following...

My BBS's MRC client is not able to connect to tbbs.homeip.net port 5000. Is anyone else unable to connect?
Just curious if my IP might have been blacklisted.

im on

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A31 (Windows)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 09/12/16, Caphood pondered and said...

Han Solo: [sounding official] Uh, everything's under control. Situation normal.
Voice: What happened?
Han Solo: [getting nervous] Uh, we had a slight weapons malfunction, but uh... everything's perfectly all right now. We're fine. We're all fine here now, thank you. How are you?
Voice: We're sending a squad up.
Han Solo: Uh, uh... negative, negative. We had a reactor leak here now. Give us a few minutes to lock it down. Large leak, very dangerous.
Voice: Who is this? What's your operating number?
Han Solo: Uh...
[Han shoots the intercom]

Love it :)

My kids are still hassling me about how cut up I was after the last Star Wars film. :)

Best, Paul

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

On 09/12/16, Pequito said the following...

On 09/12/16, karl said the following...

Nah its not, just woke up to find had a power outage and the sys

Uh, oh. Hope nothing was damaged.

Everything recovered when I started the machines back up, should be able to reconnect to MRC again. Really apologize for this downtime.

This is why we need a true 'network'. I'm still puzzling out how such a
thing can be done.

TBH, I've been spending more time doing a website makeover than on other projects like mrc. But one of my ideas was to eliminate the MPL portion of
the platform and just have individual running python clients. I still
haven't given up on the idea of creating a MPY script that can connect to a true IRC server. If we can do that, then some people can run an IRC server
and network them, then have multiple access points for each chatter.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

haven't given up on the idea of creating a MPY script that can connect
to a true IRC server. If we can do that, then some people can run an

NICE. I've experimente a LOT, with BASH and scripting, just to arrive having some sort of automatized IRC channel output on Mystic, by external command.

Is one of the 1.000 things I would like to have in the BBS contents, lol...

¯¯ÅndçŒd Cíld®®

"What do you look like?"
"It depends on who is looking."

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Miskatonic BBS (21:1/165)

projects like mrc. But one of my ideas was to eliminate the MPL portion of the platform and just have individual running python clients. I still haven't given up on the idea of creating a MPY script that can connect
to a true IRC server. If we can do that, then some people can run an
IRC server and network them, then have multiple access points for each chatter.

That's a good idea. Would the python clients be configured with multiple server options so that if it could not connect to one, it would try the next? This might add another potential problem... if the server you connected to
was isolated from the other IRC severs. Maybe if everyone's client had the same IRC servers servers and in the same order so that all of the clients
would only be connected to the same IRC server.

If there were 3 IRC servers configured to talk to each other but 1 of them
was isolated from the other 2 then whoever was connected to the isolated IRC server could communicate to the other people on that same IRC server but no
one else... All would appear fine from the client's perspective. Maybe the
IRC server would need to have a connection check to at least 1 other IRC
server otherwise it stops responding to clients.

I like the idea of the IRC server - I think it would allow more flexibility
for the person running the server and allow more client connectivity from
BBSes other than Mystic.

--
Karl
The Search BBS

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Search BBS (21:1/161)

On 09/13/16, karl said the following...

projects like mrc. But one of my ideas was to eliminate the MPL port of the platform and just have individual running python clients. I s haven't given up on the idea of creating a MPY script that can connec to a true IRC server. If we can do that, then some people can run an IRC server and network them, then have multiple access points for eac chatter.

That's a good idea. Would the python clients be configured with multiple server options so that if it could not connect to one, it would try the next? This might add another potential problem... if the server you connected to was isolated from the other IRC severs. Maybe if
everyone's client had the same IRC servers servers and in the same order so that all of the clients would only be connected to the same IRC
server.

See, that's exactly the problem I see regarding the 'relay' portion of MRC. The best I can think of is to have some sort of mesh arrangement with the servers. That way, if one drops out, the others can still do the job.

If there were 3 IRC servers configured to talk to each other but 1 of
them was isolated from the other 2 then whoever was connected to the isolated IRC server could communicate to the other people on that same
IRC server but no one else... All would appear fine from the client's perspective. Maybe the IRC server would need to have a connection check to at least 1 other IRC server otherwise it stops responding to clients.

There's still an element that has to be dealt with. How to handle dupe checking. Say client A talks to server A, and server A talks to server B and Server C. What's to keep messages from going to server A, then server B and then back to server A and back to client A? It will take some dupe checking that is tough to wrap my brain around.

I like the idea of the IRC server - I think it would allow more flexibility for the person running the server and allow more client connectivity from BBSes other than Mystic.

I think so too. This will take the load off of the relay part. It also
means that a mystic sysop can setup IRC connections with any IRC network they want, not just MRC. But it seems that there is a following for and isolated MRC service and I'm a bit afraid that that will stifle it.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

Gryphon wrote to Pequito <=-

TBH, I've been spending more time doing a website makeover than on
other projects like mrc. But one of my ideas was to eliminate the MPL portion of the platform and just have individual running python
clients. I still haven't given up on the idea of creating a MPY script that can connect to a true IRC server. If we can do that, then some people can run an IRC server and network them, then have multiple
access points for each chatter.

Using an IRC server would let Synchronet and Mystic systems talk together (Synchronet already has an IRC client and server), as well as allowing for a network of servers.


... Hypochondria is the only disease I haven't got.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

karl wrote to Gryphon <=-

That's a good idea. Would the python clients be configured with
multiple server options so that if it could not connect to one, it
would try the next? This might add another potential problem... if the

Or use round robin DNS - I would certainly be happy to add "irc.vkradio.com" A, AAAA or CNAME records to bring all linked servers under a common hostname.

server you connected to was isolated from the other IRC severs. Maybe
if everyone's client had the same IRC servers servers and in the same order so that all of the clients would only be connected to the same
IRC server.

Yeah, netsplits are always an issue.

If there were 3 IRC servers configured to talk to each other but 1 of
them was isolated from the other 2 then whoever was connected to the isolated IRC server could communicate to the other people on that same
IRC server but no one else... All would appear fine from the client's perspective. Maybe the IRC server would need to have a connection
check to at least 1 other IRC server otherwise it stops responding to clients.

That's always been an issue in IRC, though I believe it will be a lot less of an issue on a BBS oriented IRC network, because we'll have a more respectful userbase.

I like the idea of the IRC server - I think it would allow more flexibility for the person running the server and allow more client connectivity from BBSes other than Mystic.

Yes. I know Synchronet will be able to join immediately, for starters. It comes with IRC out of the box. Just have to tweak the server settings to point to ours instead of irc.synchro.net, or add a separate menu item for our chat.
)


... Growing older is typical. Growing up is the option.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Gryphon wrote to karl <=-

I think so too. This will take the load off of the relay part. It
also means that a mystic sysop can setup IRC connections with any IRC network they want, not just MRC. But it seems that there is a
following for and isolated MRC service and I'm a bit afraid that that
will stifle it.

No reason we can't have our own branded IRC network, fsxchat? :D


... WWhhaatt ddooeess dduupplleexx mmeeaann??
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

No reason we can't have our own branded IRC network, fsxchat? :D

Did anyone have tried to output IRC chan #xxx on own BBS?

¯¯ÅndçŒd Cíld®®

"What do you look like?"
"It depends on who is looking."

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Miskatonic BBS | telnet://rasppi.servebbs.org (21:1/165)