qupfer wrote:
> texas_72 wrote:
>
> > With Softether server started:
> > http: //192.x.x.x/zm/ -> not found
> >
http://192.xxx/serviio/console/ -> not found
>
> > any ideas?
> >
> > thanks
>
>
> First: "Hiding" IPs from the private range (like 192.168.0.0/16, 10.0.0.0/8
> or 172.16.0.0/12) is not helping and unnecessary.
> So "we" must guess. Are "zm", "serviio" and
> transmission on the same machine? And they are on the NAS/VPN-Server or is it a
> different machine? Sure, we can "assume" you mean its all on the same...but
> say it directly is much better, if you want help.
>
> And you are sure, that "zm" and "console" are http-Links and not
> httpS? Because, by default, softether listen
> on Port 443, the https-Port.
>
> My personal "best" solution for remote acces is, bridge Softether to
> tap-device and then bridge the tap-device to eth0.
> With this, you can:
> - use your local nameserver and dhcp servcer for vpn-clients too
> - no "route" config needed
> - you can reach vpn-server through vpn
> - LLMNR/mDNS will work too (and all other protocolls, which is compatible with
> Ethernet, not only IP)
I know I forgot to point out a few things:
With Softether server started:
http: //192.xxx/zm/ -> 500 - Internal Server Error
http://192.xxx/serviio/console/ -> 500 - Internal Server Error
http://192.xxx:9091/transmission/web/ -> FOUND
problem both remotely and also within my wifi network.
With Softether server stopped
http: //192.x.x.x/zm/ -> FOUND
http: //192.x.x.x/serviio/console/ -> FOUND
http://192.xxx:9091/transmission/web/ -> FOUND
Logically only within my wifi network..
I think the differences that you notice is that it works the address using a port other than 80, in fact, work address with port 9091.