Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got a VirtualBox machine whose bridged interface (to eth0) isn't getting traffic in. For example I ping 8.8.8.8. I got outbound traffic, but inbound traffic is not getting here.
I know is also a network problem :S, actually... I also got a really poor performance if I nat ( virtualbox-bridged-adapter-8021q-%3D-%5Bb%5Dridiculous-performance%5B-b%5D-838385/
IE:
Code:
Virtual:
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3007ms
Host:
tcpdump -n host 69.64.x6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
09:32:08.262107 arp who-has 69.64.x7 tell 69.64.xx
09:32:08.262172 arp reply 69.64.x7 is-at 00:30:48:60:73:ca
09:32:08.262511 IP 69.64.x6.51561 > 8.8.8.8.domain: 6235+[|domain]
09:32:08.262525 IP 69.64.x6.51561 > 8.8.8.8.domain: 6235+[|domain]
09:32:08.696706 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 1, length 64
09:32:08.696727 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 1, length 64
09:32:08.749868 arp who-has 69.64.x6 tell 69.64.94.2
09:32:08.750093 arp reply 69.64.x6 is-at 08:00:27:14:c4:af
09:32:08.750098 arp reply 69.64.x6 is-at 08:00:27:14:c4:af
09:32:09.700685 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 2, length 64
09:32:09.700704 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 2, length 64
09:32:10.701303 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 3, length 64
09:32:10.701322 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 3, length 64
09:32:11.701225 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 4, length 64
09:32:11.701242 IP 69.64.x6 > 8.8.8.8: ICMP echo request, id 58955, seq 4, length 64
09:32:13.262163 IP 69.64.x6.51561 > 8.8.8.8.domain: 6235+[|domain]
09:32:13.262180 IP 69.64.x6.51561 > 8.8.8.8.domain: 6235+[|domain]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.