Curious whether point systems are allowed in fsxNet. Is this allowed, or is it discouraged? Or is it simply preferably to seek out its own node number?
Asking because I have a second board I'd like to get connected, and
would like to to try my hand at having my main board serve as its uplink.
<codeƒenix>
...I only touch base with reality on an as-needed basis!
--- SBBSecho 3.20-Win32
* Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (21:4/141)
Curious whether point systems are allowed in fsxNet...
Curious whether point systems are allowed in fsxNet. Is this allowed, or is it discouraged? Or is it simply preferably to seek out its own node number?
I've pondered perhaps trying to create a list of point systems in fsxNet but have not done this at this time. I guess the overhead (much like with systems.txt) is trying to keep on top of what has been created by sysops and my hunch is trying to keep up a point list may be a bridge to far for effort expended... not 100% sure
Curious whether point systems are allowed in fsxNet. Is this allowed, or is it discouraged? Or is it simply preferably to seek out its own node number?
So clrghouz will discover points, when folks with a point send a
message. It wont know the sysop or the system name though... Actually,
as I think about it, it wont know when they leave the network either -
but that could be determine by how long ago a last message was seen...
Here's what's been discovered so far...
id | host_id | node_id | point_id
------+---------+---------+----------
5731 | 1 | 158 | 1
Asking because I have a second board I'd like to get connected, and
would like to to try my hand at having my main board serve as its uplink.
Curious whether point systems are allowed in fsxNet. Is this allowed,
or is it discouraged? Or is it simply preferably to seek out its own
node number?
Asking because I have a second board I'd like to get connected, and
would like to to try my hand at having my main board serve as its
uplink.
Avon wrote to Codefenix <=-
I've pondered perhaps trying to create a list of point systems in
fsxNet but have not done this at this time. I guess the overhead (much like with systems.txt) is trying to keep on top of what has been
created by sysops
yes this is fine :)
The point systems do not appear in the nodelist so any netmail sent to them will route to your main node number and then it's up to your system to handle the flow of netmail to/from the point as well as any echomail you opt to feed the point system.
Wait, what? Is it live? Would love to see another Codefenix creation!
What a lot of us do is run a main node, and then any aditional system is run as a point. It then saves a lot of issues.
ie:
1. Taking down the point
2. If the sysop only wants to test.
3. Taking Avon's time, but adding or removing nodes.
4. Testing a different software setup.
5. Firewall changes...
Like Vorlon said, it takes away
from having to get Avon to add another board to the nodelist and remove it if you take it down..
I've never understood pointlists. Fido zone 2 has a lengthy one, but
from my understanding, points are meant for BBSes that aren't
nodelisted or mail only systems, either one relies on the point calling
the boss node and all routing is to the boss. So, why would a list of
unreachable points be of any benefit?
Wait, what? Is it live? Would love to see another Codefenix creatio
Yeah, it's up. Started putzing around with Mystic a couple years ago,
just seeing how things worked, and not really sure whether it'd see the light of day.
│ telnet://conchaos.synchro.net:2300
│ ssh://conchaos.synchro.net:2200
Ogg wrote to poindexter FORTRAN <=-
Hello pF!
I've never understood pointlists. Fido zone 2 has a lengthy one, but
from my understanding, points are meant for BBSes that aren't
nodelisted or mail only systems, either one relies on the point calling
the boss node and all routing is to the boss. So, why would a list of
unreachable points be of any benefit?
If the editor/reader supports it, it provides the names and
addresses of point users. Very handy.
So running a point system, and thereby delegating another system as a
boss is a task that some may not be able to perform - especially if your BBS/mailer/tosser of choice cannot handle the task.
So if you are in that position, then you can always get another node or two of off clrghouz. I've built (well still building it), so that it can be as much self service as possible.
Once you are assigned a node number (which is currently manual, but I'll
Bucko wrote to deon <=-
Another great way of getting extra nodes. clrghouz is also a way to get
it done.. Especially if as Deon says your software can't handle
points..
I've never understood pointlists. Fido zone 2 has a lengthy one, but
from my understanding, points are meant for BBSes that aren't
nodelisted or mail only systems, either one relies on the point calling
the boss node and all routing is to the boss. So, why would a list of
unreachable points be of any benefit?
Solid, thanks. :)
Looks like I have things rolling. :D
┌ codefenix - dawnCHAOTIC
│ telnet://conchaos.synchro.net:2300
│ ssh://conchaos.synchro.net:2200
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,044 |
| Nodes: | 16 (1 / 15) |
| Uptime: | 46:03:42 |
| Calls: | 500,943 |
| Calls today: | 6 |
| Files: | 109,374 |
| D/L today: |
5,871 files (1,062M bytes) |
| Messages: | 304,051 |