easy way to keep out unwanted clients

[tamahome]

Just wondering if there was an easier way to keep out unwanted clients besides having a file with every clientid in them (which seems based on ipv6 addresses?).

Actually the firewall on the server blocks the data transfer part, but any client can still get the first announcement.

[Dennis Bush]

The client list on the server is the only way to keep out unwanted clients.

Besides the ID number of the client (by default, the 4 least significant bytes of the primary IP), it can also contain the client's key fingerprint to authenticate the client during encrypted transfers.

[tamahome]

Actually, I'm in Windows 10, and I don't understand where the clientid is coming from. The serverid I can see is the hex version of the ipv4 address, but not the clientid. Is it from the ipv6 link local address? If it is, I can't see it.

Oh, I get it, it's backward pairs from the end, from the link local ipv6 (fill in the 0 before the f, ignore the %5):

clientid 0x8adee80f

Link-local IPv6 Address . . . . . : fe80::4925:d301:fe8:de8a%5

[Dennis Bush]

It is the last 4 bytes of the IPv6 address, but in the reverse order.

The ID has bytes 8a de e8 0f
The last 4 of the IP has bytes 0f e8 de 8a

[tamahome]

I was trying the -S option with the client, but I get this error? servers.txt just has a pingable ipv4 private address on the same network:

uftpd.exe -x 5 -S servers.txt -M 232.0.0.1
Invalid server name/address (null): No such host is known.

servers.txt:
172.17.64.206

[Dennis Bush]

The serverlist file must contain the ID of the server followed by its IP. This is listed in the included documentation.

Assuming the server doesn't have an IPv6 address and you didn't assign it an ID, the file should contain:

0xAC1140CE|172.17.64.206

[tamahome]

Oh, I've been using the online version of the docs. http://uftp-multicast.sourceforge.net/client_usage3.txt Thanks! Oh I see, I googled the wrong version.