Folding Forum

That's fair enough, but if it says "allow 127.0.0.1" and "deny nothing", I'd assume that wouldn't let in say 192.168.1.52. I used to work in network administration, what are standard non-IT-literate users supposed to think of this? An interface should always make sense, not be ambiguous, and be simple for a simpleton to use.

Huh?
Deny nothing means allow anything.

So why is 127.0.0.1 in there?

Anyway it actually says that zero matches all IP addresses. So the default is deny everything, which I assume means the allow list overrides that.

The advanced control panel and other tools communicate with the client over TCP.
127.0.0.1 is localhost, it means the tools running on the computer can access the client.
You add IP ranges or subnets to the Allow list to allow other computers to communicate with the client.

AFAIK the allow list takes precedence over the deny list.
0/0 basically means everything is blocked.
It's still worth remembering that the client is a little glitchy and it's hit or miss as to whether the changes will take immediate effect or need the client to be restarted, we always recommend restarting after making changes.

So 127.0.0.1 in allow and 0/0 in deny should mean all is blocked except local. But that's not what's happening. I can get to all the computers from another one on the LAN.

Some changes will only take effect after the client has been restarted.

Maybe I need to say, the advanced control panel is not the client. Restarting the advanced control panel does not restart the client.

There are a couple of options to restart the client
1). click the multicoloured bubble on the notification area of the taskbar, select Quit. Start -> Folding@Home -> Folding@home
2). reboot the computer

As I said before, deny 0/0 gets special, UNDOCUMENTED treatment.

If a password is set, 0/0 is deny none, instead of deny all. This was changed because so many people had trouble configuring remote access.

If you use deny 0.0.0.0/0, you will get deny all.

So 0/0 is the opposite of what it says, but 0.0.0.0/0 is what it says. This is even more confusing!

calxalot wrote:As I said before, deny 0/0 gets special, UNDOCUMENTED treatment.

If a password is set, 0/0 is deny none, instead of deny all. This was changed because so many people had trouble configuring remote access.

Thanks, looks like I have some testing ahead of me.

Since you've changed what 0/0 means, this should be reflected in the instruction only 3 lines above it, which still says it denies all.

Yes, but I’m afraid you’re complaining about something that won’t change.

Development is focused on version 8 now.

It’s extremely unlikely that there will be another v7 release.

I don't care if it's in 7 or 8, as long as it's fixed! Mind you I'd prefer them to enhance the advanced control so I can monitor multiple machines at a glance without having to click each one.

The next version of the client will most likely be focused on improving the science - what the interface is like is at this point not known but is likely to be the culmination of many inputs from folders and the requirements of the researchers ... with still a relatively small amount of dev effort what is finally delivered will be prioritised by the core fah team and the devs ... advanced multi rig management requirements that benefit a limited pool of folders may not be that high on the priority list - in the past this has been the realm of the specialist enthusiast non fah devs who produce their own interfaces (such as hfm and various apps/web interfaces that exist) - I wouldn't expect there to be major developments in that area however that is simply a guess on my part as a volunteer folder ... I would have expected dev effort to be taken improving assignment and moving the code more towards open source but again just a guess on my part