Hello Debian Team,
We are using Linux Debain 9 in our moxa devices.
we are connected in a network where we connect with our moxa device via ssh and
run the commands with Gauge ip and port and get Data.
Now I'm Facing issue from 2, 3 weeks to connect the moxa using ssh and then
connect to the seri
On 03/04/11 02:07, Stephen Powell wrote:
> On Fri, 01 Apr 2011 06:02:38 -0400 (EDT), MAROUNI Abbass wrote:
> I also used to have an IBM PS/2 Model 70. The UART on its motherboard
> is a 16550A. According to the manufacturer's specifications, the
> 16550A is capable of operating at speeds of up
On Fri, 01 Apr 2011 06:02:38 -0400 (EDT), MAROUNI Abbass wrote:
>
> Sorry forgot to mention that we are in Paris and the datacenter is in
> Amsterdam. So no physical access to the servers.
For your production environment, perhaps. But you led us to believe
that you had two local servers side-by
Le 01/04/11 01:51, Stephen Powell a écrit :
On Thu, 31 Mar 2011 09:14:07 -0400 (EDT), MAROUNI Abbass wrote:
In a production environment, this what will happen :
Two servers connected with a single serial cable ( Which I need to
figure out how?! :) ), ttyS0 on server1 to ttyS0 on server2.
getty
On Thu, 31 Mar 2011 09:14:07 -0400 (EDT), MAROUNI Abbass wrote:
> In a production environment, this what will happen :
>
> Two servers connected with a single serial cable ( Which I need to
> figure out how?! :) ), ttyS0 on server1 to ttyS0 on server2.
> getty is always listening to the ttyS0 por
Abbass,
From: MAROUNI Abbass
Date: Thu, 31 Mar 2011 15:14:07 +0200
> I am still not convinced that the serial cable might have different ends
> if it's a standard null modem cable, ...
You haven't ruled out a broken conductor where you can't see it.
And there are other cables with the app
Stephen Powell put forth on 3/31/2011 6:30 AM:
> You can't
> reverse the direction of communications without physical access to
> *both* servers. That is why you need two serial ports on each server
> and two properly-wired cross-over cables. If you only care about
> one-way control, then why d
MAROUNI Abbass wrote:
In a production environment, this what will happen :
Two servers connected with a single serial cable ( Which I need to
figure out how?! :) ), ttyS0 on server1 to ttyS0 on server2.
getty is always listening to the ttyS0 port on both servers (assured by
inittab respawn).
server is unaccessible
or haven't come up after a restart, so we can connect to its pair and
pass through the serial connection to see what's happening. The idea of
using a single cable is to enconomise. I thought it would be relativley
simple since it's logically possible. I migth need
able per server.
>
> The Two servers are exactly the same. getty and minicom have the same
> exact parameters.
> We need to use the serial connections in case one server is unaccessible
> or haven't come up after a restart, so we can connect to its pair and
> pass through
MAROUNI Abbass wrote:
The Two servers are exactly the same. getty and minicom have the same
exact parameters.
Which are top secret. :-)
I thought it would be relativley
simple since it's logically possible. I migth need to check the cables
but I think it's the standard Null modem.
I thoug
Abbass,
> I migth need to check the cables but I think it's the standard Null modem.
Yes, check the cable wiring with an ohmeter. All the hope in the
world won't help. As Stephen said,
> You need to find out
> *exactly* how your cross-over cable or null modem is wired. There may
> be some as
fusion (in this thread) comes from the
difference between an ideal balanced state, and a non-functioning state.
[...]
More importantly - the 'phone system, particularly the outsiders view of
it, is not particularly relevant to the "serial connection" cabling
question. :-)
[...
ave the same
exact parameters.
We need to use the serial connections in case one server is unaccessible
or haven't come up after a restart, so we can connect to its pair and
pass through the serial connection to see what's happening. The idea of
using a single cable is to enconomise. I t
tems are extremely robust, and very few these days are
pure copper.
More importantly - the 'phone system, particularly the outsiders view of
it, is not particularly relevant to the "serial connection" cabling
question. :-)
Note: the opinions and experiences of telecommunications technic
On 30/03/11 01:18, MAROUNI Abbass wrote:
> Le 28/03/11 10:30, Russell L. Harris a �crit :
>> to:
>> CC:
>> * Stan Hoeppner [110328 06:24]:
>>> Moczik Gabor put forth on 3/28/2011 12:01 AM:
Stan Hoeppner wrote:
> I think that the discussion diverted somehow from my original question.
>
> M
On Tue, 29 Mar 2011 10:18:50 -0400 (EDT), MAROUNI Abbass wrote:
>
> I think that the discussion diverted somehow from my original question.
>
> My problem was the following :
> Two identical servers Z0 & Z1 and a null modem cable. ttyS0 on Z0
> connected to ttyS1 on Z1.
> on ttyS0 on Z0 I have
* MAROUNI Abbass [110329 14:21]:
> I think that the discussion diverted somehow from my original question.
>
> My problem was the following :
> Two identical servers Z0 & Z1 and a null modem cable. ttyS0 on Z0
> connected to ttyS1 on Z1.
> on ttyS0 on Z0 I have a getty listening for incoming con
Le 28/03/11 10:30, Russell L. Harris a écrit :
to:
CC:
* Stan Hoeppner [110328 06:24]:
Moczik Gabor put forth on 3/28/2011 12:01 AM:
Stan Hoeppner wrote:
We bought DB25 plugs in bags of 100, and used spooled CAT5 as the noise
rejection is many times that of CAT3, allowing greater distances ac
to:
CC:
* Stan Hoeppner [110328 06:24]:
> Moczik Gabor put forth on 3/28/2011 12:01 AM:
> > Stan Hoeppner wrote:
> >> We bought DB25 plugs in bags of 100, and used spooled CAT5 as the noise
> >> rejection is many times that of CAT3, allowing greater distances across
> >> sprawling warehouses.
>
Stan Hoeppner wrote:
Moczik Gabor put forth on 3/28/2011 12:01 AM:
Stan Hoeppner wrote:
We bought DB25 plugs in bags of 100, and used spooled CAT5 as the noise
rejection is many times that of CAT3, allowing greater distances across
sprawling warehouses.
RS-232 uses single-ended signaling and r
* Stan Hoeppner [110328 06:24]:
> The single largest user of twisted pair cable, its inventor and
> progenitor actually, was AT&T (the old monopoly AT&T), now known as many
> different companies after the 1980s breakup of the AT&T monpoly and the
> creation of the "baby Bells", now known as Verizo
Moczik Gabor put forth on 3/28/2011 12:01 AM:
> Stan Hoeppner wrote:
>> We bought DB25 plugs in bags of 100, and used spooled CAT5 as the noise
>> rejection is many times that of CAT3, allowing greater distances across
>> sprawling warehouses.
>
> RS-232 uses single-ended signaling and requires sh
Stan Hoeppner wrote:
We bought DB25 plugs in bags of 100, and used spooled CAT5 as the noise
rejection is many times that of CAT3, allowing greater distances across
sprawling warehouses.
RS-232 uses single-ended signaling and requires shielded cable, twisted
pair doesn't help either. The common
On 28/03/11 11:46, Stephen Powell wrote:
> On Sun, 27 Mar 2011 16:27:08 -0400 (EDT), Stan Hoeppner wrote:
>>
>> For attaching a terminal all you need to connect are pins 2, 3, and 7 on
>> a DB25, or 2, 3, and 5 on a DB9. Reverse 2,3 on one end of each cable
>> to get your x-over. All the other pi
On Sun, 27 Mar 2011 19:30:49 -0400 (EDT), ow...@netptc.net wrote:
> On Sun, 27 Mar 2011 14:41:37 -0400 (EDT, Stephen Powell wrote:
>>
>> That's true. But a properly-wired cross-over cable or null modem
>> not only crosses over TD and RD but also crosses over DTR and DSR
>> and also crosses over
On Sun, 27 Mar 2011 16:27:08 -0400 (EDT), Stan Hoeppner wrote:
>
> For attaching a terminal all you need to connect are pins 2, 3, and 7 on
> a DB25, or 2, 3, and 5 on a DB9. Reverse 2,3 on one end of each cable
> to get your x-over. All the other pins are for modems only and are not
> used for
- Original Message -
From: Stephen Powell
To: debian-user@lists.debian.org
Sent: 3/27/2011 6:41:37 PM
Subject: Re: Serial Connection
On Sun, 27 Mar 2011 11:40:40 -0400 (EDT), ow...@netptc.net wrote:
> On Sat, 26 Mar 2011 18:52:23 -0400 (EDT, Stephen Powell wrote:
>&
Stephen Powell put forth on 3/27/2011 1:41 PM:
> That's true. But a properly-wired cross-over cable or null modem
> not only crosses over TD and RD but also crosses over DTR and DSR
> and also crosses over RTS and CTS. Ground, of course, is wired
> to Ground. CD is normally tied to DSR on the s
On Sun, 27 Mar 2011 11:40:40 -0400 (EDT), ow...@netptc.net wrote:
> On Sat, 26 Mar 2011 18:52:23 -0400 (EDT, Stephen Powell wrote:
>>
>> I haven't tried this, but one thing you want to make sure of is that
>> you use a "cross-over" cable. The serial ports on PCs have what's known
>> as a DTE int
- Original Message -
From: Stephen Powell
To: debian-user@lists.debian.org
Sent: 3/26/2011 10:52:23 PM
Subject: Serial Connection
On Mon, 21 Mar 2011 at 17:45:17 +0100, MAROUNI Abbass wrote:
>
> I have two servers with Debian Lenny installed.
>
> The two servers h
On Mon, 21 Mar 2011 at 17:45:17 +0100, MAROUNI Abbass wrote:
>
> I have two servers with Debian Lenny installed.
>
> The two servers have a serial cable connected form Stty0 on Server0
> to Stty1 on Server1. I can use minicom to log into Server0, but when
> I try to login to Server1 from Server0
Hello all,
I have two servers with Debian Lenny installed.
The two servers have a serial cable connected form Stty0 on Server0 to
Stty1 on Server1.
I can use minicom to log into Server0, but when I try to login to
Server1 from Server0 using minicom I get some garbage and I can't type
anything
With the Samsung V200 phone I received a datacable (serial) with
Windows software (EasyGPRS). I have tried to install the software on
wine, but did not have success.
I would like to be able to download pictures from the phone using the
datacable. Does anyone know about Linux software able to do
<...>
> > HDD IRQs are unmasked:
> > hdparm -u1 # READ the hdparm manpage first!
>
> At which end? What does this do?
both, if possible (may break things with some chipsets),
it ensures serial IRQ events are handled in a timely manner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
on Wed, Sep 03, 2003 at 12:02:01PM -0600, Bruce Sass ([EMAIL PROTECTED]) wrote:
> --
> On Wed, 3 Sep 2003, Karsten M. Self wrote:
>
> > I'm running minicom over a null-modem serial cable settings: 57600 8N1.
> >
> > File transfer setting is:
> >
> > zmodem /usr/bin/sz -vv -be YUN
I'm still trying to debug my file transfers between two Debian GNU/Linux
systems using zmodem file transfers from within minicom, over a serial
connection.
I'm running minicom over a null-modem serial cable settings: 57600 8N1.
File transfer setting is:
zmodem /usr/bin/sz -vv
Mike Fedyk said:
> How can I read-only log both sides with a program available in debian
> (from debian-sid is ok, if required)?
I'm sure it's overkill but I use minicom for logging, fire it up in
screen, turn on the buffer logging and detach ..
never tried doing exactly what your trying though
Hi,
I have a null serial cable between two debian linux systems. Niether side
has a serial login setup on the serial port. I want to be able to catch an
oops on either computer with the other still-working system, and log it to a
file.
Now, I've tried using ttylog, and found a nice bug (see the
Hi,
After many mistakes, defective cables, and a lot of help from these
people,
I have login to my Slink box from a Win95 box. I have:
A null modem 9-pin mini cable about 10 meters long.
HyperTerminal on Win95
(windows\Start Menu\Programs\Accessories\Hyper
Terminal\hypertrm.exe)
Direct to C
Hello!
Here I am again after a long, long time in a galaxy far, far away...
Sorry for not replying so long, but I was terribly busy all the time. And
thanks for all your work on this issue!!
> After reading the .inf (it's in plain text, and commented :)), you don't
> use a PPP connection - you us
Hello!
Sorry for not replying for a so long time. I'll to get a network adapter
soon, so that the problem will be solved.
Thanks very much for your suggestion, I'll try it as it sounds quite easy
and I'm no linux (network) expert.
I'm also talking about the net emulation with Phil, but I think, i
e <[EMAIL PROTECTED]>
To: Stephan Hachinger <[EMAIL PROTECTED]>
Sent: Wednesday, September 29, 1999 3:49 AM
Subject: Re: Serial connection to windoze box
> A long time ago, in a galaxy far, far way, someone said...
>
> > I've now got the inf file, and I'm tryi
have any
money left at all :(
- Original Message -
From: Phil Brutsche <[EMAIL PROTECTED]>
To: Stephan Hachinger <[EMAIL PROTECTED]>
Cc:
Sent: Monday, September 27, 1999 9:40 PM
Subject: Re: Serial connection to windoze box
> A long time ago, in a galaxy far, far way, someo
>Used ethernet cards cost pennies and Windows 95
>usually already has a
>driver
>for them. If you can track down some 50 ohm
>terminators, these rest is
>usually available for next to nothing.
Make sure you get the kind of ethernet cards that have
bnc coax connectors on them. RadioShack has coax
Phil Brutsche wrote:
>
> The best way of doing things, I think, is ethernet. I don't know how much
> things cost in Germany, but here in the US you can get a "home networking
> kit" for about US$70. It includes two PCI cards, a hub, and two ethernet
> cables.
Used ethernet cards cost pennies a
A long time ago, in a galaxy far, far way, someone said...
> Hello!
>
> I'd like to connect my slink box to my W95 machine over a serial cable. If
> anyone knows a more or less comfortable way to do this, please let me know.
>
> Best solution was of course some network emulation, but I think thi
Hello!
I'd like to connect my slink box to my W95 machine over a serial cable. If
anyone knows a more or less comfortable way to do this, please let me know.
Best solution was of course some network emulation, but I think this isn't
possible.
Kind Regards, and thanks for any reply,
Stephan Hac
On Sun, 25 Apr 1999 18:41:44 -0500 (CDT), Jor-el wrote:
>> You need a 2.2.x kernel for this to work or a patched 2.0.x one.
Basically
>> you use a kernel command-line parameter of "console=ttyS0" to make a
serial
>> terminal (box A in your setup) hooked to /dev/ttyS0 on machine B the
display
On Sun, 25 Apr 1999, Robert Vollmert wrote:
> Hi,
>
> On Sun, Apr 25, 1999 at 11:39:53AM -0500, Jor-el wrote:
> > The what I would like to do is to use the monitor that I have as a
> > console for both machines A and B. Unfortunately, I cant accomplish this
> > via a CPU switch, thanks to t
On Sun, 25 Apr 1999, Ralf G. R. Bergs wrote:
> On Sun, 25 Apr 1999 11:39:53 -0500 (CDT), Jor-el wrote:
>
> >Is this possible?
>
> Yes. See /usr/src/linux/Documentation/serial-console.txt.
>
> I've just done it (after having some trouble due to an incorrect
> /dev/console device).
>
> You ne
Hi,
On Sun, Apr 25, 1999 at 11:39:53AM -0500, Jor-el wrote:
> The what I would like to do is to use the monitor that I have as a
> console for both machines A and B. Unfortunately, I cant accomplish this
> via a CPU switch, thanks to the non-standard monitor cable (Aptiva S90)
> that I have.
On Sun, 25 Apr 1999 11:39:53 -0500 (CDT), Jor-el wrote:
>Is this possible?
Yes. See /usr/src/linux/Documentation/serial-console.txt.
I've just done it (after having some trouble due to an incorrect
/dev/console device).
You need a 2.2.x kernel for this to work or a patched 2.0.x one. Basically
Hi,
I have the following setup :
---
| | | |
|A| | B|
| | | |
---
>
> Ooops, I meant a null-modem connection.
>
>
I have an old PC XT-compatible hooked up to my 486 with a null-modem
cable. I added a getty for it (COM2 == ttyS1) in my /etc/inittab file:
# :::
0:23:respawn:/sbin/getty 19200,9600 ttyS1 vt100
--gilbert
___
Ooops, I meant a null-modem connection.
56 matches
Mail list logo
