thedarkener wrote:1) Timestamped STDERR entries (so I can do " ./repeater 2>> /var/log/repeater.log " and know when things happened)
2) Connection authentication (text file parsed for list of authorized ID: numbers to connect, if it's not listed it's disconnected? How hard would it be to write a DSM for a regular password authentication against a repeater, for cases of SC servers?)
3) Distributor (Mode 1) support
I sure wish I was a programmer, or I'd do it myself!! Alas, I'm but a network engineer..
[1]: Yes, logs would look much nicer that way. I will do that fro next version.
[2]: Yeah, I've actually started to do this already (I plan to use windows .ini- file like syntax and read it with libiniparser). Current plan (straight form idranges.ini):
;This INI file is used for restricting access to allowed servers/viewers
;There are 4 sections:
;[AcceptServers]: Defines ranges of Servers allowed access
;[AcceptViewers]: Defines ranges of Viewers allowed access
;[RejectServers]: Defines ranges of Servers denied access
;[RejectViewers]: Defines ranges of Viewers denied access
;There can be upto 10 Min#/Max# keys in each section (Min1 to Min10 and Max1 to Max10)
;Min# key defines lower limit (downto and including) of ID number range
;Max# key defines upper limit (upto and including) of ID number range
;Access rules: ID number is compared to each range defined in this file
;If ID is in one or more of Accept ranges and NOT in Reject any Reject ranges, access is allowed
;In case where ID number is in both Accept and Reject ranges, access is denied
;In case where ID number is not in any Accept ranges, access is denied
;In case where ID number is in some Reject range, access is denied
[3]: Yes, I removed this from original port because I did not understand it (I thought repeater would always stay in open internet, so connect from repeater to server would not work because of firewalls.)
Well, this should not be that hard to implement, I'll try to do that for next version.
Cheers,
Jari
Thanks for all of your work!!