SVN client connectivity issues on Linux virtual machines __linux

Background

In the construction of the virtual machine to set up SVN, in the SVN client connection when there are some problems, the cost of a great deal of effort, and ultimately with the help of experienced experts to successfully solve. The following is an analysis of their own problems.
problem

Can ' t connect to host ' 192.167.33.10 ': The connection attempt failed because the connecting party did not respond correctly after a period of time or the host connected was not responding.

Reason

1, IP may be occupied, to replace a not occupied by IP address

2, the firewall 3690 ports do not open up the solution

The first step: Modify the configuration file: Vi/etc/sysconfig/iptables

<span style= "FONT-SIZE:18PX;" > # Firewall configuration written by System-config-securitylevel # Manual Customization of this file I  
      
    s not recommended.  
      
    *filter:input ACCEPT [0:0]: FORWARD ACCEPT [0:0]: OUTPUT ACCEPT [0:0]  
      
    : Rh-firewall-1-input-[0:0]-A input-j rh-firewall-1-input-a forward-j rh-firewall-1-input  
      
    -A rh-firewall-1-input-i lo-j accept-a rh-firewall-1-input-p ICMP--icmp-type any-j ACCEPT -A rh-firewall-1-input-p 50-j accept-a rh-firewall-1-input-p 51-j accept-a RH -firewall-1-input-p UDP--dport 5353-d 224.0.0.251-j accept-a rh-firewall-1-input-p udp-m UDP--dport 6 31-j accept-a rh-firewall-1-input-p tcp-m TCP--dport 631-j accept-a- M state--state Established,related-j accept-a Rh-firewall-1-input-M state--state new-m tcp-p TCP--dport 22-j accept-a rh-firewall-1-input-m State--state new-m tcp-p  
      
    TCP--dport 80-j accept-a rh-firewall-1-input-m the state--state new-m tcp-p TCP--dport 443-j ACCEPT -A rh-firewall-1-input-j REJECT--reject-with icmp-host-prohibited COMMIT </span>

The second step: Change the IP address, open the Vagrantfile file to modify, the results are as follows.

<span style= "FONT-SIZE:18PX;" ># Create a private network, which allows host-only access to the machine
  # using a specific IP.
  Config.vm.network "Private_network", IP: "<span style=" color: #FF0000; >192.168.11.18</span> "</span>

Step Two: Restart the virtual machine

Step three: Modify the session in Xshell, and the results are as follows:

Step fourth: Go back to SVN for configuration and start SVN

<span style= "FONT-SIZE:18PX;" >[root@localhost vagrant]# mkdir-p/var/svn/svnrepos [root@localhost-vagrant]# svnadmin create/var/svn/
Svnrepos
svnadmin:e165002: '/var/svn/svnrepos ' is a existing repository
[root@localhost vagrant]# /svnrepos
[root@localhost svnrepos]# ls
conf  db  format  hooks  locks  README.txt
[ Root@localhost svnrepos]# CD conf
[root@localhost conf]# ls
authz passwd svnserve.conf
[ Root@localhost conf]# vi passwd
[root@localhost conf]# vi authz
[root@localhost conf]# VI svnserve.conf
[Root@localhost conf]# svnserve-d-r/var/svn/svnrepos
</span>

Step Fifth: Add inbound rules, and then start SVN

<span style= "FONT-SIZE:18PX;" >[root@localhost conf]#/sbin/iptables-i input-p tcp--dport 3690-j ACCEPT
(root@localhost conf]#/ETC/INIT.D/IP Tables Save
Bash:/etc/init.d/iptables:no such file or directory
[root@localhost conf]# service iptables restart
redirecting to/bin/systemctl restart  iptables.service
Failed to issue method Call:unit Failed to load:no such file or directory.
[Root@localhost conf]# svnserve-d-r/var/svn/svnrepos
svnserve:E000098:Can ' t bind server socket:address already I n Use
</span>

It's no problem to use the SVN client to connect to the server here. tips for small extensions

The path to install your own software as far as possible with all English without spaces, otherwise it is likely to have some problems, I have eaten in this area has been a big loss, I remember oh.
Summary

When you encounter problems, do not be discouraged, to find information on the Internet, to do experiments, to ask people who have experience in this area, the problem can always be solved. If you encounter problems the world will not, then you can apply for a patent, haha.