I want to make genymotion's android phone's internet to work with tor proxy.
I added
Proxy server: 127.0.0.1:9150 - To access Tor port
Rule player.exe with 192.168.58.* port with Virtual Box only network action. To isolate genymotion -> virtual box communication.
Genymotion's phone runs correctly, but without internet. How should I route 5555 wifi port for adb.exe to access internet? Got 10049 error from Proxy SOCKS5 127.0.0.1 via Virtual Box host-only network.
Related
I'm trying to set up a personal cloud server on a Surface Pro, but I'm running into a networking issue that has me completely stumped.
My setup looks like this: I've installed a Nextcloud server on a VMWare virtual machine that's running Ubuntu 16.04, and I have it configured to use NAT so the virtual machine shares a fixed ip address with the host machine. I've forwarded ports 80, 443, etc. on the host machine's NAT device so requests go to the virtual machine. Additionally I've configured my router to have a static ip address, and I've forwarded all the relevant ports to the Surface Pro on my router.
So the trouble is that I can't connect to my server from my browser. HOWEVER, I am able to ping my server, I can SSH in to both the virtual machine and the host machine from the internet, and I am able to access the server in my browser from any computer that's connected to LAN, no problem.
This all sounds like it could be a firewall issue to me (maybe port 80 is blocked on the host machine for some reason??) but the fact that I have no trouble accessing the server from LAN is confusing the issue, and also deactivating the firewall on the host machine doesn't solve the issue.
Any thoughts?
I solved the problem! It turns out the NAT device was improperly configured to use its own DHCP service rather than using the local DHCP service. Basically it was assigning a LAN IP address 169.254.72.176 to the virtual machine, while everything else was configured to expect that the virtual machine's IP address was fixed at 192.168.34.43.
I'm running Windows Server 2012 w/ vmWare Workstation. I've built a GitLab VM on Centos 7 that's totally setup and accessible on my local network. It's configured using Bridged Mode so it has it's own IP from the DHCP Server.
I use No-IP to connect to my Network externally which has been working great for several years now. I have port-forwarding setup within my router to forward traffic for the GitLab webUI to the GitLab VM, but it's not accessible externally. I even tried setting up the port forwarding to direct the traffic to the Windows Server and then setup internal port forwarding w/ netsh on the Windows Server to forward the traffic to the GitLab VM, making sure I opened the port on the Windows Firewall (even tried disabling it), but I still can't get to the GitLab VM externally. AFAIK running a VM w/ a Bridged adapter should essentially be like it is just another physical machine on the network.
Now, I am running IIS on the Windows Server, but when I specify a specific port using my public No-IP Domain, the router should detect the traffic on that port and forward it according to the rules that I have setup, correct? IIS shouldn't be interfering with any traffic on other ports with the external Domain.
I'm totally stumped on this on and searching around the web really hasn't helped much.
So it turns out that I did everything 100% correctly with setting up port forwarding right to the IP of the VM, but my workplace blocks just about every port except for 80 and 443. Tested connectivity from an AWS box and everything is accessible exactly as designed.
Now I just feel like an idiot, but hey, I figured it out.
I've been searching around and found no similar issues have been asked.
My desktop (windows 7) is in LAN, has IP (192.168.3.121).
I installed vmware (windows 7), using NAT connection (172.168.174.128). The guest is able to access internet without problem.
In guest, if I "ping 192.168.3.121", this will be ok.
If I "ping 192.168.3.xxx", will also be ok.
If I "ping 192.168.174.2" (DNS), this will be ok.
If I "ping 192.168.174.1", can't ping.
Note my host Vmnet8's ip is indeed 192.168.174.1. Ping from host also doesn't work.
From host:
"ping 192.168.174.128" (guest IP), does not work
"ping 192.168.174.2", does not work
Both host/guest windows are installed without any other "security/defender/firewall" related softwares.
Anywhere can go wrong?
Thanks.
If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host, or anywhere else for that matter, without configuring port forwarding for that virtual NAT network.
If you would like to be able to access your VM from your host you can either:
A) Change the mode of the network adapter for the VM to a bridged adapter. This will make the VM act as if it is just another computer on the same network your Desktop is and will be accessible at an IP such as 192.168.3.122
or
B) Add a Host-Only network adapter to the VM. This second NIC will be connected to a network that has no internet access, but is connected to the host and any other VMs on the same host-only network
Also, check the firewall settings to allow inbound ICMP inside the VM.
You mean that you cannot ping to the VMnet8 interface of your physical PC.
Maybe it is not activated.
It should be activated first by issuing the command at the cmd prompt with the admin's privilege.
C:\Windows\system32>netsh interface set interface name="VMware Network Adapter V
Mnet8" admin=ENABLED
I have seen this issue with two different windows 10 machine & two different version of vmware workstation ( 15 & 16).
One way it works is I start the wireshark & under capture options I select on VMWARE8(default for workstation/need to adjust according to your NAT Interface) & than start ping from My Local Machine to NAT IP of the VM .
It takes time but it works. I do not what triggers this .
My initial thought was it's one of the Windows 10 upgrade but with two different version of windows 10 & this old issue resurfaced.
Navigate to "Control Panel\Network and Internet\Network Connections".
Disable and Enable the VMware Network Adapter VMnet8 and try again.
I was having same problem after the latest release of VirtualBox-6.1.6-137129-Win update. "NAT Network" on any of the guest machine was not working. So i downgraded my virtual box version to 6 and works fine with all my VMs but problem remains in Kali Linux.
NAT Network was successful in giving IP to kali machine but Internet was not working. Problem i found was somehow gateway of kali wasn't set. Then i configured both Gateway and DNS manually and it worked for me.
Make sure that you Uncheck the option "Use this Connection only for resources on this network."
Kali manual configuration for IP, DNS and Gateway
I have a VPN (pptpd) server configured and a client connected. In the same machine of VPN server, I have a proxy server (port 3128)(squid) running with authentication enabled. When I use the proxy in my firefox browser it works fine. However, when I conect my notebook to my VPN server I can't navigate using firefox + proxy. Just to remember Proxy server and VPN server running in same machine (a VPS). I'm using UFW firewall.
Is there some tips in configuration files (pptpd or squid) to get this problem fixed?
Best Regards!
use squid's access.log to make sure: squid doesn't receive requests from your notebook; check the routing availability between internal IP network of VPN server and proxy address, it must be accessible (pingable). you may use port address translation (PAT) as a simple fix.
I'm doing this (Chrome Remote Debuggin): https://developers.google.com/chrome-developer-tools/docs/remote-debugging
I'd like to be able to access localhost or any of my vhosts (via apache on my desktop) from my phone so that I can debug a local site.
Is there ANY way to do this?
Thanks so much!
Do I understand correctly that you are running Apache on a workstation and want to connect your phone to a website hosted on it?
Yes, that is possible. The simplest method is to join your phone to the same network (WiFi) as your workstation and connect your phone to http://IP-ADDRESS-OF-WORKSTATION. Then use the Remote Debugging as usual.
Alternatively, you need to configure your WiFi router to enable port forwarding. The basic idea is your WiFi router controls traffic between your private home network (where your workstation is) and the public Internet (where your phone is), and port forwarding allows inbound traffic from the Internet to be routed into your private network.
Here's the configuration page for my WiFi router. My workstation's private IP address is 192.168.1.5 and I'm running Apache on the default port 80. If my public IP address was 8.8.8.8 then I would enter http://8.8.8.8:3000 in my phone's browser, and the router would redirect the request to my workstation at 192.168.1.5:80.
In either setup, you'll need to find your workstation's private IP address (e.g., use "Open Network Preferences" from your WiFi status icon on Mac OS X). You can find your WiFi router's public IP address by just googling "my IP address" from your workstation.
Obviously the first method (placing your phone and workstation on the same network) is quite a bit simpler. Port forwarding can be tricky to debug, and the configuration is slightly different for every router. Do post follow-up questions if you get stuck somewhere.