Fwd: Cross-console for RIS box - F root in NYC
Arife, Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console? Joe Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 18 January 2005 09:38:42 EST To: Systems Operations <ops-workers@isc.org> Subject: Fwd: Cross-console for RIS box - F root in NYC
RIPE are agreeable to a cross console arrangement if we can get the cables in place. OUr username on their box will be isc, and theirs on ours will be risops, as per below
Joao
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 17 January, 2005 12:39:28 CET To: Arife Vural <arife@ripe.net> Cc: ris-int@ripe.net, andrei@ripe.net Subject: Re: [henk@ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box - F root in NYC]]
On 17 Jan, 2005, at 11:04, Arife Vural wrote:
Hi Joao,
Sorry for the late reply.
That sounds good. Do you think you can do the cabling over there?
I think we can get telehouse to do it for us, yes.
I ask OPS to create an account on RIS box, and you can get the console through this user. As username, is isc OK, or would you like to have something else?
isc is fine for us.
For ris, I suggest you to use risops.
shall do I will let you know as we get telehouse to schedule this
Joao
Hi Joe,
Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console?
It looks we have only one serial port, I did not think about that. Please go head and do the cabling, we can use that port F root. I will get back to you about user info. Arife
Joe
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 18 January 2005 09:38:42 EST To: Systems Operations <ops-workers@isc.org> Subject: Fwd: Cross-console for RIS box - F root in NYC
RIPE are agreeable to a cross console arrangement if we can get the cables in place. OUr username on their box will be isc, and theirs on ours will be risops, as per below
Joao
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 17 January, 2005 12:39:28 CET To: Arife Vural <arife@ripe.net> Cc: ris-int@ripe.net, andrei@ripe.net Subject: Re: [henk@ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box - F root in NYC]]
On 17 Jan, 2005, at 11:04, Arife Vural wrote:
Hi Joao,
Sorry for the late reply.
That sounds good. Do you think you can do the cabling over there?
I think we can get telehouse to do it for us, yes.
I ask OPS to create an account on RIS box, and you can get the console through this user. As username, is isc OK, or would you like to have something else?
isc is fine for us.
For ris, I suggest you to use risops.
shall do I will let you know as we get telehouse to schedule this
Joao
Hi Joe, Just James reminded me, we have USB port on RIS box, if you can find a USB-Serial converter, we can use that port for us. Arife On Wed, Jan 19, 2005 at 10:41:58AM +0100, Arife Vural wrote:
Hi Joe,
Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console?
It looks we have only one serial port, I did not think about that. Please go head and do the cabling, we can use that port F root.
I will get back to you about user info.
Arife
Joe
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 18 January 2005 09:38:42 EST To: Systems Operations <ops-workers@isc.org> Subject: Fwd: Cross-console for RIS box - F root in NYC
RIPE are agreeable to a cross console arrangement if we can get the cables in place. OUr username on their box will be isc, and theirs on ours will be risops, as per below
Joao
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 17 January, 2005 12:39:28 CET To: Arife Vural <arife@ripe.net> Cc: ris-int@ripe.net, andrei@ripe.net Subject: Re: [henk@ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box - F root in NYC]]
On 17 Jan, 2005, at 11:04, Arife Vural wrote:
Hi Joao,
Sorry for the late reply.
That sounds good. Do you think you can do the cabling over there?
I think we can get telehouse to do it for us, yes.
I ask OPS to create an account on RIS box, and you can get the console through this user. As username, is isc OK, or would you like to have something else?
isc is fine for us.
For ris, I suggest you to use risops.
shall do I will let you know as we get telehouse to schedule this
Joao
Hi Joe, Could you please send us your public key to login RIS box? Arife
Just James reminded me, we have USB port on RIS box, if you can find a USB-Serial converter, we can use that port for us.
Arife
On Wed, Jan 19, 2005 at 10:41:58AM +0100, Arife Vural wrote:
Hi Joe,
Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console?
It looks we have only one serial port, I did not think about that. Please go head and do the cabling, we can use that port F root.
I will get back to you about user info.
Arife
Joe
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 18 January 2005 09:38:42 EST To: Systems Operations <ops-workers@isc.org> Subject: Fwd: Cross-console for RIS box - F root in NYC
RIPE are agreeable to a cross console arrangement if we can get the cables in place. OUr username on their box will be isc, and theirs on ours will be risops, as per below
Joao
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 17 January, 2005 12:39:28 CET To: Arife Vural <arife@ripe.net> Cc: ris-int@ripe.net, andrei@ripe.net Subject: Re: [henk@ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box - F root in NYC]]
On 17 Jan, 2005, at 11:04, Arife Vural wrote:
Hi Joao,
Sorry for the late reply.
That sounds good. Do you think you can do the cabling over there?
I think we can get telehouse to do it for us, yes.
I ask OPS to create an account on RIS box, and you can get the console through this user. As username, is isc OK, or would you like to have something else?
isc is fine for us.
For ris, I suggest you to use risops.
shall do I will let you know as we get telehouse to schedule this
Joao
On 19 Jan 2005, at 08:03, Arife Vural wrote:
Could you please send us your public key to login RIS box?
I'll assume that means ssh public key (if you mean some other kind, let me know). Joe
On 19 Jan 2005, at 09:26, Arife Vural wrote:
Could you please send us your public key to login RIS box?
I'll assume that means ssh public key (if you mean some other kind, let me know).
Yes. Your ssh public is in place. Please try to login rrc111.ripe.net, by using isc user. Let me know if you would have a problem.
Looks like I have a problem: The file /Users/jabley/.ssh/id_dsa corresponds to the public key I sent you. [jabley@ganesh]% ssh -v isc@rrc111.ripe.net OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090702f debug1: Reading configuration data /etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: Connecting to rrc111.ripe.net [213.200.66.6] port 22. debug1: Connection established. debug1: identity file /Users/jabley/.ssh/identity type -1 debug1: identity file /Users/jabley/.ssh/id_rsa type -1 debug1: identity file /Users/jabley/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175 debug1: Miscellaneous failure No credentials cache found debug1: Miscellaneous failure No credentials cache found debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'rrc111.ripe.net' is known and matches the RSA host key. debug1: Found key in /Users/jabley/.ssh/known_hosts:100 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /Users/jabley/.ssh/identity debug1: Trying private key: /Users/jabley/.ssh/id_rsa debug1: Offering public key: /Users/jabley/.ssh/id_dsa debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,keyboard-interactive debug1: No more authentication methods to try. Permission denied (publickey,keyboard-interactive). debug1: Calling cleanup 0x1c540(0x0) [jabley@ganesh]%
Joe, Could you please try again? BTW, this user can only run minicom, I hope that's OK. If you would need full shell access, please let us know. Arife
On 20 Jan 2005, at 04:43, Arife Vural wrote:
Could you please try again?
See below -- still doesn't work. If it's easier, please feel free to pgp-encrypt a password to me by e-mail, or to SMS one. My cellphone is the 519 number in this person object: person: Joe Abley address: 73 Base Line Road East address: London, ON address: N6C 2N6 address: CANADA phone: +1 650 423 1310 phone: +1 519 670 9327 e-mail: jabley@isc.org nic-hdl: JA856-RIPE changed: jabley@isc.org 20050120 source: RIPE mnt-by: MAINT-ISC and my PGP key can be found as key-cert: PGPKEY-E4DB44F2 (which you can either extract from the RPSL object, or which you can find on any of the usual key servers and use the key-cert: object to verify the fingerprint).
BTW, this user can only run minicom, I hope that's OK. If you would need full shell access, please let us know.
No, that should be fine. Joe [jabley@ganesh]% ssh -v isc@rrc111.ripe.net OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090702f debug1: Reading configuration data /etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: Connecting to rrc111.ripe.net [213.200.66.6] port 22. debug1: Connection established. debug1: identity file /Users/jabley/.ssh/identity type -1 debug1: identity file /Users/jabley/.ssh/id_rsa type -1 debug1: identity file /Users/jabley/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175 debug1: Miscellaneous failure No credentials cache found debug1: Miscellaneous failure No credentials cache found debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'rrc111.ripe.net' is known and matches the RSA host key. debug1: Found key in /Users/jabley/.ssh/known_hosts:100 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /Users/jabley/.ssh/identity debug1: Trying private key: /Users/jabley/.ssh/id_rsa debug1: Offering public key: /Users/jabley/.ssh/id_dsa debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,keyboard-interactive debug1: No more authentication methods to try. Permission denied (publickey,keyboard-interactive). debug1: Calling cleanup 0x1c540(0x0) [jabley@ganesh]%
Hi Joe, I forward your e-mail to our OPS guys, they will get bakc to you. Arife On Thu, Jan 20, 2005 at 09:39:51AM -0500, Joe Abley wrote:
On 20 Jan 2005, at 04:43, Arife Vural wrote:
Could you please try again?
See below -- still doesn't work.
If it's easier, please feel free to pgp-encrypt a password to me by e-mail, or to SMS one. My cellphone is the 519 number in this person object:
person: Joe Abley address: 73 Base Line Road East address: London, ON address: N6C 2N6 address: CANADA phone: +1 650 423 1310 phone: +1 519 670 9327 e-mail: jabley@isc.org nic-hdl: JA856-RIPE changed: jabley@isc.org 20050120 source: RIPE mnt-by: MAINT-ISC
and my PGP key can be found as key-cert: PGPKEY-E4DB44F2 (which you can either extract from the RPSL object, or which you can find on any of the usual key servers and use the key-cert: object to verify the fingerprint).
BTW, this user can only run minicom, I hope that's OK. If you would need full shell access, please let us know.
No, that should be fine.
Joe
[jabley@ganesh]% ssh -v isc@rrc111.ripe.net OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090702f debug1: Reading configuration data /etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: Connecting to rrc111.ripe.net [213.200.66.6] port 22. debug1: Connection established. debug1: identity file /Users/jabley/.ssh/identity type -1 debug1: identity file /Users/jabley/.ssh/id_rsa type -1 debug1: identity file /Users/jabley/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175 debug1: Miscellaneous failure No credentials cache found
debug1: Miscellaneous failure No credentials cache found
debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'rrc111.ripe.net' is known and matches the RSA host key. debug1: Found key in /Users/jabley/.ssh/known_hosts:100 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /Users/jabley/.ssh/identity debug1: Trying private key: /Users/jabley/.ssh/id_rsa debug1: Offering public key: /Users/jabley/.ssh/id_dsa debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,keyboard-interactive debug1: No more authentication methods to try. Permission denied (publickey,keyboard-interactive). debug1: Calling cleanup 0x1c540(0x0) [jabley@ganesh]%
I think we could do that Joao On 19 Jan, 2005, at 13:50, Arife Vural wrote:
Hi Joe,
Just James reminded me, we have USB port on RIS box, if you can find a USB-Serial converter, we can use that port for us.
Arife
On Wed, Jan 19, 2005 at 10:41:58AM +0100, Arife Vural wrote:
Hi Joe,
Can you confirm that your box in New York has two serial ports available, one to talk to our console and one to act as RIS console?
It looks we have only one serial port, I did not think about that. Please go head and do the cabling, we can use that port F root.
I will get back to you about user info.
Arife
Joe
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 18 January 2005 09:38:42 EST To: Systems Operations <ops-workers@isc.org> Subject: Fwd: Cross-console for RIS box - F root in NYC
RIPE are agreeable to a cross console arrangement if we can get the cables in place. OUr username on their box will be isc, and theirs on ours will be risops, as per below
Joao
Begin forwarded message:
From: Joao Damas <Joao_Damas@isc.org> Date: 17 January, 2005 12:39:28 CET To: Arife Vural <arife@ripe.net> Cc: ris-int@ripe.net, andrei@ripe.net Subject: Re: [henk@ripe.net: Fwd: Re: [Fwd: Cross-console for RIS box - F root in NYC]]
On 17 Jan, 2005, at 11:04, Arife Vural wrote:
Hi Joao,
Sorry for the late reply.
That sounds good. Do you think you can do the cabling over there?
I think we can get telehouse to do it for us, yes.
I ask OPS to create an account on RIS box, and you can get the console through this user. As username, is isc OK, or would you like to have something else?
isc is fine for us.
For ris, I suggest you to use risops.
shall do I will let you know as we get telehouse to schedule this
Joao
On 19 Jan 2005, at 07:50, Arife Vural wrote:
Just James reminded me, we have USB port on RIS box, if you can find a USB-Serial converter, we can use that port for us.
Any particular chipset for the USB-Serial dongle? (What OS do the RIS boxes run?) Joe
Just James reminded me, we have USB port on RIS box, if you can find a USB-Serial converter, we can use that port for us.
Any particular chipset for the USB-Serial dongle?
(What OS do the RIS boxes run?)
Debian Linux, dmesg only says following, usb.c: registered new driver hub Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. I'm not sure it's helpful enough. RIS box is Dell PowerEdge1750. Arife
participants (3)
-
Arife Vural -
Joao Damas -
Joe Abley