Re: Odd ping problem

2017-03-02 Thread Gary Stainburn
On Monday 27 February 2017 17:50:24 Rick Stevens wrote: > That would clean it up, yes. What I recommended are settings we use > when we set up clusters of servers on load balancers using DSR (direct > server return). The main problem you had is that you had two different > physical NICs on the same

Re: Odd ping problem

2017-03-01 Thread Cameron Simpson
On 24Feb2017 10:19, Gary Stainburn wrote: Here's an odd one for you. I have a Fedora 19 box - GROUCHO - that is the DNS/DHCP/email/.. server for one of my LANs On there I have a home-grown network status monitor which pings a list of IP's and monitors the state, reporting anything that goes

Re: Odd ping problem

2017-02-27 Thread Rick Stevens
On 02/27/2017 08:01 AM, Gary Stainburn wrote: > On Friday 24 February 2017 18:51:54 Rick Stevens wrote: >> The most common issue with this sort of thing is ARP and/or route >> confusion. You have a machine with two interfaces on the same network. >> Try doing this as root on zeppo (the machine with

Re: Odd ping problem

2017-02-27 Thread Gary Stainburn
On Friday 24 February 2017 18:51:54 Rick Stevens wrote: > The most common issue with this sort of thing is ARP and/or route > confusion. You have a machine with two interfaces on the same network. > Try doing this as root on zeppo (the machine with two interfaces): > > echo "1" >/proc/sys/net

Re: Odd ping problem

2017-02-24 Thread Rick Stevens
On 02/24/2017 02:19 AM, Gary Stainburn wrote: > Here's an odd one for you. > > I have a Fedora 19 box - GROUCHO - that is the DNS/DHCP/email/.. server > for one of my LANs > > On there I have a home-grown network status monitor which pings a list of > IP's > and monitors the state, reporti

Odd ping problem

2017-02-24 Thread Gary Stainburn
Here's an odd one for you. I have a Fedora 19 box - GROUCHO - that is the DNS/DHCP/email/.. server for one of my LANs On there I have a home-grown network status monitor which pings a list of IP's and monitors the state, reporting anything that goes missing. The IP address of this host is

Re: ping problem

2012-06-26 Thread Eddie G.O'Connor Jr-I
On 06/25/2012 03:07 AM, JD wrote: On 06/25/2012 12:57 AM, Ed Greshko wrote: getcap /bin/ping $ getcap /bin/ping $ But how could this happen?? That was going to be my question as well! How could something like this change?...Unless somehow with an upgrade or update these files are re-config

Re: ping problem

2012-06-25 Thread JD
On 06/25/2012 02:14 PM, Ed Greshko wrote: On 06/26/2012 01:32 AM, JD wrote: On 06/25/2012 12:59 AM, Ed Greshko wrote: On 06/25/2012 02:47 PM, Ed Greshko wrote: Actually.strike all that. Or at least most of it. Need to rethink... OK *NOW* I do have it The "correct" co

Re: ping problem

2012-06-25 Thread Michael Cronenworth
Ed Greshko wrote: > Now all you have to do is, since you've overwritten everything, is to sit > around and > scratch your head and ask. "Was the sha256sum correct before I > reinstalled? Was > that ping command the "real" ping or was it dropped in by nefarious means?". It would have been

Re: ping problem

2012-06-25 Thread Ed Greshko
On 06/26/2012 01:32 AM, JD wrote: > On 06/25/2012 12:59 AM, Ed Greshko wrote: >> On 06/25/2012 02:47 PM, Ed Greshko wrote: >>> Actually.strike all that. Or at least most of it. Need to >>> rethink... >> OK *NOW* I do have it >> >> The "correct" command is "getcap" >> >> roo

Re: ping problem

2012-06-25 Thread JD
On 06/25/2012 12:59 AM, Ed Greshko wrote: On 06/25/2012 02:47 PM, Ed Greshko wrote: Actually.strike all that. Or at least most of it. Need to rethink... OK *NOW* I do have it The "correct" command is "getcap" root@f17 tmp]# getcap /bin/ping /bin/ping = cap_net_raw+ep

