NextSync Release Thread

[tadaguff]

^linux

[sol_hsa]

works great, thanks. had to create /sys/config manually, but you know that.

That's one bug I don't understand. I'll have to do some more testing, I guess.

NB the python script only shows localhost as my interface but the server works fine when I enter the IP/name on the Next

Have a screenshot or just copy-paste of the text? I develop on windows, but it being python it should(tm) give the same kinds of answers everywhere..

[tadaguff]

[stuart@nurse server]$ ./nextsync.py
NextSync server, protocol version NextSync3
by Jari Komppa 2020

Running on host:nurse
IP addresses:
127.0.1.1

Note: Using /home/stuart/dev/server as sync root
Note: Ready to sync 0 files, 0.00 kilobytes.

2020-06-01 14:48:20 | NextSync listening to port 2048

[tadaguff]

heh, I notice that's 127.0.1.1 not loopback, and indeed my OS installer has put that against the local hostname in /etc/hosts so it's pretty reasonable for python to use that. Manjaro (based on Arch Linux) fyi. I wouldn't pursue this further if I were you.

[sol_hsa]

heh, I notice that's 127.0.1.1 not loopback, and indeed my OS installer has put that against the local hostname in /etc/hosts so it's pretty reasonable for python to use that. Manjaro (based on Arch Linux) fyi. I wouldn't pursue this further if I were you.

Thanks for the report anyway =)

[chris]

heh, I notice that's 127.0.1.1 not loopback, and indeed my OS installer has put that against the local hostname in /etc/hosts so it's pretty reasonable for python to use that. Manjaro (based on Arch Linux) fyi. I wouldn't pursue this further if I were you.

Incidentally the same happens on Raspberry Pi OS.
It's picking the IP up from /etc/hosts, not the one assigned to the interface.

It's probably not worth fixing, but I found some Stack Overflow answers which apparently give correct results on Linux and Windows.

[varmfskii]

When doing IP address lookup, /etc/hosts is generally first. If you name is listed as 127.0.1.1 (which while not strictly the standard localhost *is* loopback) then that is what you expect to get. The entire class A network 127.x.x.x is supposed to be loopback. If you want your hostname to access the (one of the) actual network addresses, you need to edit /etc/hosts. That said the loopback network is likely to be the fastest. It is better to lookup your addresses using something like ifconfig or ip address which will give all your addresses.

[sol_hsa]

I've added the "open a connection and see" method of figuring out your IP in case your IP contains 127 or you seem to have several IP addresses. Should cover most bases.

[paulland]

I have finally got to the point on my job list to investigate/need NextSync.

I have been following the provided instructions. I have an internet connection with my Next confirmed by going online with Nextel. I have the NextSync server setup on my PC (called VADER) and is waiting for a connection.

On the Next, issuing a .sync



which is as expected according to the docs, so I then issue a .sync VADER or .sync 192.168.0.15




but then I get the error about not being able to open the file.

Going to the SYS directory shows me that there is no config directory let alone a nextsync.cfg file, unless of course it is hidden.






I'll get a different SD card and make a another NextZXOS build to try next.

Any other ideas?


Cheers

[sol_hsa]

Create the file by hand. There's a bug I've already fixed that fails to create the directories if they don't exist.