Topic: SVN protocol via SME firewall

[leonp]

Hello.
I have the SME 9.2 running and installed the svnserve for the svn clients access using the SVN protocol.
For this, the 3690 TCP port must be accessible. SO, I did as described in https://wiki.contribs.org/Firewall:

config set svn service access public status enabled TCPPort 3690
config setprop svn AllowHosts 192.168.50.0/24   (my local network)
signal-event remoteaccess-update
signal-event reboot

but still, when I try:
telnet 192.168.50.254 3690  (server address)
I receive:
telnet: connect to address 192.168.50.254: Connection refused

Any help will be highly appreciated.

[Jean-Philippe Pialasse]

Hello Leonp,

apart from trying to have a SVN client access, what was your initial need ? (without background, from there it seems like a XYproblem)
Have you got a look at https://wiki.contribs.org/Subversion which includ webdav SVN access?

Hello.
I have the SME 9.2 running and installed the svnserve for the svn clients access using the SVN protocol.
For this, the 3690 TCP port must be accessible. SO, I did as described in https://wiki.contribs.org/Firewall:

config set svn service access public status enabled TCPPort 3690
config setprop svn AllowHosts 192.168.50.0/24   (my local network)
signal-event remoteaccess-update

I will assume your SME is configured as gateway server and not server only, as you did not mention that. Then if your SME LAN is 192.168.50.0/24, you do not need this kind of setting but rather :

Code: [Select]

config set svn service access private status enabled TCPPort 3690
signal-event remoteaccess-update

to change from your current status:

Code: [Select]

config setprop svn  access private
config delprop svn AllowHosts
signal-event remoteaccess-update

signal-event reboot

this is not needed after remoteaccess-update

but still, when I try:
telnet 192.168.50.254 3690  (server address)
I receive:
telnet: connect to address 192.168.50.254: Connection refused

Any help will be highly appreciated.

By default all ports are open to the LAN without the previous commands. So my first guesses would rather be:
- is your service running ?
- is it really listening on that port 3690?
- is it listening on this ip192.168.50.254  (some might only listen on loopback by default, or on nothing until specified)?
- have you tried telnet from localhost (ie from the server itself)?

[leonp]

Jean-Philippe, thank you very much for your detailed reply.
I am very ashamed.
I new that I am stupid and you proved it again...
I was sure that svnserve is running, as it resides in all rc.d directories, but it was not.
I beg your pardon for disturbing...

[Jean-Philippe Pialasse]

You will need a link in rc7.d for SME and an entry in config db as service with exact same name as process :

config set svnserve service status enabled

Then i suggest to move all the entries from the previous key there.

Again are you sure you want to use svnserve and not mod dav svn? When using port 3690, you are sending password without encryption over the network. Alternative would be to close that port and use ssh +svn. But easiest way would be to stick to https and mod dav svn as all is offered in a contrib.... unless you have a specific app using only svn protocol...

See https://stackoverflow.com/questions/6227893/why-choose-mod-dav-svn-instead-of-svnserve-a-repository-browser

[leonp]

I have read the link.
My considerations to use svnserve were: we have 2 programmers using it solely on internal network via kdesvn client. We got used to it. There is no need in WEB access, remote access, etc.
May be I am wrong, but it seems to me in my case mod dav svn will be more obstacle than help...
Thank you again fir your help.