I followed all the steps and installed mitmproxy in my virtual machine and then proceeded to test it.
I opened firefox and used the IP address I got from ifconfig. {inet address}
And it worked!
But when I to do the same for my other laptop or phone{with the ca certificate installed} connected to the same router. It does not connect. The proxy doesn't work.
As you can see it works in my PC where I have the vmware running linux and mitmproxy, but this proxy isn't working for my other machines.
I just changed the 'Network' settings on my vmware to 'bridged'. And everything started working as expected.
Cheers,
Related
I have installed browsersync using command npm install -g browser-sync in windows 10 x64. nodejs version 10.11.0 browsersync version 2.26.3
everything is working fine in desktop. but when i try to access http://192.168.56.1:3000 from mobile device using same wifi, i get "this site can't be reached"
i have installed another tool named dev-ip which returns this in powershell:
[ '192.168.56.1', '192.168.0.120' ]
the ip series 192.168.0.120 used to work fine in my mobile devices.
now, how to use the ip 192.168.0.120 instead of 192.168.56.1 in browsersync globally?
Just specify the host in your configuration that you want the server to run on.
Eg. In you case it would be
host: "192.168.0.120"
You can refer to the link below for more information.
https://www.browsersync.io/docs/options#option-host
Hi, guys. This is how it worked for me:
Source:
windows 10
all firewalls are closed
network access (from windows) to the PC is disabled
external url from gulp 192.168.56.1:3000
proxying local php site from OpenServer
external device - iphone safari/chrome
external (virtual) device - vwware with macos
make sure that Windows Defender firewall monitor in high-risk mode -> rules for incoming connections -> Node.js: Server-side JavaScript is enabled (and other necessary apps)
Solution:
look at what ip address in the home network my PC has (all devices are connected to the same network) - for example 192.168.1.103
in the gulp file I specify it host: "192.168.1.103",
save
checking it out
Important:
for source - external device - iphone safari/chrome - correct url is only 192.168.1.103:3000
for source - external (virtual) device - vwware with macos - correct urls is 192.168.1.103:3000 and 192.168.56.1:3000 both
Visually in pic:
Result:
Checked on all devices, in virtual devices, on the PC itself
browsersync works
the Internet is not lost
there is no address conflict within the network
Hope this will help someone too 🙂
You don't have to change the settings.
run cmd using Administrator
run ipconfig
copy IPv4 address like 192.168.43.52
Now open google on mobile and add http:// at the front and :3000 or :5500 at the back.
like run http://192.168.43.52:3000
I am trying to setup a DocumentDB emulator on my Win7 local, then found out it only supports Windows 10.
then I installed the emulator on Windows10 VirtualBox, I have no problem seeing the Emulator page using localhost.
however, when I try to connect from my Win7 local box to the emulator on Win10 virtualbox, I can't get a connection (either from browser pointing to https://localhost:8081/... or from code).
Is the DocumentDB Emulator only accessible from the machine running it?
i turned off windows firewall on Win10
I ran Emulator on port 443 on Win10
Virtualbox network config: NAT Port forwarding 8081 to 443 (i have similar config for SSH from Win7 to Linux VB that works)
thanks in advance
I had the same problem, this is how I succeeded.
First, install DocumentDBEmulatorCertificate from your VM to the host, as a trusted certificate. Here you can find how to export it.
Then forward a port to 8081 with netsh:
netsh interface portproxy add v4tov4 listenport=64000 connectport=8081 connectaddress=127.0.0.1
I have a windows server running inside a VM and trying to access it from a raspberry pi 3 which is configured to have access to the VM network.
Problem is when I ping the server with its' IP it responds but when I do it with the name (in my case it's nlux807) it throws Unknown Hostname nlux807
How can I resolve it?
I am quite new to Raspbian. Any handy tip will be appreciated.
If the Windows server has a static IP, you can edit the file /etc/hosts on the Raspberry Pi device and add the following line:
192.168.0.99 nlux807 # Actually the IP address of the Windows server
That will make ping nlux807 work.
This is similar to ssh-could-not-resolve-hostname-name-or-service-not-known.
I want to install whm & cpanel in my laptop. I install centOs 6.4 using oracle virtualBox as per instruction/iso in http://www.comunidadhosting.com/t/tutorial-de-como-instalar-cpanel-en-localhost.18879/.
After install it i check IP and it show me 10.0.2.15 . but my main problem is I am not able ping to guest machine from my host. When I ping from my guest to host machine then it's working fine , and host get internet access also.
I use NAT in networking.
Can any body tell me what is the problem and how to solve it ?
You need to check if you have a bridged connection OR a NAT connection with the outside host network. Both should have the same network connection and IP may be same/different.
And, if you have done this, then you need to disable the firewall on the guest-machine side so that your host machine could connect to the VM.
Your ping may then be failing because of getting blocked by the VM's firewall.
I created a ubuntu server on vmware. I am using it as a file server. I can access it if I am connecting through the machine which hosts the virtual machine. I am not able to do it from other machines which are on the same network. Thanks in advance!
First of all make sure in the setting of the virtual machine that it is in Bridged Adaptor type connectivity.
Give a static ip to the virtual machine using
sudo ifconfig eth0 10.0.0.100 netmask 255.255.255.0
the above is an example. You got what I mean.
3.Third, Try pinging the virtual machine with the base machine running the vbox to make sure they are connected.
ping ipaddress-basemachine
4 . Now if everything is working fine from there then connect with this virtual machine with other base machine using Remote Desktop Viewer or any other similar application.
Specify, the ip-address of the vbox and username, password. It will be able to connect with it now.
5 . If it still is not able to then try to check the firewall rules on both the virtual box machine and the base machine running the vbox using the command
iptables -L