Client losing log-in settings on service restart (Raspberry)
Page 1 of 1

Author:  Alfredo [ Sat Sep 08, 2018 6:26 pm ]
Post subject:  Client losing log-in settings on service restart (Raspberry)

I installed the NeoRouter Client on the Raspberry Pi Zero W, updated the NIC name in Feature.ini as "wlan" and it seemed to work without an issue.
After running nrclientcmd the Client logs in and appears online to the other clients, but at this point the Raspberry cannot communicate with other clients and vice versa (cannot ping).

ifconfig shows that there's the ntrap adaptor, but all stats are zero:
nrtap: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet  netmask  broadcast
        inet6 fe80::529b:70b6:9145:5a2  prefixlen 64  scopeid 0x20<link>
        ether 3e:2f:86:e8:81:65  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Another issue is that if nrservice is restarted manually or by system restart, it does not connect to the server again. I have to run nrclientcmd and enter the connection info again before the RPi can appear online to other clients.
I have enabled debugging and examined the generated log to see that the service, when restarted, attempts to connect to the server at localhost on the default port, but my server is on another machine and listening to a non-default port. It seems that the service is losing the domain information when it's restarted.

What am I missing here?

Thanks for any help you can offer.

Author:  Alfredo [ Mon Sep 10, 2018 11:27 am ]
Post subject:  Re: Client losing log-in settings on service restart (Raspberry)

Somehow all the issues got resolved by doing the following:

- I reset the server settings to use the default port and the network
- Logged in on the RaspberryPi, and thing are working very well now.
- Changed back the port on the server to my favorite 443.
- Restarted the service on the RPi and logged in again. It works.
- Changed back the network on the server to
- Restarted the service on the RPi and logged in again. It works.
- Restarted the OS on RPi, and it logs in to the VPN automatically.

I don't understand why it wasn't working, and why it is working now, but the problem is solved for the moment.

Page 1 of 1 All times are UTC - 5 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group