search for: icmp_req

...5535 bytes As soon as I generate traffic from inside the domU to the outside world over this interface, traffic in both directions starts to flow: $ ping 10.140.36.2 (as seen from the problematic domU to the outside) PING 10.140.36.2 (10.140.36.2) 56(84) bytes of data. 64 bytes from 10.140.36.2: icmp_req=1 ttl=64 time=1008 ms 64 bytes from 10.140.36.2: icmp_req=2 ttl=64 time=0.274 ms 64 bytes from 10.140.36.2: icmp_req=3 ttl=64 time=0.205 ms 64 bytes from 10.140.36.2: icmp_req=4 ttl=64 time=0.218 ms 64 bytes from 10.140.36.2: icmp_req=5 ttl=64 time=0.182 ms 64 bytes from 10.140.36.2: icmp_req=6 ttl...

...expected. For the test, I used Fedora 17 for both host and guest, using kernel 3.5.2-3.fc17.86_64. Pinging an external server on the LAN from the host, using a gigabit interface, the results are: # ping -c 10 172.16.1.1 PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data. 64 bytes from 172.16.1.1: icmp_req=1 ttl=64 time=0.109 ms 64 bytes from 172.16.1.1: icmp_req=2 ttl=64 time=0.131 ms 64 bytes from 172.16.1.1: icmp_req=3 ttl=64 time=0.145 ms 64 bytes from 172.16.1.1: icmp_req=4 ttl=64 time=0.116 ms 64 bytes from 172.16.1.1: icmp_req=5 ttl=64 time=0.110 ms 64 bytes from 172.16.1.1: icmp_req=6 ttl=64...

...expected. For the test, I used Fedora 17 for both host and guest, using kernel 3.5.2-3.fc17.86_64. Pinging an external server on the LAN from the host, using a gigabit interface, the results are: # ping -c 10 172.16.1.1 PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data. 64 bytes from 172.16.1.1: icmp_req=1 ttl=64 time=0.109 ms 64 bytes from 172.16.1.1: icmp_req=2 ttl=64 time=0.131 ms 64 bytes from 172.16.1.1: icmp_req=3 ttl=64 time=0.145 ms 64 bytes from 172.16.1.1: icmp_req=4 ttl=64 time=0.116 ms 64 bytes from 172.16.1.1: icmp_req=5 ttl=64 time=0.110 ms 64 bytes from 172.16.1.1: icmp_req=6 ttl=64...

...N=VOLENDAM,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=solid-optics,DC=local root at hoorn:/home/newhang# He still founds volendam root at hoorn:/home/newhang# ping volendam PING volendam.solid-optics.local (192.168.10.42) 56(84) bytes of data. 64 bytes from 192.168.10.42: icmp_req=1 ttl=64 time=0.192 ms 64 bytes from 192.168.10.42: icmp_req=2 ttl=64 time=0.228 ms 64 bytes from 192.168.10.42: icmp_req=3 ttl=64 time=0.204 ms ^C64 bytes from 192.168.10.42: icmp_req=4 ttl=64 time=0.295 but not the domain root at hoorn:/home/newhang# ping solid-optics.local ping: unknown host so...

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

...0 \ / macvtap0 bond0 --- vlan222 eth1 / \ macvtap1 So I've got two guests, let's say A and B. When I try to ping B from A, it works : # ping -s 3000 -c 5 78.109.95.11 PING 78.109.95.11 (78.109.95.11) 3000(3028) bytes of data. 3008 bytes from 78.109.95.11: icmp_req=1 ttl=64 time=0.065 ms 3008 bytes from 78.109.95.11: icmp_req=2 ttl=64 time=2.19 ms 3008 bytes from 78.109.95.11: icmp_req=3 ttl=64 time=1.43 ms --- 78.109.95.11 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.065/0.960/2.197/0.760 ms Bu...

