Page 1 of 1

round robin problem

Posted: Wed Jun 06, 2018 9:14 am
by DjMohsen
hello;
i have setup a new round robin for nameserver , but unfortunately the connection intrupts and reconnects continusely ,
my gateway is: t.anti-filter.net
wich is rounded between tow ips , both are a copy of linux running softether4 and auth using radius astrisk , you can test connection using the name server i have provided and port :2000 with the credentials bellow
{
username: test
password: tsttst
port: 2000
name server: t.anti-filter.net
}
ps: you can ping each ip and connect them directly without problem, we need to solve problem with round robin wich we have set on the mentioned test NS,...
i appreciate your co-operation to solve this problem.
thank you


email: Dj.Moh3n

Re: round robin problem

Posted: Wed Jun 06, 2018 9:43 am
by cedar
Did you try to disable NAT-T connection?

Re: round robin problem

Posted: Wed Jun 06, 2018 1:36 pm
by DjMohsen
cedar wrote:
> Did you try to disable NAT-T connection?

i need to use both udp and tcp connections like direct connect
i can not disable it because vpn function will be useless

Re: round robin problem

Posted: Thu Jun 07, 2018 8:52 am
by cedar
NAT-T of SoftEther VPN uses UDP hole punching technology.
It is necessary to let the VPN client and VPN server throw UDP packets simultaneously.
The NAT-T broker service provided by SoftEther Corporation identifies the VPN server to be synchronized with the destination server name specified in the connection setting of the VPN client.
Therefore, it is impossible to correctly identify the destination VPN server with round robin DNS name.

Re: round robin problem

Posted: Sat Jun 09, 2018 6:47 pm
by DjMohsen
cedar wrote:
> NAT-T of SoftEther VPN uses UDP hole punching technology.
> It is necessary to let the VPN client and VPN server throw UDP packets
> simultaneously.
> The NAT-T broker service provided by SoftEther Corporation identifies the
> VPN server to be synchronized with the destination server name specified in
> the connection setting of the VPN client.
> Therefore, it is impossible to correctly identify the destination VPN
> server with round robin DNS name.

is there any way like changing source code to get it compatable ?

Re: round robin problem

Posted: Mon Jun 11, 2018 9:28 am
by cedar
Since this is the limit of the underlying technology, I think it is difficult to deal with by modifying the source code.