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.
Related
unable to create mgmt network on openstack.
Tried creating "mgmt" network on openstack (OCATA version) as per the given instruction in the link
(Replaced to ocata version command keywords)
configure openstack for OSM
I got the following response, No much info about the error
stack#kanine-openstack:~/devstack/accrc/admin$ openstack network create --provider-network-type VLAN --provider-physical-network physnet_enp0s8 --provider-segment 7777 --share mgmt
Ignoring domain related config project_domain_id because identity API version is 2.0
Ignoring domain related config user_domain_id because identity API version is 2.0
Ignoring domain related config project_domain_id because identity API version is 2.0
Ignoring domain related config user_domain_id because identity API version is 2.0
Ignoring domain related config project_domain_id because identity API version is 2.0
Ignoring domain related config user_domain_id because identity API version is 2.0
Ignoring domain related config project_domain_id because identity API version is 2.0
Ignoring domain related config user_domain_id because identity API version is 2.0
Error while executing command: Bad Request
I installed ubuntu on virtual box, Please find the interface
~$ ifconfig
br-ex Link encap:Ethernet HWaddr 26:f9:df:8b:bb:49
inet addr:172.24.4.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: 2001:db8::2/64 Scope:Global
inet6 addr: fe80::24f9:dfff:fe8b:bb49/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:972 (972.0 B) TX bytes:10796 (10.7 KB)
enp0s3 Link encap:Ethernet HWaddr 08:00:27:76:8f:15
inet addr:10.0.15.112 Bcast:10.0.15.255 Mask:255.255.255.0
inet6 addr: fe80::5bf2:65ab:b422:817b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48615 errors:0 dropped:1 overruns:0 frame:0
TX packets:43919 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6642829 (6.6 MB) TX bytes:10149498 (10.1 MB)
enp0s8 Link encap:Ethernet HWaddr 08:00:27:f4:3d:0f
inet addr:10.0.10.5 Bcast:10.0.10.255 Mask:255.255.255.0
inet6 addr: fe80::2a7:9404:baf9:ea12/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23780 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2539893 (2.5 MB) TX bytes:10510 (10.5 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:65536 Metric:1
RX packets:320077 errors:0 dropped:0 overruns:0 frame:0
TX packets:320077 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:164795161 (164.7 MB) TX bytes:164795161 (164.7 MB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Please help me on creating the mgmt network.
This error messages causes from different API version at the keystone.
If your API version is 2? it's not correct, Domain feature is as of Version 3.
so you change your auth URL as follows
export OS_AUTH_URL=http://YOUR_KEYSTONE_IP:5000/v3
And neutron network is not appear as the Ethernet device.
You check the current network list as follow command,
$ openstack network list
And share type network is required Admin authorization.
I'm developing a WordPress site with Vagrant box "vccw-team/xenial64", which can be found at vccw.cc. The website was slow with waiting times that average around 5 seconds, did some googling and many people where pointing at Vagrants synced folder wich is slow in combination with Virtualbox. The solution: nfs. Nfs doesn't exist on Windows so that gave rise to the Vagrant plugin winnfsd.
I installed the plugin and changed the Vagrantfile as such:
config.vm.network :private_network, ip: "192.168.33.10"
config.vm.synced_folder _conf['synced_folder'],
_conf['document_root'], :create => "true", :mount_options => ['dmode=755', 'fmode=644'], type: "nfs"
On vagrant up, I receive this message:
==> vccw.dev: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp,dmode=755,fmode=644 192.168.33.1:/D/_projects/Vagrant/vccw/wordpress /var/www/html
Stdout from the command:
Stderr from the command:
mount.nfs: an incorrect mount option was specified
I guess the portion 192.168.33.1:/D/_projects/Vagrant/vccw/wordpress might be wrong because D/_projects/Vagrant/vccw/wordpress exist on the host and not on the guest (192.168.33.1).
Other people managed to get the plugin working. Does anyone know what I'm doing wrong?
Versions:
Vagrant: 2.0.0
vagrant-winnfsd: 1.3.1
Virtualbox: 5.1.26 r117224 (Qt5.6.2)
I enabled DHCP in Vagrantfile like so:
config.vm.network :private_network, ip: "192.168.33.11", type: "dhcp"
But that resulted in the error:
NFS requires a host-only network to be created. Please add a host-only network to the machine (with either DHCP or a static IP) for NFS to work
Then I read in another question on StackOverflow that one can configure a host-only network by using the code below in the Vagrantfile:
config.vm.network :private_network, ip: "192.168.33.11"
config.vm.network :public_network, ip: "192.168.44.12"
config.vm.synced_folder _conf['synced_folder'],
_conf['document_root'], type: "nfs"
I think 192.168.44.0 255.255.255.0 is now the hosted network, derived from ip: "192.168.44.12". It work's now and my WordPress site is faster with a loading time that averages around 3 seconds. I appreciate the improvement but I'll be hawking for other tweaks.
Extra info, the output of ifconfig in the guest:
vagrant#vccw:~$ ifconfig
enp0s3 Link encap:Ethernet HWaddr 08:00:27:a8:df:8b
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fea8:df8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1156 errors:0 dropped:0 overruns:0 frame:0
TX packets:788 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:277602 (277.6 KB) TX bytes:97056 (97.0 KB)
enp0s8 Link encap:Ethernet HWaddr 08:00:27:da:65:a0
inet addr:192.168.33.11 Bcast:192.168.33.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feda:65a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12461 errors:0 dropped:0 overruns:0 frame:0
TX packets:7004 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10059912 (10.0 MB) TX bytes:2671763 (2.6 MB)
enp0s9 Link encap:Ethernet HWaddr 08:00:27:62:47:ec
inet addr:192.168.44.12 Bcast:192.168.44.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe62:47ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:204 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18654 (18.6 KB) TX bytes:648 (648.0 B)
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:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1658 (1.6 KB) TX bytes:1658 (1.6 KB)
I'm new to centos.
When I'm at work I'm able to connect to my centos server from my mac, Now I'm trying to connect from home and I can't.
I've tried pinging google.com and recieved: unknown host google.com .
Maybe it's something with the ip I get from my home router?
here's my /etc/hosts file:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Here's my ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1C:42:B3:AC:2C
inet6 addr: fe80::21c:42ff:feb3:ac2c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:730172 errors:0 dropped:0 overruns:0 frame:0
TX packets:582258 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:642394306 (612.6 MiB) TX bytes:59636955 (56.8 MiB)
eth1 Link encap:Ethernet HWaddr 00:1C:42:19:FB:DC
inet addr:10.37.129.3 Bcast:10.37.129.255 Mask:255.255.255.0
inet6 addr: fdb2:2c26:f4e4:1:21c:42ff:fe19:fbdc/64 Scope:Global
inet6 addr: fe80::21c:42ff:fe19:fbdc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:694184 errors:0 dropped:0 overruns:0 frame:0
TX packets:465777 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:104085044 (99.2 MiB) TX bytes:1662635867 (1.5 GiB)
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:3581071 errors:0 dropped:0 overruns:0 frame:0
TX packets:3581071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3060357993 (2.8 GiB) TX bytes:3060357993 (2.8 GiB)
P.S-
I'm not sure if it matters, but I'm using Nginx server. I can't restart it also.
Please checks your Centos server file
/etc/hosts.allow
It maybe only allowing certain IPs access to the Centos Box
Your work IP maybe in there but your home IP may not
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.
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