IP-Adresse des Clients einer HS-Session

[vince]

Hallo!
Gibt es ein (internes) Kommunikationsobjekt oder eine andere Variable im Homeserver-Experten, welche die IP-Adresse des PCs speichert, der über den HS-Clients oder Webbrowser die Http-Session zum Homeserver aufbaut?
Ich möchte auf der Visu beim Klicken auf ein Symbol ein UDP/IP-Paket an den PC senden, um dort bestimmte Aktionen auszulösen. Der HS muss diese Adresse ja kennen, sonst könnte er nicht antworten, aber wie bekomme ich die im Experten mit? Bei "IP/EIB-Telegramme senden" muss ich den Empfänger immer STATISCH eintragen.
Hat jemand eine Idee?

Danke und Gruß

[Michel]

Nein, diese Information ist nicht verfügbar.
Auch das Senden von IP-Telegrammen an "dynamische" IP´s ist nicht möglich.

Allerdings sind die IP´s der Benutzer verfügbar: Login-Liste.

Wie wäre es alternativ mit einer speziellen Seite für jeden Benutzer? Dann ist die IP definiert. Z.B. Benutzer "Kinderzimmer" -> Startseite "Kinderzimmer" -> klick auf Symbol -> Telegramm an IP "Kinderzimmer".

[Warichet]

welche die IP-Adresse des PCs speichert, der über den HS-Clients oder Webbrowser die Http-Session zum Homeserver aufbaut?

I've the same request, and I think it is possible , as Michel said, via the Login list.
I'm working on it, hammering with Python (oh what a pain) , hoping to have it ready ........ before Christmas

It's a pitty this internal object is not exposed to user usage.

[MatthiasS]

The problem with "the pitty" is:

HS accepts up to 200 simultaneous sessions. So "this internal object" wouldn't work at all.

[Warichet]

HS accepts up to 200 simultaneous sessions.

Hé, that keeps the CPU busy

So "this internal object" wouldn't work at all.

Aah
I'm curious now, can you tell me more ? as I don't even understand the problem.
Not willing to put any critic on the HS, but Windows exposes thousands of internal objects, each having dozens of methods and properties, which any user can grasp with classical programming languages. I used those objects from the Win32, WMI etc to write system tools.

So I guess Linux can to the same or better, unless it is an architectural design decision (as opposed to a system shortcoming) not to expose those objects.

Thank you for shedding some light on the topic.

[MatthiasS]

I wanted to say, that it does not help to have one IKO because there could be up to 200 sessions. So you need 200 iKOs aka an arry.

On my guest account for my demo HS I had up to 20 users at the same time. So putting this to one iKO does not help.

On the other hand, what do you want to do with this information? You can have a login list that tracks every login for month with all data you need.

Why putting the IP address of the last visitor that logged in on the visu window?

[Warichet]

it does not help to have one IKO because there could be up to 200 sessions. So you need 200 iKOs aka an arry.

Mmm, well euuh, yes, why not ?
Those 200 iKOs are not fired-up at start, but rather created on-demand for each detached process/user session (or fork as you say in Linux) up to the max limit of 200 set in a param of the OS. Nothing wrong with that. It consumes resouces ? well yes !

On the other hand, what do you want to do with this information? You can have a login list that tracks every login for month with all data you need.

Yes, sure you are right.
But I see the login list as a separate web page not integrated in the visu, so I mean, you have to go explicity to that page to see what's up.
Personally, I would prefer to see the relevant info integrated in the visu, on a page summarizing the external world.

Why putting the IP address of the last visitor that logged in on the visu window?

Oh well, this is more an academic execise of a HS newbie that tries to learn via practical examples.
Nevertheless, I'm interested in the guest visitors only (I do not check regular visitors owning a HS account). My final goal is to setup an archive to save the guest visits (IP addr, date & time).
I was hoping for much more information (dreaming awake ) like the stats that a webmaster can get about his visitors. Of course the HS is not a web server, there it stops.

Thank you for taking the time to reply.

[MatthiasS]

You are welcome

My final goal is to setup an archive to save the guest visits (IP addr, date & time).

Exactly what the login archive does .

Including/inserting all types of archives (especially data archives) into the HS GUI is one of my favourite tasks for the next HS update. In my opinion this feature is very important.