Community


All times are UTC - 5 hours




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: Centos 7 server running 2.3.1.4360 - Feature.ini broken?
PostPosted: Sat Apr 29, 2017 2:32 am 
Offline

Joined: Tue Sep 27, 2016 8:26 pm
Posts: 7
I just realized tonight that when I run openvpn client on same server as nrserver, that it reports the openvpn's public IP instead of the VPS's public IP. This causes clients to fail to connect unless I manually enter the VPS IP instead of domain name. I do NOT want to hardcode the IP, that's the whole point of the domain.

# ls /usr/local/ZebraNetworkSystems/NeoRouter/Feature.ini
/usr/local/ZebraNetworkSystems/NeoRouter/Feature.ini

# cat Feature.ini
AltServer=$$$$$$$,xxx.xxx.xxx.xxx:32976
DNSCache=1
AutoUpdateDomain=0
#Description: Whether disable SSLv3 protocol and use TLS only
#Options: 0-Disabled; 1-Enabled
#Default: 1
DisableSSLv3=1
HostIPType=1

With the $$$'s and xxx;s changed for my actual, nrserver keeps overwriting the domain IP that is reported when I login to Neorouter website. My /etc/hosts file has the domain name set for the VPS IP.

Log.ini correctly works and is how I can verify that the Feature.ini is not being used. Also, your wiki needs to be updated because clearly SSLv3 is NOT disabled by default. That is really shocking and ticked me off...

Is Feature.ini broken in this version?

2017-04-29 07:14:09|00608|140485020120960|******************************************
2017-04-29 07:14:09|00608|140485020120960| TraceLog Starts
2017-04-29 07:14:09|00608|140485020120960|[hostname]
2017-04-29 07:14:09|00608|140485020120960|
2017-04-29 07:14:09|00608|140485020120960|2.3.1.4360
2017-04-29 07:14:09|00608|140485020120960|******************************************
2017-04-29 07:14:10|00608|140485020120960|I|Check existing instance: hr=0x0
2017-04-29 07:14:10|00608|140485020120960|I|Initialize DB: hr=0x0
2017-04-29 07:14:10|00608|140485020120960|I|Load domain information: hr=0x0; DomainName=$$$$$$$; Port=32976
2017-04-29 07:14:11|00608|140485020120960|I|CreateTimerQueue
2017-04-29 07:14:11|00608|140485020120960|I|CreateTimer: TimerQueue: 1, DueTime: 15000
2017-04-29 07:14:11|00608|140485020120960|I|CreateTimer: Succeeded. hTimer: 2, lstTimers size: 1
2017-04-29 07:14:11|00608|140485020120960|I|Initialize domain updater: hr=0x0
2017-04-29 07:14:12|00608|140485020120960|I|CreateTimerQueue
2017-04-29 07:14:12|00608|140485020120960|I|CreateTimer: TimerQueue: 3, DueTime: 30000
2017-04-29 07:14:12|00608|140485020120960|I|CreateTimer: Succeeded. hTimer: 4, lstTimers size: 2
2017-04-29 07:14:12|00608|140485020120960|I|Initialize product updater: hr=0x0
2017-04-29 07:14:12|00608|140485020120960|I|Found IP: index=1; IP=192.168.232.1
2017-04-29 07:14:12|00608|140485020120960|I|CreateTimerQueue
2017-04-29 07:14:12|00608|140485020120960|I|Initialize ClientMgr: hr=0x0
2017-04-29 07:14:13|00608|140485020120960|I|Server instance started hr=0x0
2017-04-29 07:14:21|00608|140484848625408|I|CClientMgr::OnAccept(15)
2017-04-29 07:14:21|00608|140484848625408|I|CreateTimer: TimerQueue: 5, DueTime: 17000
2017-04-29 07:14:21|00608|140484848625408|I|CreateTimer: Succeeded. hTimer: 6, lstTimers size: 3
2017-04-29 07:14:21|00608|140484994631424|I|SSL_CB_HANDSHAKE_START
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:before/accept initialization
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:SSLv3 read client hello A
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:SSLv3 write server hello A
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:SSLv3 write certificate A
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:SSLv3 write server done A
2017-04-29 07:14:21|00608|140484994631424|I|SSL_accept:SSLv3 flush data
2017-04-29 07:14:21|00608|140484994631424|I|R retry R
2017-04-29 07:14:21|00608|140484994631424|I|SSL handshaking W 968
2017-04-29 07:14:21|00608|140484994631424|I|R retry R
2017-04-29 07:14:21|00608|140484994631424|I|W retry R
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 read client key exchange A
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 read finished A
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 write session ticket A
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 write change cipher spec A
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 write finished A
2017-04-29 07:14:21|00608|140484969453312|I|SSL_accept:SSLv3 flush data
2017-04-29 07:14:21|00608|140484969453312|I|SSL_INFO_ESTABLISHED
2017-04-29 07:14:21|00608|140484969453312|I|SSL connection using AES256-SHA
2017-04-29 07:14:21|00608|140484969453312|I|Peer does not have certificate.
2017-04-29 07:14:21|00608|140484969453312|I|R retry R
2017-04-29 07:14:21|00608|140484969453312|I|SSL handshaking W 234
2017-04-29 07:14:21|00608|140484969453312|I|R retry R
2017-04-29 07:14:21|00608|140484969453312|I|W retry R
2017-04-29 07:14:21|00608|140484969453312|I|SSL Handshake completes
2017-04-29 07:14:21|00608|140484882196224|I|CreateTimerQueue
2017-04-29 07:14:21|00608|140484882196224|I|CreateTimer: TimerQueue: 7, DueTime: 15000
2017-04-29 07:14:21|00608|140484882196224|I|CreateTimer: Succeeded. hTimer: 8, lstTimers size: 4
2017-04-29 07:14:21|00608|140484882196224|I|ComputerHandler::Connect
2017-04-29 07:14:21|00608|140484882196224|I|ComputerHandler::ConnectActual
2017-04-29 07:14:21|00608|140484882196224|I|Found IP: index=17; IP=192.168.232.17
2017-04-29 07:14:22|00608|140484882196224|I|DeleteTimer: hTimer: 6, fWait: 1
2017-04-29 07:14:22|00608|140484882196224|I|CClientMgr::OnClientAuthenticated(15, 1, 300460224)
2017-04-29 07:14:22|00608|140484882196224|I|ComputerHandler::NotifyComputerOpen
2017-04-29 07:14:22|00608|140484882196224|I|192.168.232.17 is opened, hr=0x0


Top
 Profile  
 
 Post subject: Re: Centos 7 server running 2.3.1.4360 - Feature.ini broken?
PostPosted: Tue Oct 03, 2017 7:54 pm 
Offline

Joined: Tue Sep 27, 2016 8:26 pm
Posts: 7
5 months and no comment on two bugs? Linux version much older than the other versions.

Has development stopped and I should stop with testing and bug reports?


Top
 Profile  
 
 Post subject: Re: Centos 7 server running 2.3.1.4360 - Feature.ini broken?
PostPosted: Mon Oct 09, 2017 3:42 am 
Offline

Joined: Fri Aug 19, 2016 6:57 am
Posts: 13
MaxBlitzer wrote:

Has development stopped and I should stop with testing and bug reports?


I am afraid so...


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron