vpn ibm-cloud Cannot get to private addresses via VPN - ecm

Apparently Softlayer changed the VPN. So I've reinstalled my MotionPro client on Win10 and can now connect. But I can no longer connect to the 10 addresses beyond it. They don't show up in the netstat -rn listing.
I can ping the remote end of the VPN, but not the 10 addresses. What else do I need to do to make this happen?
Thanks.

No worries. It turned out the VPN entry point has changed, and when I use a different one it now gives me all the correct routing.

Related

Popup page without internet connection using coova-chilli

I am using openwrt and coovachilli for registration purpose, when there is presence of internet connection to router then chilli starts and popup page appears after connect to WiFi.
But I want popup page without presence of internet. Router should popup after connect to WiFi using coovachilli without internet. Please help me out in this situation.
Thanks in advance.
OpenWrt Version:- 15.05
CoovaChilli Version:- 1.3.0
It's not possible technically due to the way Coova Chilli (and other hotspot software systems) works.
Without Internet connection, your DNS server will return failures so no DNS query will work. Without DNS queries (and IP addresses as result), there won't be a HTTP request for Coova to hijack. Your device (eg. iPhone) won't even trigger a CNA window
There are possibilities (workarounds) of course - eg. make your DNS resolver (dnsmasq?) resolve to some dummy/hardcoded IP address while the connection is down. You would have to write a script yourself that detects connection and swaps configs
It is possible with a workaround.
You have to use a local UAM server (on the same host or LAN) and authenticate with local users file or local RADIUS server. For using local users file, without RADIUS server, you must specify a dummy RADIUS server IP:
radiusserver1 127.0.0.1
localusers /etc/chilli/localusers
Then, you can add a dummyuser:dummypass to your localusers file and use it for the authentication as usual:
http://${uam_ip}:${uam_port}/logon?username=dummyuser&password=${chap_password}

Cant connect to my PLEX Media server outside my network

iam currently trying to make a plex media server, ive been using windows 8.1 because that was the installation i had laying around. but now i think ive tried everything to make it working outside my network.
when i "connect" on the plex it shows:
so i guess it knows my server, and it knows my public ip and what ports to use, but still no internet? ive talked a friend and he said he sat the remote access port on the server, but i dont think i have that option on win8.
what ive tried:
port forwarding 32400
set up firewall to allow 32400
putting the server in a DMZ
any ideas?
The Problem was double NAT at my ISP :-)

oVirt engine 3.6 in local Internet **connectionless** network

I wanna use oVirt engine 3.6 in my Internet connectionless network. I installed oVirt with yum over internet. After that I tried to work offline. When I go offline Web Interface it still works fine. But I connected it to my local netowork Interface starts not to respond. I check POST/GET requests that made by it and I see it stuck on request/respond to/from GenericApiGWTService. For example, normally time between request and respond takes 1 to 600ms but when I connect it to local network it take up to 300.000ms second and eventually it fails. I use CentOS 7 x86_64. I couldn't figure out what is it cause to that.
I fix the problem by;
Use another IP from different address group then the one you use for
internet connection. Example: I used 192.168.1.10 for internet
connection. When I connect pc to local I changed it to 192.168.2.10
Delete all Gateway and DNS IPs.
Then it works fine.

How to serve a website over a wifi without internet?

I want to serve a website over an open wifi connection but I do not want this wifi connection to have access to the internet. Is this possible and how would I go about doing it.
I have setup websites locally and have gotten access in the browser through localhost or the IP address but I am not sure how I would go about setting up a webserver and serving the website via wifi.
Any insight on this?
you can access your machine's localhost via any computer easily, as long as that computer is connected to the said wifi.
get your computer name, and access it from other machine like this:
http://<your_computer_name_here:port_if_applicable>/website_folder_name
I do this to test my websites on mac and windows at home. My windows machine is called "The-Genius" and I access it via my mac like this:
http://The-Genius/Test/
which leads to the IIS.. if I want to access Apache, which is on port 78, I do this:
http://The-Genius:78/Test/
Hope it helps..
If you are using a wifi router, you don't have to do anything to get this to work. Whenever a client connects over wifi, they will be able to type in your webserver's IP address to see the website. If you want to use a DNS name then you might be able to set up the DNS names on the router itself.
Based on #LocustHorde's answer,
I tired the pc's IP address instead of using the pc name.
This worked fine for me...
http://172.168.1.21:8080/test/aa.php

Restrict the server access from LAN only

Recently we got a new server at the office purely for testing purposes. It is set up so that we can access it from any computer.
However today our ip got blocked from one of our other sites saying that our ip has been suspected of having a virus that sends spam emails. we learned this from the cbl http://cbl.abuseat.org/
So of course we turned the server off to stop this. The problem is the server must be on to continue developing our application and to access the database that is installed on it. Our normal admin is on vacation and is unreachable, and the rest of us are idiots(me included) in this area.
We believe that the best solution is to remove it from connecting to the internet but still access it on the lan. If that is a valid solution how would this be done or is there a better way? say blocking specified ports or whatever.
I assume that this server is behind a router? You should be able to block WAN connections to the server on the router and still leave it open to accepting LAN connection. Or you could restrict the IPs that can connect to the server to the development machines on the network.