Random Lost Packets When Pinging Through Different Subnet

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Random Lost Packets When Pinging Through Different Subnet

rohanrimando
I set up several VMs via Vagrant.

    # Machine
    config.vm.box = "ubuntu/xenial64"
    config.vm.provider "virtualbox" do |vb|
        vb.memory = "2048"
        vb.cpus = "2"
    end

    # Networking
    config.vm.hostname = "domain.com"
    config.vm.network "public_network", ip: "10.10.2.29", bridge: "p1p1"

    # default router
    config.vm.provision "shell",
    run: "always",
    inline: "route add default gw 10.10.2.1"

Now the vagrants can ping each other without packet loss because they are on the same subnet, but when its going through the switch from my machine(10.10.13.XX) there is about 3-10% packet loss. Weirdly enough I can start a screen instance and ping the default gateway continuously so that the loss is negated. I am not a network administrator so I am not sure if there is anything I can do or if I missed something, can someone help?

Thanks!




--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0c904570-2aec-4fa0-a99d-ca9889f46d5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Random Lost Packets When Pinging Through Different Subnet

Alvaro Miranda Aguilera
hello

Can you do vagrant halt, then turn the VM on using the Virtualbox Gui and try the pings from inside?

I don't think this is a Vagrant issue..

From the VM, whats the output of route -n

other option is from virtualbox gui, power the VM off, and check settings of the 2nd network card and test different network cards

Inline image 1

perhaps there is one that runs better.

Alvaro.

On Fri, Nov 24, 2017 at 6:54 AM, <[hidden email]> wrote:
I set up several VMs via Vagrant.

    # Machine
    config.vm.box = "ubuntu/xenial64"
    config.vm.provider "virtualbox" do |vb|
        vb.memory = "2048"
        vb.cpus = "2"
    end

    # Networking
    config.vm.hostname = "domain.com"
    config.vm.network "public_network", ip: "10.10.2.29", bridge: "p1p1"

    # default router
    config.vm.provision "shell",
    run: "always",
    inline: "route add default gw 10.10.2.1"

Now the vagrants can ping each other without packet loss because they are on the same subnet, but when its going through the switch from my machine(10.10.13.XX) there is about 3-10% packet loss. Weirdly enough I can start a screen instance and ping the default gateway continuously so that the loss is negated. I am not a network administrator so I am not sure if there is anything I can do or if I missed something, can someone help?

Thanks!




--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0c904570-2aec-4fa0-a99d-ca9889f46d5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyKXp2n%2BNNa6%3D9imfpEwc8XyJXOsani3doMtkNm%3DSzTPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Random Lost Packets When Pinging Through Different Subnet

rohanrimando
In reply to this post by rohanrimando
Hi,

I am afraid I have limited access to the Ubuntu GUI. Here is what you asked for.

ubuntu@xxx:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.10.2.1       0.0.0.0         UG    0      0        0 enp0s8
0.0.0.0         10.0.2.2        0.0.0.0         UG    0      0        0 enp0s3
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0        0 enp0s3
10.10.2.0       0.0.0.0         255.255.255.0   U     0      0        0 enp0s8

Also here is network config of the VM

ubuntu@xxx:~$ ifconfig
enp0s3    Link encap:Ethernet  HWaddr 02:1f:97:0f:e2:73  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::1f:97ff:fe0f:e273/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45279 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5660 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:62211543 (62.2 MB)  TX bytes:475866 (475.8 KB)

enp0s8    Link encap:Ethernet  HWaddr d0:a4:ea:c9:11:21  
          inet addr:10.10.2.23  Bcast:10.10.2.255  Mask:255.255.255.0
          inet6 addr: fe80::d2a4:eaff:fec9:1121/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:542522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:467181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:92578333 (92.5 MB)  TX bytes:184305414 (184.3 MB)

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:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


TYIA

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9c827c4f-e082-4930-aab8-5c534358f06f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Random Lost Packets When Pinging Through Different Subnet

Alvaro Miranda Aguilera
Hello

Virtualbox gui

If this runs in your computer, is opening Virtualbox.

Alvaro

On Fri, Nov 24, 2017 at 9:32 AM, <[hidden email]> wrote:
Hi,

I am afraid I have limited access to the Ubuntu GUI. Here is what you asked for.

ubuntu@xxx:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.10.2.1       0.0.0.0         UG    0      0        0 enp0s8
0.0.0.0         10.0.2.2        0.0.0.0         UG    0      0        0 enp0s3
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0        0 enp0s3
10.10.2.0       0.0.0.0         255.255.255.0   U     0      0        0 enp0s8

Also here is network config of the VM

ubuntu@xxx:~$ ifconfig
enp0s3    Link encap:Ethernet  HWaddr 02:1f:97:0f:e2:73  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::1f:97ff:fe0f:e273/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45279 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5660 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:62211543 (62.2 MB)  TX bytes:475866 (475.8 KB)

enp0s8    Link encap:Ethernet  HWaddr d0:a4:ea:c9:11:21  
          inet addr:10.10.2.23  Bcast:10.10.2.255  Mask:255.255.255.0
          inet6 addr: fe80::d2a4:eaff:fec9:1121/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:542522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:467181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:92578333 (92.5 MB)  TX bytes:184305414 (184.3 MB)

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:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


TYIA

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9c827c4f-e082-4930-aab8-5c534358f06f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezbzM3M24N6V8T7Hnz6%3DgWANHQGd_%3D1r9MJvimEVf8y8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.