Re: ping problem

2012-06-25 Thread JD
On Mon, Jun 25, 2012 at 9:13 AM, Reindl Harald wrote: > > > Am 25.06.2012 17:03, schrieb JD: > > Usually it happens by someone copying the file, or replacing the > file. > > > > [egreshko@meimei ~]$ ll /bin/ping > > -rwxr-xr-x. 1 root root 39344 Nov 10 2011 /bin/ping > > [egreshko

Re: ping problem

2012-06-25 Thread Reindl Harald
Am 25.06.2012 17:03, schrieb JD: > Usually it happens by someone copying the file, or replacing the file. > > [egreshko@meimei ~]$ ll /bin/ping > -rwxr-xr-x. 1 root root 39344 Nov 10 2011 /bin/ping > [egreshko@meimei ~]$ cat /bin/ping | sha256sum > b7eaaa776658fb9fff65dd927c

Re: ping problem

2012-06-25 Thread JD
On Mon, Jun 25, 2012 at 12:57 AM, Ed Greshko wrote: > On 06/25/2012 02:54 PM, JD wrote: > > On 06/25/2012 12:22 AM, Ed Greshko wrote: > >> On 06/25/2012 01:21 PM, JD wrote: > >>> fc16 with latest updates. > >>> > >>> Pinging my gateway: > >>> $ ping 192.168.42.129 > >>> ping: icmp open socket: Op

Re: ping problem

2012-06-25 Thread JD
On Mon, Jun 25, 2012 at 1:16 AM, Ed Greshko wrote: > On 06/25/2012 03:07 PM, JD wrote: > > On 06/25/2012 12:57 AM, Ed Greshko wrote: > >> getcap /bin/ping > > $ getcap /bin/ping > > $ > > > > But how could this happen?? > > > > Usually it happens by someone copying the file, or replacing the file

Re: ping problem

2012-06-25 Thread JD
Running 32bit fc16. On Mon, Jun 25, 2012 at 6:22 AM, Daniel wrote: > On 06/25/2012 05:00 AM, > users-request@lists.**fedoraproject.orgwrote: > >> [egreshko@meimei ~]$ ll /bin/ping >> -rwxr-xr-x. 1 root root 39344 Nov 10 2011 /bin/ping >> [egreshko@meimei ~]$ cat /bin/ping | sha256sum >> b7eaaa

Re: ping problem

2012-06-25 Thread Bill Davidsen
JD wrote: On 06/25/2012 12:22 AM, Ed Greshko wrote: On 06/25/2012 01:21 PM, JD wrote: fc16 with latest updates. Pinging my gateway: $ ping 192.168.42.129 ping: icmp open socket: Operation not permitted Now as root: # ping 192.168.42.129 PING 192.168.42.129 (192.168.42.129) 56(84) bytes of da

Re: ping problem

2012-06-25 Thread Daniel
On 06/25/2012 05:00 AM, users-requ...@lists.fedoraproject.org wrote: [egreshko@meimei ~]$ ll /bin/ping -rwxr-xr-x. 1 root root 39344 Nov 10 2011 /bin/ping [egreshko@meimei ~]$ cat /bin/ping | sha256sum b7eaaa776658fb9fff65dd927cc9480d39a3221129aceaa07d642ef6d9c33e4c - If you've got an i686 ins

Re: ping problem

2012-06-25 Thread Ed Greshko
On 06/25/2012 03:07 PM, JD wrote: > On 06/25/2012 12:57 AM, Ed Greshko wrote: >> getcap /bin/ping > $ getcap /bin/ping > $ > > But how could this happen?? > Usually it happens by someone copying the file, or replacing the file. [egreshko@meimei ~]$ ll /bin/ping -rwxr-xr-x. 1 root root 39344 Nov 1

Re: ping problem

2012-06-25 Thread JD
On 06/25/2012 12:57 AM, Ed Greshko wrote: getcap /bin/ping $ getcap /bin/ping $ But how could this happen?? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject

Re: ping problem

2012-06-24 Thread Ed Greshko
On 06/25/2012 02:47 PM, Ed Greshko wrote: > Actually.strike all that. Or at least most of it. Need to > rethink... OK *NOW* I do have it The "correct" command is "getcap" root@f17 tmp]# getcap /bin/ping /bin/ping = cap_net_raw+ep If nothing is returned from getcap then

