@Gertjan
thank for your long explanation. And I'm glad to hear that our neighbor has the same shitty law.
In our case the third member are renter in our house (Student flat). Normally we can trust them. But confidence is good, control is better. ;)
VPN was the first idea. I saw the all the problems from configuration to compatibility and our user don't have much experience in computing. So VPN is to complex. Setting up an VPN server is no option, because we are glad to have a stable server now. So never change a running system. ( I keep thin option in mind, but my primary aim is to login via the web interface)
I noticed your judicial aspect. The pf-Sense should only protect the internet access owner. If a user get hacked, give the password to a friend or something else, than it is the problem of the user. We need to lists internal IP <-> web IP (collected by the firewall) and internal IP <-> user (collected by the CP).
BTW to get access to the pf sense you have to login in our intranet over some AccessPoints which are protected by WPA2 password.
– back to the problem
My aim is to login via web interface to send an POST request via command line to server.
@Gertjan
PS : try using curl.
That is what I had tried. (see the quote of my first post). But this doesn't work.
curl -F ...
Response is nothing, no request, no login.
curl -- data ...
The response is an new login form. no login. The POST-URL is copied in the redirect field.
I think there is another security feature, which reject my POST requests.