There dont seems to possible to bind the qnapcloud service to a specific ethernet interface, is there a way to do it?
if not QNAPCloud then the VPN service/DDNS.
Service Binding
-
VincentM
- Easy as a breeze
- Posts: 392
- Joined: Mon Jan 04, 2010 11:58 am
- Location: Indian Ocean
-
schumaku
- Guru
- Posts: 43578
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: Service Binding
Obviously only interface holding the default interface can be used - think about it.... Anything else does not make a much useful configuration.
Completely mistaken as myQNAPcloud is not a service running on the NAS, listening on a certain interface at all.
Or do you use service bindings for DDNS service somehow?
Bind the VPN service to a different interface than the one able to communicate to the outside world - or are you concerned the VPN server might be abused internally somehow? The only reason to bind VPN to a specific interface - respectively not to bind it to all. VPN is a dedicated service, independent of myQNAPcloud.
Completely mistaken as myQNAPcloud is not a service running on the NAS, listening on a certain interface at all.
Or do you use service bindings for DDNS service somehow?
Bind the VPN service to a different interface than the one able to communicate to the outside world - or are you concerned the VPN server might be abused internally somehow? The only reason to bind VPN to a specific interface - respectively not to bind it to all. VPN is a dedicated service, independent of myQNAPcloud.