search for: seq3

I have three character strings represented below as seq1, seq2, and seq3. Each string has a reference character different from the other. Thus, for seq1, the reference character is U, seq2, S (3rd S from left where A is leftmost character) and for seq3 Y. seq1 = PQRTUWXYseq2 = AQSDSSDHRSseq3 = EEZYJKFFBHO I wish to generate a 3 by 26 matrix where 3 represent seq1, seq2,...

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

...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 through but no PONG back if I understand correctly. That's > probably where it goes wrong. Yes, the final response is missing. But the above output also lacks the forwarded packets (into your 192.168.1.0/24 subnet). Thus I could imagine, that at least one o...

...uot; is a filter for the interesting traffic) > > Yes obviously. 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 through but no PONG back if I understand correctly. That's probably where it goes wrong. > > > When pinging 192.168.1.3 from client 1, with success, I see packet > passing: > > IP 172.16.0.3 > 192.168.1.3: ICMP echo request, id 2648, seq 23, lengt...

...vierzon 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 through but no PONG back if I understand correctly. That's > > probably where it goes wrong. > > Yes, the final response is missing. > But the above output also lacks the forwarded packets (into your > 192.168.1.0/24 subnet). > Thu...

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"

...topilotmarketing.com/ vCard: http://autopilotmarketing.com/~dan.kubb/vcard __________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEUTdI4DfZD7OEWk0RAlCAAJ0Zk8FVJ6hlf0IbvvPEsLmGcElK4QCfbMt4 9pVmbpKD4IZfnazQwo9fWdk= =SeQ3 -----END PGP SIGNATURE-----

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