Lol :)))) I thought about it !! But i wanted to find another solution....
So, it's the next step tomorrow morning...
-----Message d'origine-----
De : John Cameron [mailto:John.Cameron@brennanit.com.au]
Envoyé : jeudi 22 mars 2007 16:18
À : Arno MESGUICH; Joe
Cc : nn@qorbit.net
Objet : RE: [nn] Command rejected due to writing config conflict
Dude have you tried rebooting.
-----Original Message-----
From: nn-bounces@qorbit.net [mailto:nn-bounces@qorbit.net] On Behalf Of Arno
MESGUICH
Sent: Thursday, 22 March 2007 8:42 PM
To: 'Joe'
Cc: nn@qorbit.net
Subject: Re: [nn] Command rejected due to writing config conflict
Hi,
I tried the "clear session id #", i looked at the established sessions on
the 10.12.1.165 and there was no connection anymore to the netscreen.
But the "ghost connections" still exists in the "get console" !!!
-----Message d'origine-----
De : Joe [mailto:schneide+ISMNG@XXspamXX.u.washington.edu]
Envoyé : mercredi 21 mars 2007 17:59
À : Arno MESGUICH
Cc : nn@qorbit.net
Objet : Re: [nn] Command rejected due to writing config conflict
Have you tried:
1) clear session id <#>
2) if 10.12.1.165 is a PC/workstation, turn it off and
disconnect from network temporarily.
3) if not a PC/workstation, stop process using this
connection on other host
Joe Schneider
Arno MESGUICH wrote:
> Ok, i tried this.... In vain... :
>
> The get socket shows :
>
> xxxxxxxx(M)-> get socket
> Socket Type State Remote IP Port Local IP Port
> 0 tcp4/6 listen :: 0 ::
80
> 1 tcp4/6 listen :: 0 ::
443
> 2 tcp4/6 listen :: 0 ::
23
> 3 tcp4/6 listen :: 0 ::
22
> 4 tcp listen 0.0.0.0 0 0.0.0.0
12521
> 119 tcp close 0.0.0.0 0 0.0.0.0
0
> 128 tcp close 0.0.0.0 0 0.0.0.0
0
> 140 tcp open 10.12.1.165 36844 126.0.14.49
22
>
>
> The only socket i can kill is the socket id 140 which is my connection (i
> tried and i killed my own connection)
> The problem is that i want to kill the other ssh connections seen in the
get
> console :
>
> xxxxxxxx(M)-> get cons
> Console timeout: 0(minute), Page size: 20/20, debug: buffer
> privilege 200, config has not been changed!, default save prompt on
> exit/reset: yes
> ID State Duration Task Type Host
> 0 Login 4 41220272 SSH 10.12.1.165:57808
> 1 Login 18289 41207952 SSH 10.12.1.165:56314
> 2 Login 86358 41190704 SSH 10.12.1.165:36584
> 3 Logout 0 41211648 Local
> 4 Logout 0 41193168 Local
> 5 Logout 0 41159904 Local
>
> Look at the duration of sessions id 1 and 2. Those connections should have
> been closed since a long time !
>
> Any other idea ?
> Thanks
>
> -----Message d'origine-----
> De : Andre Dyck [mailto:dyck.andre@gmail.com]
> Envoyé : mercredi 21 mars 2007 16:02
> À : Arno MESGUICH
> Cc : 'DH'; nn@qorbit.net
> Objet : Re: [nn] Command rejected due to writing config conflict
>
> Hi Arno,
>
> Arno MESGUICH <arno.mesguich@noxs.fr> [070321 15:31]:
>> The problem is that i can't kick all ssh sessions.
>> I also tried to clear the sessions from a specific ip (10.12.1.165), to
> port
>> 22, using "clear session" with filters. But it doesn't seem to work.
>> Is it possible to kick only one specific connection ?
>
> try this:
>
> - CLI: get socket
> - lookup ID for entry with the specific ip
> - CLI: cl socket id XX (XX is socket ID)
>
> regards
> a.d
_______________________________________________
nn mailing list
nn@qorbit.net
http://qorbit.net/mailman/listinfo/nn
_______________________________________________
nn mailing list
nn@qorbit.net
http://qorbit.net/mailman/listinfo/nn
|