Opened 11 years ago
Last modified 9 years ago
#11978 new defect
Dup ping and not network connectivity while bridged on WIFI
Reported by: | Devon | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 4.2.16 |
Keywords: | ping dup! bridged | Cc: | |
Guest type: | all | Host type: | Linux |
Description (last modified by )
Good day all, I am running Fedora 19 x64. Using the same laptop for couple of years now and longer for Virtualbox. During the last upgrade I started having connectivity issues on some machines. Further investigation found that only machines that were bridged on the WIFI was affected. Let me know if you want any configuration files or anything at all. Thanks, Devon
[devon@fisc-dcj-rhw ~]$ ping google.com PING google.com (74.125.229.227) 56(84) bytes of data. 64 bytes from 74.125.229.227: icmp_seq=1 ttl=56 time=15.5 ms 64 bytes from 74.125.229.227: icmp_seq=1 ttl=55 time=15.6 ms (DUP!) 64 bytes from 74.125.229.227: icmp_seq=2 ttl=56 time=18.6 ms 64 bytes from 74.125.229.227: icmp_seq=2 ttl=55 time=18.7 ms (DUP!) 64 bytes from 74.125.229.227: icmp_seq=3 ttl=56 time=17.7 ms 64 bytes from 74.125.229.227: icmp_seq=3 ttl=55 time=17.8 ms (DUP!) 64 bytes from 74.125.229.227: icmp_seq=4 ttl=56 time=83.2 ms 64 bytes from 74.125.229.227: icmp_seq=4 ttl=55 time=83.3 ms (DUP!) 64 bytes from 74.125.229.227: icmp_seq=5 ttl=56 time=103 ms 64 bytes from 74.125.229.227: icmp_seq=5 ttl=55 time=103 ms (DUP!)
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 9 years ago
Description: | modified (diff) |
---|
Recent 4.3 versions had a number of fixes for bridging to wifi. Do you still see the problem with 4.3.26?
If you still do, please provide packet captures both from the host and from the guest.
comment:3 by , 9 years ago
On Centos 7.2
Have seen these symptoms when a virbr0 interface is present on the host.
Removing the virbr0 interface stopped these symptoms for me.
# virsh net-destroy default
# virsh net-undefine default
# service libvirtd restart
more details here : http://www.cyberciti.biz/faq/linux-kvm-disable-virbr0-nat-interface/
Just checking in. This is still a problem and I am seeing a lot of other people on the internet are discussing the issue. Any word on a fix or can I provide any files to help trouble shoot the problem. Thanks, Devon