Hello everybody. I'm using Rstudio in LMDE (64 bits) with xfce desktop. When I'm connecting , I don't have any problem to start Rstudio , but when I am not connecting Rstudio don't start. Any idea? In rsession-user.log I get 29 Nov 2012 23:07:50 [rsession-jose] ERROR asio.netdb error 1 (Host not found (authoritative)); OCCURRED AT: core::Error

...3-45d5-b10c-0381d258d3e7 State: Probe Sent to Peer (Connected) gluster> quit 2) System I am trying to probe, is pingable from the host... [root at llm65 glusterfs]# ping llm19.in.ibm.com PING llm19.in.ibm.com (9.124.111.25) 56(84) bytes of data. 64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=1 ttl=64 time=0.133 ms 64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=2 ttl=64 time=0.124 ms 3) The system I am trying to probe, also has the gluster service running... [root at llm19 ~]# ps -ef| grep gluster root 31514 1 0 23:29 ? 00:00:01 /usr/sbin/glusterd -p /var/r...

...4) I add the route: route add -net 192.168.236.0 netmask 255.255.255.0 gw 192.168.1.100 dev eth0 Since this moment i can ping or access (ssh/http) another CentOS machine in the 236 network ping 192.168.236.74 PING 192.168.236.74 (192.168.236.74) 56(84) bytes of data. 64 bytes from 192.168.236.74: icmp_req=1 ttl=64 time=0.281 ms But can't access or ping other machines (NOT Linux ones), ie, printers, Win servers, etc... Also tried adding: route add 192.168.1.100 eth0 before the route add -net, but no efect. This fails even if i flush IPTables. In the CentOS box that replies, i did nothing, i...

Hello. I have this settings of imapc: # doveconf -a | grep imapc imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_ca_dir = imapc_ssl_verify = yes imapc_user = %u and try to sync mailbox on old server and new one: $ dsync -o imapc_user="user at example.org"

...TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:168 (168.0 B) TX bytes:0 (0.0 B) root at web-services:/etc/tinc/webservices# ping 192.168.98.1 PING 192.168.98.1 (192.168.98.1) 56(84) bytes of data. 64 bytes from 192.168.98.1: icmp_req=1 ttl=64 time=0.058 ms 64 bytes from 192.168.98.1: icmp_req=2 ttl=64 time=0.038 ms ^C --- 192.168.98.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.038/0.048/0.058/0.010 ms root at web-services:/etc/tinc/webservices# ping 192.168.98.2 PI...

Hey, Due to a security issue in the moinmoin wiki software, the FreeBSD wiki will be offline for a bit. I do not yet know if the issue actually has been exploited in the FreeBSD wiki (haven't had the time yet to examine it), but I took the wiki down just in case. Note that even if the software was compromised, it was considered untrusted from the start and as such heavily sandboxed

...ups) All memory is saved PROF: resumed at 1294213417.385560 ... If I overlord3:~$ sudo xm destroy lindi-exp1 then the domU is unpaused on overlord1 and works just great: overlord3:~$ ping lindi-exp1 PING lindi-exp1.lan (10.7.6.20) 56(84) bytes of data. 64 bytes from lindi-exp1.lan (10.7.6.20): icmp_req=1 ttl=64 time=2.60 ms ^C --- lindi-exp1.lan ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.601/2.601/2.601/0.000 ms Have you considered shipping the remus executable so that people could at least experiment with remus even if it is not con...

...ups) All memory is saved PROF: resumed at 1294213417.385560 ... If I overlord3:~$ sudo xm destroy lindi-exp1 then the domU is unpaused on overlord1 and works just great: overlord3:~$ ping lindi-exp1 PING lindi-exp1.lan (10.7.6.20) 56(84) bytes of data. 64 bytes from lindi-exp1.lan (10.7.6.20): icmp_req=1 ttl=64 time=2.60 ms ^C --- lindi-exp1.lan ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.601/2.601/2.601/0.000 ms Have you considered shipping the remus executable so that people could at least experiment with remus even if it is not con...