Re: ping problem

2012-06-24 Thread Ed Greshko
On 06/25/2012 02:54 PM, JD wrote: > On 06/25/2012 12:22 AM, Ed Greshko wrote: >> On 06/25/2012 01:21 PM, JD wrote: >>> fc16 with latest updates. >>> >>> Pinging my gateway: >>> $ ping 192.168.42.129 >>> ping: icmp open socket: Operation not permitted >>> >>> Now as root: >>> >>> # ping 192.168.42.1

Re: ping problem

2012-06-24 Thread JD
On 06/25/2012 12:24 AM, Larry wrote: On 06/25/2012 12:21 AM, JD wrote: fc16 with latest updates. Pinging my gateway: $ ping 192.168.42.129 ping: icmp open socket: Operation not permitted

Re: ping problem

2012-06-24 Thread JD
On 06/25/2012 12:22 AM, Ed Greshko wrote: On 06/25/2012 01:21 PM, JD wrote: fc16 with latest updates. Pinging my gateway: $ ping 192.168.42.129 ping: icmp open socket: Operation not permitted Now as root: # ping 192.168.42.129 PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data. 64 byte

Re: ping problem

2012-06-24 Thread Ed Greshko
On 06/25/2012 02:42 PM, Ed Greshko wrote: > OK Now I rememberor at least relearned. > > Looking at LS_COLORS it is the ca=30;41 which gives black letters on red > background. > Which equates to "capability". > > Sodo you have something like this? > > egreshko@f17 tmp]$ lsattr /bin/p

Re: ping problem

2012-06-24 Thread Ed Greshko
On 06/25/2012 02:22 PM, Ed Greshko wrote: > I forget what black on a red background means. OK Now I rememberor at least relearned. Looking at LS_COLORS it is the ca=30;41 which gives black letters on red background. Which equates to "capability". Sodo you have something like this

Re: ping problem

2012-06-24 Thread Larry
On 06/25/2012 12:21 AM, JD wrote: fc16 with latest updates. Pinging my gateway: $ ping 192.168.42.129 ping: icmp open socket: Operation not permitted Now as root: # ping 192.168.42.129 PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data. 64 bytes from 192.168.42.129: icmp_req=1 ttl=64 ti

Re: ping problem

2012-06-24 Thread Ed Greshko
On 06/25/2012 01:21 PM, JD wrote: > fc16 with latest updates. > > Pinging my gateway: > $ ping 192.168.42.129 > ping: icmp open socket: Operation not permitted > > Now as root: > > # ping 192.168.42.129 > PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data. > 64 bytes from 192.168.42.129: icm

ping problem

2012-06-24 Thread JD
fc16 with latest updates. Pinging my gateway: $ ping 192.168.42.129 ping: icmp open socket: Operation not permitted Now as root: # ping 192.168.42.129 PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data. 64 bytes from 192.168.42.129: icmp_req=1 ttl=64 time=3.53 ms 64 bytes from 192.168.42

bridge network ping problem

2012-03-17 Thread 嘉谟
I use tap mode for the guest network in qemu . here is /etc/sysconfig/network-scripts/ifcfg-br0 2 DEVICE=br0 3 TYPE=Bridge 4 BOOTPROTO=static 5 ONBOOT=yes 6 DNS1=192.168.1.1 7 GATEWAY=10.16.255.254 8 IPADDR=10.16.172.77 9 NETMASK=255.255.0.0 10 ONBOOT=yes 11 DELAY=0 12 STP=of