I am trying to deploy my Shiny App on a Virtual Machine (CentOS 6.7). I have configured a bridged connection (I think I did it correctly) for the Virtual Machine, and I have my Static IP Address for the web application. The sample application works on localhost:3838.
I am behind a corporate proxy, so I am using a proxy to connect to the internet. The proxy is set in http_proxy. I can also connect to the internet successfully on the Virtual Machine.
When I try to access <my_VM_static_IP_Address>:3838 the website does not connect.
I can ping both the host IP address and the guest (static) IP address successfully from another PC that is connected to the network.
br0 Link encap:Ethernet HWaddr 70:F3:95:03:B5:CC
inet addr:<My Static IP Address> Bcast:<my_broadcast_address> Mask:255.255.254.0
inet6 addr: fe80::72f3:95ff:fe03:b5cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:69753 errors:0 dropped:0 overruns:0 frame:0
TX packets:9698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34003791 (32.4 MiB) TX bytes:843817 (824.0 KiB)
eth0 Link encap:Ethernet HWaddr 70:F3:95:03:B5:CC
inet6 addr: fe80::72f3:95ff:fe03:b5cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:130187 errors:0 dropped:0 overruns:0 frame:0
TX packets:9704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45704171 (43.5 MiB) TX bytes:845299 (825.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:439 errors:0 dropped:0 overruns:0 frame:0
TX packets:439 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:814679 (795.5 KiB) TX bytes:814679 (795.5 KiB)
My host default gateway and subnet mask are the same on the VM Guest and the host.
Any support is greatly appreciated!
Investigate whether a firewall on the host prevents port 3838 from being accessible from the rest of the network. It seems like you have a Windows host, correct?
A quick and easy way to check is to telnet to that port on your guest OS's IP from another machine on the network. If the connection is refused with an error, you know something is blocking the port. A blank screen means an open port.
From some other machine on the network, telnet to your guest VM's IP on port 3838. A blocked port will cause telnet to quickly return an error. If the telnet command sits with a blank screen, you have an open port.
Related
I created a vagrant environment where there is 2 VM's in the private network , i need this because i want them to be able to communicate with each other like application server and database server.So here is my vagrantfile:
Vagrant.configure("2") do |config|
config.vm.define "mac1" do |mac1|
mac1.vm.box = "kaorimatz/centos-6.8-x86_64"
mac1.vm.network :private_network, ip: "192.168.56.101"
mac1.vm.network "forwarded_port", guest: 80, host: 8080
end
config.vm.define "mac2" do |mac2|
mac2.vm.box = "fully-functional"
mac2.vm.network :private_network, ip: "192.168.56.102"
mac2.vm.network "forwarded_port", guest: 80, host: 8081
mac2.vm.synced_folder "./piwik", "/var/www/html"
end
end
now lets say i want to reach only mac2 VM via browser.but i am putting the url like http://localhost:8081 but it says site is not reachable.In that machine when i run the command ifconfig here is the result:
eth0 Link encap:Ethernet HWaddr 08:00:27:AF:D5:5C
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feaf:d55c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2779 errors:0 dropped:0 overruns:0 frame:0
TX packets:1504 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:221177 (215.9 KiB) TX bytes:165269 (161.3 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:4E:48:A7
inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe4e:48a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1114 (1.0 KiB) TX bytes:2408 (2.3 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I also added that lines to apache conf :
<VirtualHost *:80>
ServerName mac2.com
DocumentRoot /var/www/html
</VirtualHost>
And i can also listen to the port 8081 like telnet localhost 8081
but i couldnt reach the webserver by any means however i can try.Pls help thank you in advance.
I had the same thing with two vagrant instances using the "kaorimatz/centos-6.8-x86_64" box (even after being fully updated during provisioning):
When I used a different box, I was then able to forward ports. The only change I made was with the Vagrantfile config.vm.box value. I suspect it's a "kaorimatz/centos-6.8-x86_64" issue but I'm not going to investigate the kaorimatz box as the alternative box worked.
(I used the "bmcgonigle/centos68" box.)
#config.vm.box = "kaorimatz/centos-6.8-x86_64"
config.vm.box = "bmcgonigle/centos68"
I had tried the same thing with the private network but had no success with it. I got suspicious of the kaorimatz box when I noticed that I had other vagrant dev configs that forwarded ports with no issues. Best of luck!
I have configured a NAT connection on Centos 6.5 VM and it seems it does not connect to my NIC.
service network restart returns
Bringing up interface eth1: Error: No suitable device found: no device found for connection 'eth1'
ifconfig -a is shown below
eth2 Link encap:Ethernet HWaddr 00:0C:29:90:6C:31
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX Packets:90 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Base address:0x2024
Well your ifconfig states that you have eth2 device. It is my assumption that you originally had it bridged and changed into NAT.
In /etc/sysconfig/network-scripts/
Create file named ifcfg-eth2
And fill it so it would be configured automatically by DHPC server:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
I am not sure if it should have rights to be executed (chmod +x).
I have a freedompop Ubee stick that I would like to connect to my beaglebone black (running angstrom with 3.2.0-54-generic kernel). After solving some issues with hotswapping (it's not possible apparently), I am seeing the the interface in using ifconfig. But when I try bringing it up nothing happens:
root#beaglebone:~# ifconfig eth1 up
root#beaglebone:~# udhcpc eth1
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Something also strange is that the interface initially has an address:
root#beaglebone:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1D:88:53:2F:52
inet addr:192.168.14.2 Bcast:192.168.14.255 Mask:255.255.255.0
inet6 addr: fe80::21d:88ff:fe53:2f52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2542 (2.4 KiB) TX bytes:9062 (8.8 KiB)
But a few moments ( < 1 minute) later, if I run the same command, eth1 no longer has an address, bcast, etc:
root#beaglebone:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1D:88:53:2F:52
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2730 (2.6 KiB) TX bytes:9240 (9.0 KiB)
Under no circumstance (before or after address is stripped in ifconfig) can I ever ping something.
I have tried re-assigning the address, mask, etc, but nothing helps. Bring the interface up or down does not help. I tried manually creating an interfaces file and that didn't help either.
To solve this problem, I had to:
Add an inet dhcp interface in /etc/network/interfaces:
iface eth1 inet dhcp
Add the freedompop as a nameserver in resolve.conf
nameserver 192.168.14.1
Bring up the interface
ifup eth1
I am using windows, and I'm also running an ubuntu server on virtual box. I've SSH'd into the guest machine countless times in the recent past when the guest machine was connected to a network using IPv4 addresses. This worked back when I was at home and at work. Right now, I'm connected to the university network. Here's the result from ifconfig when executed in my VM.
eth0 Link encap:Ethernet HWaddr 08:00:27:ae:e4:a0
inet6 addr: fe80::a00:27ff:feae:e4a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65404 errors:0 dropped:0 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7588239 (7.5 MB) TX bytes:10610 (10.6 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1296 (1.2 KB) TX bytes:1296 (1.2 KB)
I did some research, and found this post on SO.
IPv6 link-local address format
So I ran netsh interface ipv6 show address on my host machine and this is my vbox network info
Interface 208: VirtualBox Host-Only Network
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite fe80::f8cd:e410:b1b1:c081%208
I then tried pinging the address, and it was successful. I then tried to SSH into the server, using the following command
ssh -6 fe80::f8cd:e410:b1b1:c081%208
And I got this error
"no address associated with name"
I don't understand why I'm getting this error - I've ssh'd into machines by specifying their ipv4 addresses before, and I've never gotten this error before. Could anyone tell me what I might be doing wrong?
Thanks for the help!
Try specifying the interface to the ssh client. however ssh does not have a switch for that, you have to use this syntax:
ipv6%eth1
fe80::f8cd:e410:b1b1:c081%eth0
How do I print which packets are dropped by by the interface ???
I have an interface wherein RX packets are dropped , see below :
eth0 Link encap:Ethernet HWaddr DE:AD:BE:EF:42:46
inet addr:192.168.122.86 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::dcad:beff:feef:4246/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
**RX packets:10963521 errors:0 dropped:1006 overruns:0 frame:0**
TX packets:6221974 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3108701252 (2.8 GiB) TX bytes:3842229777 (3.5 GiB)
Interrupt:10 Base address:0xe000
In Windows you can enable dropped packets logging:
Step 1. Change Windows Firewall configuration:
auditpol.exe /set /SubCategory:"Filtering Platform Packet Drop" /failure:enable
Step 2. Restart firewall service
net stop MPSSVC
net start MPSSVC
More info on http://technet.microsoft.com/en-us/library/cc754714(v=ws.10).aspx.