search for: rsts

...pad = 0,width = 2 , "left"),2),year=sort(rep(2016:2017,12)))->dt stack(r)->s r->rs for(i in 1:23){ rs[]<-r[]*i addLayer(s,rs)->s print(nlayers(s)) } timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month'])) rts(s,time=as.yearmon(timelst))->rsts str(rsts at time) apply.monthly(rsts,mean) I was expecting that the statistics accept the yearmonth format of the timeslot, as it allows subsetting. Any suggestions? Thanks Herry [[alternative HTML version deleted]]

...ayers(s)) } dt<-list(ID=seq(1:24),month=rep(formatC(1:12,flag=0,width=2),2), year=sort(rep(2016:2017,12))) timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month']),"-01") strptime(timelst,format="%Y-%m-%d")->t1 rts(s,time=as.yearmon(t1))->rsts subset(rsts,'2017')->r2017 class(r2017 at time) class(rsts at time) apply.monthly(rsts,mean) -----Original Message----- From: David Winsemius [mailto:dwinsemius at comcast.net] Sent: Tuesday, 6 March 2018 11:10 AM To: Herr, Alexander (L&W, Black Mountain) <Alexander.Herr at c...

...ID=seq(1:24),month=rep(formatC(1:12,flag=0,width=2),2), > year=sort(rep(2016:2017,12))) > timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month']),"-01") > strptime(timelst,format="%Y-%m-%d")->t1 > > rts(s,time=as.yearmon(t1))->rsts > subset(rsts,'2017')->r2017 > class(r2017 at time) > class(rsts at time) > > apply.monthly(rsts,mean) > > > > -----Original Message----- > From: David Winsemius [mailto:dwinsemius at comcast.net] > Sent: Tuesday, 6 March 2018 11:10 AM > To: Herr, Alex...

...ar=sort(rep(2016:2017,12)))->dt > stack(r)->s > r->rs > for(i in 1:23){ > rs[]<-r[]*i > addLayer(s,rs)->s > print(nlayers(s)) > } > timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month'])) > rts(s,time=as.yearmon(timelst))->rsts > str(rsts at time) > apply.monthly(rsts,mean) > > I was expecting that the statistics accept the yearmonth format of the timeslot, as it allows subsetting. > Any suggestions? > Thanks > Herry > > [[alternative HTML version deleted]] > > ________________________...

...r=sort(rep(2016:2017,12)))->dt > stack(r)->s > r->rs > for(i in 1:23){ > rs[]<-r[]*i > addLayer(s,rs)->s > print(nlayers(s)) > } > timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month'])) > rts(s,time=as.yearmon(timelst))->rsts > str(rsts at time) > apply.monthly(rsts,mean) > > I was expecting that the statistics accept the yearmonth format of the timeslot, as it allows subsetting. > Any suggestions? > Thanks > Herry > > [[alternative HTML version deleted]] > > ____________________...

...ayers(s)) } dt<-list(ID=seq(1:24),month=rep(formatC(1:12,flag=0,width=2),2), year=sort(rep(2016:2017,12))) timelst<-paste0(unlist(dt['year']),'-',unlist(dt['month']),"-01") strptime(timelst,format="%Y-%m-%d")->t1 rts(s,time=as.yearmon(t1))->rsts subset(rsts,'2017')->r2017 class(r2017 at time) class(rsts at time) apply.monthly(rsts,mean) # this creates error rts(s,time=as.Date(t1))->rsts1 apply.monthly(rsts1,mean) # this creates output -----Original Message----- From: Jim Lemon [mailto:drjimlemon at gmail.com] Sent: Tuesda...

...cking, but connections in other states are only subject to the "within the window" check. Part 2 of the patch is simply a patch to netstat so that it displays the statistic. As expected, it's very straightforward, the only real question is what to call the statistic... "Ignored RSTs in the window" isn't the best description. FWIW, I've been testing with the exploit code (reset-tcp-rfc31337-compliant.c from osvdb-4030-exploit.zip), and this change does indeed defeat the attack. It took me a while to get the code working, they really munged up the libnet calls, bu...

Forwarded message: > From full-disclosure-admin@lists.netsys.com Wed Apr 21 11:49:12 2004 > To: full-disclosure@lists.netsys.com > From: Darren Bounds <dbounds@intrusense.com> > Subject: [Full-Disclosure] IETF Draft - Fix for TCP vulnerability > Date: Tue, 20 Apr 2004 18:19:58 -0400 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >

A lot of us wouldn't be here without him. DEC made good, really reliable hardware. mark <http://www.networkworld.com/news/2011/020711-kenneth-olsen-dec-obit.html>

Hi, Some lines are printing on console: [CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] CAppConfig:: getString() Required config parameter [amqp_password] is missing from section [c ommunication_amqp] Can you help me to understand why we are getting these lines on console? How we can remove these lines from the console? Please suggest. Thanks & Regards, Shagun

...on comes from the workstation, and is greeted with a SYNACK by the server which also disappears - finally, the workstation gets tired of waiting and the connecting application fails - several minutes later the glitch magically clears up, and the missing SYNACKs are sent to the workstation, which RSTs them. - everything works later on I haven't discovered a method to reproduce this behaviour, and my sysadminning is only part time here, as I have windows coding to do. The detective work I mentioned was done several weeks ago, and the local LUG here classified it as a nat/conntrack bug. I...

...addresses. But I was testing something else, and while looking at this interface with a packet capture, I accidentally noticed that a public internet interface was occasionally sending packets sourced from internal private machines, using an RFC1918 address as the source address. These were FIN and RSTs, only, just like you say. Unlike some of you, I use a front-end for IPtables that makes use of perl scripting (which in the end, scripts IPtables similarly in the way most of you are also scripting your policies). So then I composed a huge bug report that I was going to submit to the developer of...

Having moved from a "cascading LANs" configuration to two independent LANs on eth0 and eth1, I still get some "state INVALID" for which I am not sure what the cause is. Can somebody help me understand its probable origin? Thanks, Costantino [see attachment]

Hi, When deploying a BSD with IPF in at the network perimeter and using rules like these: pass in .. proto tcp ... keep state(strict) it's possible to refuse tcp packets which arrive out of order. This would increase the difficulty doing blind attack resets and blind data injection attack, cause then you'd have to "guess" the exact expected number. Checpoint has a similar

http://www.uniras.gov.uk/vuls/2004/236929/index.htm ----Quote---- "The impact of this vulnerability varies by vendor and application, but in some deployment scenarios it is rated critical. Please see the vendor section below for further information. Alternatively contact your vendor for product specific information. If exploited, the vulnerability could allow an attacker to create a

On Sat, 29 May 2004 12:00:52 -0700 (PDT), <freebsd-security-request@freebsd.org> wrote: Hello ! Today i see in snort logs : [**] [1:528:4] BAD-TRAFFIC loopback traffic [**] [Classification: Potentially Bad Traffic] [Priority: 2] 06/07-09:44:39.044590 127.0.0.1:80 -> 10.6.148.173:1566 TCP TTL:128 TOS:0x0 ID:577 IpLen:20 DgmLen:40 ***A*R** Seq: 0x0 Ack: 0x75830001 Win: 0x0 TcpLen:

From: Andy King <acking at vmware.com> ** Introduce VM Sockets *** In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly VMCI Sockets) (vmw_vsock) kernel module for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. Unlike previous

From: Andy King <acking at vmware.com> ** Introduce VM Sockets *** In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly VMCI Sockets) (vmw_vsock) kernel module for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. Unlike previous

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012