I got cu to work on /dev/ttyS2 . That is odd due ti the fact there are only
two serial ports on my system, it would open ttyS0 and
bmike1@1[bmike1]$ sudo cu -s 9600 -l /dev/ttyS1
cu: open (/dev/ttyS1): No such device <------------------
cu: /dev/ttyS1: Line in use
which tells me that there just isn't anything connected to that port. I don't
know why but then I entered:
bmike1@1[bmike1]$ sudo cu -s 9600 -l /dev/ttyS2
Connected.
Cisco console system
CLI session with the switch is open.
To end the CLI session enter [Exit]
On Wednesday 05 January 2005 05:23, Mikey wrote:
> Do you do anything special to start the transfer of data with cu; or is it
> like minicom where you are supposed to hit the spacebar a few times and
> data transfers? I never got minicom working.
>
> On Tuesday 04 January 2005 12:52, Robert Ambrose wrote:
> > The 'ip l' command will show all links. Show is the default. FWIW, I'd
> > use 'ip a' because address shows everything link shows plus the IP
> > address. You first network link is probably your loopback interface.
> >
> > Ttys are not network interfaces per se. They are an interface to an RS
> > 232 device. ppp0 would be the network interface for a network link
> > connected via a RS 232 device (modem).
> >
> > On your switch issue: if you're trying to connect to a console port of
> > a switch, the cu command from the uucp package is the easiest. The
> > command 'cu -s 9600 -l /dev/tty0' (assuming you're using COM1 to connect
> > to your switch) should do the trick. If cu fails to connect due to
> > a permission problem, do a 'chmod 666 /dev/tty0'.
> >
> > HTH, rna
> >
> > On Mon, 3 Jan 2005, Mikey wrote:
> > > YOu know, I was thinking about what I've learned from the list over the
> > > past weeks about 'ip' and thought that it might be of some use with the
> > > topic at hand.
> > >
> > > First, lets test it on some known devices:
> > >
> > > bmike1@1[bmike1]$ ip link show eth0 (lucky guess thinking of eth0)
> > > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> > > link/ether 00:08:c7:ca:62:4b brd ff:ff:ff:ff:ff:ff
> > > bmike1@1[bmike1]$ ip link show ppp0
> > > 3: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast
> > > qlen 3 link/ppp
> > >
> > > Ok. So then it works w/o sudo.
> > >
> > > Now, will it work on the serial ports:
> > >
> > > bmike1@1[bmike1]$ ip link show ttyS0
> > > Device "ttyS0" does not exist.
> > > bmike1@1[bmike1]$ ip link show ttyS1
> > > Device "ttyS1" does not exist.
> > >
> > > I guess not.
> > > But wait a second; eth0 appears to be device 2 and ppp0 device 3: so,
> > > what is device 1.
> > >
> > > bmike1@1[bmike1]$ ip link show 1
> > > Device "1" does not exist.
> > > bmike1@1[bmike1]$
> > >
> > > Anyone know what I should do? How do I see what device '1' is, could
> > > that be the switch? I don't think so because eth0 and ppp0 are all
> > > internal devices. But what does that mean. They could also be external
> > > devices. Know what I mean? I bet device 1 is the scsi controller
> > >
> > > ---------------------------------------------------
> > > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > > To subscribe, unsubscribe, or to change you mail settings:
> > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change you mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)