similar to: counting characters starting point

Hello Julien, Am Tue, 15 Jan 2019 09:30:23 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > In that case I see: > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq1, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq2, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq3, length 64 > > Packet goes

Le mar. 15 janv. 2019 à 03:13, Lars Kruse <lists at sumpfralle.de> a écrit : > Hello Julien, > > > Am Mon, 14 Jan 2019 22:15:47 +0100 > schrieb Julien dupont <marcelvierzon at gmail.com>: > > > > ** Test 1 ** > > On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' > > When pinging 192.168.1.1 from client 1, with no success, I

ip_forward was not enabled, now it is. Still same result: On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.1' and ping 192.168.1.1 from the client: 5:28:42.646203 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 1, length 64 15:28:43.663014 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 2, length 64 15:28:44.688133 IP 172.16.0.3 >

Hello Julien, Am Mon, 14 Jan 2019 22:15:47 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > ** Test 1 ** > On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' > When pinging 192.168.1.1 from client 1, with no success, I see no packet > passing. Sorry - the tcpdump command should end with "192.168.1.1" instead of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, A few months ago someone posted a message about specifying validates_* constraints on a per-attribute basis. I just created a small plugin that allows you to do this. Here''s an example from one of my models: class Country < ActiveRecord::Base attribute :name, :string do |a| a.validates_length :within =>

Derar Rxperts, I have a strange situation.. I see curly brackets around "strip.levels" in multipanel strips while using lattice::xyplot. .How do I get rid of the curly brackets? For some reason, I am not able to reproduce the problem using an example below... Any suggestions are highly welcome! Thanks, Santosh q <-

Hello, my series of dates look like [1] "2012-05-30 18:30:00 UTC" "2012-05-30 19:30:00 UTC" [3] "2012-05-30 20:30:00 UTC" "2012-05-30 21:30:00 UTC" [5] "2012-05-30 22:30:00 UTC" "2012-05-30 23:30:00 UTC" [7] "2012-05-31 00:30:00 UTC" "2012-05-31 01:30:00 UTC" [9] "2012-05-31 02:30:00 UTC"

WARNING: This is not compatible with the previous lz4 patchset. If you''re using experimental compression that isn''t in mainline kernels, be prepared to backup and restore or decompress before upgrading, and have backups in case it eats data (which appears not to be a problem any more, but has been during development). These patches add lz4 and lz4hc compression

Hi, I need to reshape my dataframe from a long format to a wide format. Unfortunately, I have a continuous date variable which gives me headaches. Consider the following example: > id=c("034","034","016","016","016","340","340") > date=as.Date(c("1997-09-28", "1997-10-06", "1997-11-04",