пробовал 192.168.0.200 / 255.0.0.0Я ожидал худшего
А нафига такие проблемы?! Особенно если вспомнить, что 192.168.0.0/16 -- это просто запись диапазона, а сети в этом диапазоне когда-то звались "класс С" = "/24" = "255.255.255.0"... [/more]только 192.168.0.0/24 не маршрутизируется в интернете, или весь 192.168.0.0/16 ?192.168.0.0/24 это одна из сетей диапазона 192.168.0.0/16, который не маршрутизируется весь (т.е. и любые другие сети из него, например 192.168.111.0/24 или 192.168.123.0/24, не маршрутизируются тоже).
Настраиваем на модеме port mapping......и регистрируем и прописываем в модеме Dynamic DNS, в обоих моделях он есть, после чего ходим на камеры по имени вроде mywebcam.dyndns.info, а на NAS, скажем, metpas-nas.noip.org
не маршрутизируются все "частные" диапазоны
А вообще, создание домена у них можно таки обойти, подсунув папочку с настройками (выше описано) Мне вот как раз хотелось бы, чтобы трафик шел через их сервер, так как у меня дома реальных айпи нет. How do I activate the NeoRouter Professional Edition?
If you have purchased NeoRouter Professional Edition, you should receive a product key in email. Please have the product key ready before starting the activation process.
a. Ensure NeoRouter server is running. b. Launch Configuration Explorer and sign in c. Open “General” page, click on the “Activate Product” button d. Enter the product key in the following dialog e. Click on the “OK” button to activate it
After successful activation, the “Activate Product” button will disappear and License status will show as activated.
If the server host is non-Windows, you can also activate using nrserver’s CLI. The command is as follows. On Mac nrserver executable is located under /Library/NeoRouter.
“nrserver –activateproduct <PRODUCT KEY>”
NeoRouter Mesh is a cloud-based zero-config remote access and VPN service. Simply follow the three easy steps below and you can start accessing remote computers within minutes.
http://www.neorouter.com/nrmesh.html
http://download.neorouter.com/Downloads/NRMesh/Update_1.6.0.2830/Windows/NeoRouter-1.6.0.2830-mesh-Setup.exe
думаю нет привязки к железу и на их сервере тоже не полезет для проверкиСогласен, т.к. всё нормально работает даже в отключенной от Инета локалке -- и сервер заводится, и клиент к нему по адресу коннектится.
What's new
* IPv6 support. NeoRouter can now support both IPv6 and IPv4 for underlying client-server connections and peer-to-peer connections. NeoRouter server and client can run on computers with public or NAT'd IPv4 address, computers with public IPv6 address, or computers with dual stacks. NeoRouter can connect these computers with various connection types into a virtual LAN and allow user to access them remotely.
Direct P2P connection can be established between two IPv4 computers or two IPv6 computers. Connection between an IPv4 only computer and an IPv6 only computer is relayed through NeoRouter server.
IPv6 is supported on all platforms except for Android and Tomato firmware.
* Full View and Personalized View of computer list. With Full View enabled, one can see the full computer list and new computer will be added to the list automatically. One can easily switch between those views.
* Implemented incoming connection throttle feature in NeoRouter Server and optimized sign in module to void high CPU usage when hundreds clients try to connect to the server.
* Allowed NeoRouter Mesh clients (all versions) to connect to NeoRouter Pro server and Pro clients can access NeoRouter Mesh as well.
* Use the Coordinated Universal Time (abbreviated UTC) instead of local date time in the logging and auditing.
* Updated Android build to use NDK r5c. See http://developer.android.com/sdk/ndk/index.html.
* Inline proxy setting parameter support in nrclientcmd (all versions)
-setproxy: set proxy information.
optional parameters: [noproxy]|[http|socks4|socks5,ip,port,auth|noauth,[username],[password]]
Bug fixes
* Fixed critical bug that may cause NeoRouter client hang while signing in
* Fixed bug that may cause Operating System accounts fail to sign in after the account information has been modified by Configuration Explorer. This issue may happen on Linux, Mac, FreeBSD and in-a-box versions.
* Fixed bug that may cause add-ons disappeared in Network Explorer
* Fixed bug which may cause stuck signing in after computer reboot (Windows client ONLY)
* Fixed bug which may cause client service for Linux crash when logging enabled
* Fixed bug that NicInterfaceName value in Feature.ini does not work properly on FreeBSD
* Other small fixes related to UI and so on
Предыдущая тема: DRIVER