...> # nslookup dc1 > Server: 192.168.17.4 > Address: 192.168.17.4#53 > > Name: dc1.ads.ccenter.lan > Address: 192.168.17.4 > > # ping dc1 -c 1 > PING dc1.ads.ccenter.lan (192.168.17.4) 56(84) bytes of data. > 64 bytes from dc1.ccenter.lan (192.168.17.4): icmp_req=1 ttl=64 time=0.487 ms > > --- dc1.ads.ccenter.lan ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.487/0.487/0.487/0.000 ms > > root at userl:~# wbinfo -t > checking the trust secret for domain CCENTER via RPC calls s...

...ttle.VirtAPI.testing.VirtAPITesting.main(VirtAPITesting.java:29) ... 5 more But I know there is a route to the host as virsh could get there. Sanity check: ping works fine too. [jdrews at flynx ~]$ ping 192.168.1.23 PING 192.168.1.23 (192.168.1.23) 56(84) bytes of data. 64 bytes from 192.168.1.23: icmp_req=1 ttl=64 time=1.58 ms Here is the code I'm running in the VirtAPITesting.jar. For the most part it's a direct copy of the example at the end of the libvirt java page: http://libvirt.org/java.html package com.jdrews.VirtAPI.testing; import org.libvirt.*; public class VirtAPITesting {...

...192.168.17.4 >> Address: 192.168.17.4#53 >> >> Name: dc1.ads.ccenter.lan >> Address: 192.168.17.4 >> >> # ping dc1 -c 1 >> PING dc1.ads.ccenter.lan (192.168.17.4) 56(84) bytes of data. >> 64 bytes from dc1.ccenter.lan (192.168.17.4): icmp_req=1 ttl=64 time=0.487 ms >> >> --- dc1.ads.ccenter.lan ping statistics --- >> 1 packets transmitted, 1 received, 0% packet loss, time 0ms >> rtt min/avg/max/mdev = 0.487/0.487/0.487/0.000 ms >> >> root at userl:~# wbinfo -t >> checking the trust secret for do...

Hi, My Samba 4.1.x server is connected to two networks, one in the 192.168.* range (wired) and one in the 10.* range (wifi). The clients on either network normally cannot reach each other. I noticed Samba hands out (eg: for dcname.company.net) it's IP's from both ranges to clients on both sides. So the 192.168.* clients get two A records: 192.168.1.1 & 10.0.0.2. I noticed that,

...t; Address: 192.168.17.4#53 >>> >>> Name: dc1.ads.ccenter.lan >>> Address: 192.168.17.4 >>> >>> # ping dc1 -c 1 >>> PING dc1.ads.ccenter.lan (192.168.17.4) 56(84) bytes of data. >>> 64 bytes from dc1.ccenter.lan (192.168.17.4): icmp_req=1 ttl=64 time=0.487 ms >>> >>> --- dc1.ads.ccenter.lan ping statistics --- >>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms >>> rtt min/avg/max/mdev = 0.487/0.487/0.487/0.000 ms >>> >>> root at userl:~# wbinfo -t >>> chec...

...has SRV record 0 100 389 dc1.ads.ccenter.lan. # nslookup dc1 Server: 192.168.17.4 Address: 192.168.17.4#53 Name: dc1.ads.ccenter.lan Address: 192.168.17.4 # ping dc1 -c 1 PING dc1.ads.ccenter.lan (192.168.17.4) 56(84) bytes of data. 64 bytes from dc1.ccenter.lan (192.168.17.4): icmp_req=1 ttl=64 time=0.487 ms --- dc1.ads.ccenter.lan ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.487/0.487/0.487/0.000 ms root at userl:~# wbinfo -t checking the trust secret for domain CCENTER via RPC calls succeeded root at userl:~# wbinfo...