Since most Service providers block Port 25, is there any real reason to open Port 25 anymore on your firewall or router for Synchronet.
port listed on the "ports to open chart" are obsolete or not used anymore. I'm also trying to get instant messages to work, but don't want to open ports no longer supported by synchronet. Thanks In Advance as always.
a) You're running a service that's listening on port 25
b) You want people to be able to connect to that service
c) Your ISP doesn't make it impossible for people to connect on that port
If any of the above are false, then there's no reason to open the port.
went opsolete. I was trying to free up a few ports for your ecweb4, ports 1123 and 1513, that was my only reason for asking, but I have consolidated
Ok, I guess I'll still leave it open then for instant messaging. As far as
DesotoFireflite wrote to All <=-
@MSGID: <585170C2.2218.fido-synchron@freeway.apana.org.au>
@TZ: 412c
Since most Service providers block Port 25, is there any real reason to open Port 25 anymore on your firewall or router for Synchronet.
Telnet 23 - For Telnet logins (highly recommended)
SSH 22 - For SecureShell logins (recommended)
RLogin 513 - Optional for quick-login from RLogin clients (e.g.
SyncTERM) SMTP 25 - Necessary for receiving Internet e-mail and
inter-BBS instant messages
POP3 110 - Allows BBS users to check their e-mail using standard
Internet mail clients (e.g. Outlook Express)
FTP21 - Allows access to the BBS file/download areas using a standard
FTP client or web browser
HTTP 80 - Required for access to the BBS's web server
NNTP119 - Allows BBS users to read and post messages using standard
news readers/clients
Gopher 70 - Archaic protocol allows reading of messages and other BBS
info IRC6667 - Allows Internet Relay Chat (IRC) clients to connect to
your BBS Finger 79 79 Allows remote querying of BBS user info, who's online, and other BBS info
SYSTAT 11 11 Allows remote querying of who's online (aka Active Users)
QOTD 17 17 Allows remote querying of the current auto-message (aka
Quote Of The Day)
MSP 18 18 Allows incoming inter-BBS instant messages without SMTP connectivity
echicken wrote to DesotoFireflite <=-
The only reasons to open that port would be:
a) You're running a service that's listening on port 25
b) You want people to be able to connect to that service
echicken wrote to DesotoFireflite <=-
Re: obsolescence, a few of those services probably qualify as obsolete
(by popular opinion anyway). They still work, though - just depends if you want to be bothered with hosting them. (After all, we're all
hosting some arguably obsolete services one way or the other, for our
own amusement.)
a) You're running a service that's listening on port 25
b) You want people to be able to connect to that service
c) Your ISP doesn't make it impossible for people to connect on that
port
If any of the above are false, then there's no reason to open the
port.
Ok, I guess I'll still leave it open then for instant messaging.
b) You want people to be able to connect to that service
Or machines - much SMTP activity is automated, the only exception being local users sending email using a client like Thunderbird, Outlook, etc.
Re: obsolescence, a few of those services probably qualify as
obsolete (by popular opinion anyway). They still work, though - just
depends if you want to be bothered with hosting them. (After all,
we're all hosting some arguably obsolete services one way or the
other, for our own amusement.)
I look at probability of use. Telnet is technically considered
obsolete these days,
echicken wrote to Tony Langdon <=-
Yes, that's "people" in a very general sense, extending to systems
those people have put in place.
mark lewis wrote to Tony Langdon <=-
people keep saying that but one only need look around to see that it is not true... especially considering that i've just watched my system
swat down the 500th telnet connect today attempting MIRAI or variant infestation... yes, that counts the feeler probes that don't do
anything but to report the address back to the bot herder for a future infestation takeover attempt...
Sounds like you may need a better router. I'm guessing you have a limited number of 'slots' you can use when configuring port forwarding?
Re: obsolescence, a few of those services probably qualify as obsolete (by popular opinion anyway). They still work, though - just depends if you want to be bothered with hosting them. (After all, we're all hosting some arguably obsolete services one way or the other, for our own amusement.)
Since most Service providers block Port 25, is there any real reason
to open Port 25 anymore on your firewall or router for Synchronet.
It depends on your provider. Both my ISP and the IPv4 tunnel provider I use allow traffic on port 25. In fact, my ISP lets me turn the filter for port 25 (and several other ports commonly abused on user machines) on or off.
Telnet 23 - For Telnet logins (highly recommended)
Needed, either 23 or whatever port you're actually using. :)
SSH 22 - For SecureShell logins (recommended)
Very highly recommended.
RLogin 513 - Optional for quick-login from RLogin clients (e.g.
Recommended, unless you're not offering rlogin.
SyncTERM) SMTP 25 - Necessary for receiving Internet e-mail and
inter-BBS instant messages
Necessary if hosting email, but pointless if ISP blocks port 25 (in which case, you will need to use a workaround to send/receive email).
POP3 110 - Allows BBS users to check their e-mail using standard
Internet mail clients (e.g. Outlook Express)
Recommended, some users may choose to access their email this way.
FTP21 - Allows access to the BBS file/download areas using a
standard FTP client or web browser
Highly recommended
HTTP 80 - Required for access to the BBS's web server
Highly recommended.
NNTP119 - Allows BBS users to read and post messages using standard
news readers/clients
Highly recommended.
Gopher 70 - Archaic protocol allows reading of messages and other
BBS
Could get away without this one, unless you know you have users using Gopher (not likely).
info IRC6667 - Allows Internet Relay Chat (IRC) clients to connect
to
Depends on your user base and server interconnects. I would forward this port, unless you have reason not to.
your BBS Finger 79 79 Allows remote querying of BBS user info, who's
online, and other BBS info
Not really necessary. Finger has fallen into disuse in the UNIX world due to security concerns. Also, less interesting there, given many systems have very few users these days (as opposed to years ago, when Linux was rare/nonexistent, and UNIX systems had lots of shell users).
SYSTAT 11 11 Allows remote querying of who's online (aka Active
Users)
Useful, but again, rarely used these days.
QOTD 17 17 Allows remote querying of the current auto-message (aka
Quote Of The Day)
Same again. :)
MSP 18 18 Allows incoming inter-BBS instant messages without SMTP
connectivity
I'd forward this one. :)
... Spam will keep in it's can until the end of time.
do you actually get instant messages from other BBSes? if not, then it is not needed... port 18 is also available for such IF you want to allow for this activity...
remember, the fewer ports you have open the smaller your attach surface is... all IPs on the net are probed for vulnerabilities all the time... keeping your attack surface as small as possible is better for security than having a whole bunch of ports open and presenting a large attack surface that may be breached by using multiple ports for the attacks...
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 40:47:01 |
Calls: | 15,172 |
Calls today: | 1 |
Files: | 19,859 |
D/L today: |
23 files (4,259K bytes) |
Messages: | 1,692,952 |