Bind Serviio to specific IP not working

I've used the entry
-Dserviio.boundAddr=192.168.0.5
in the ServiioService.exe.vmoptions, and Serviio binds successfully to this IP

However the following services
2013-06-15 06:59:35,862 INFO [RestletServer] Starting Restlet server (/rest) exposed on port 23423
2013-06-15 06:59:35,884 INFO [RestletServer] Starting Restlet server (/cds) exposed on port 23424
2013-06-15 06:59:35,885 INFO [RestletServer] Starting Restlet server (/mediabrowser) exposed on port 23424
bind to all IPs

I can prove this by starting a service and then trying to connect to it on all the IP's on my server

Any way to force the above services to connect on the specified IP's ONLY

Andrew

[will]

That's by design and probably won't change eg the console connects to local host by default when installed on the same machine. If you really want you can block access using a firewall.

if that's by design, then whats the point in the bind address to the alternate IP ????

Also these ports are on ALL allocated IPs.

That cant right.....

[zip]

These are Serviio specific API ports. The UPnP/DLNA server is bound to the selected IP only and Serviio uses the IP to multicast its presence as well.

Thanks petr,
It just seems strange that only part of the product is managed by the IP binding. If other parts of the app are not using the rules, then this appears to negate the usefulness of the bind options,
or have i missed something ? I have only ever seen specific binding to allow the entire product to be locked to a specific IP by one or more config settings.


Will serviio be updated to allow the IP bind config to work for all services?

Andrew

[zip]

It's there to notify the devices what is the IP that Serviio is listening on. Again, it's only for the UPnP part. The non UPnP APIs listens on all IPs. This will not change.

This is a long-shot but I thought I'd ask.
Just for "fun" I'm trying to run Serviio in a local Kubernetes cluster. I've almost got it working but I think I'm stuck because the UPnP part is advertising the IP address of the pod (10.1.20.119), which is an internal, cluster IP.
I think what I need is a way of overriding the IP address that's advertised so that when the devices on the network use the IP address, they are using the networking-facing IP address allocated by the Load Balancer.

Is there a way of overriding the IP address that's broadcast?

I know that there's a serviio.bindAddr and I've tried setting it to the network facing IP address but then I see errors in the logs ([MultiCastUtils] Host IP address 192.168.2.200 is not available, will try again 9 times) because the pod can't see that IP address. I need it to bind to the pod address but advertise a different one.