Date: Fri, 22 Dec 2000 14:38:54 -0500 From: Bob Johnson <bob@eng.ufl.edu> To: hjagnew@mba1.mba-consulting.com Cc: questions@freebsd.org Subject: Re: dial in question REVISED Message-ID: <3A43ADCE.10D08D7C@eng.ufl.edu>
next in thread | raw e-mail | index | archive | help
> > > Date: Fri, 22 Dec 2000 12:44:22 -0500 (EST) > From: "H. Jared Agnew" <hjagnew@mba1.mba-consulting.com> > Subject: dial in question REVISED > > I'm so sorry to re send this question but I figured it would save maybe > one or two people the time of replying. In the original e-mail I included > the incorrect gettytab and ttys file. Thanks again for any help. > > Setup : > > FreeBSD -- 4.2 Stable 12/21/00 i386 > /dev/ttyd0 -- SB Modem Blaster 56K II > /dev/ttyd1 -- SB Modem Blaster 56K II > /dev/gettytab -- included > /dev/ttys -- included > > Problem : > > I'm using `ppp` on /dev/cuaa1 (/dev/ttyd1) to dial in to > /dev/ttyd0. ttyd0 picks up and talks with ttyd1, and seems > to establish a connection. ttyd0 tells ttyd1 that it has connected > at what ever speed ttyd1 asks for (ie "CONNECT 9600"). When > I use `watch` to look at what is going on with ttyd0, it shows > the usual login prompt. However on ttyd1 all I see is the "CONNECT" > message and then garbage. When I type anything in `ppp` (ttyd1) > it shows up as garbage on both the `watch` of ttyd0 and in `ppp` > of ttyd1, but it is not the same garbage. The modems are identical > and have identical register settings save for the answer register. > Thanks for any help you might give. > [...] I think the "CONNECT 9600" you are seeing is the modem connected to ttyd1 reporting the serial port speed at which it is connected, which is of course the speed of ttyd1, not ttyd0. Some modems by default report their serial port speed, not their carrier speed. > # $FreeBSD: src/etc/etc.i386/ttys,v 1.8 2000/01/29 12:18:03 obrien Exp $ > # @(#)ttys 5.1 (Berkeley) 4/17/89 > # > # This file specifies various information about terminals on the system. > # It is used by several different programs. Common entries for the > # various columns include: > # > # name The name of the terminal device. > # > # getty The program to start running on the terminal. Typically a > # getty program, as the name implies. Other common entries > # include none, when no getty is needed, and xdm, to start the > # X Window System. > # > # type The initial terminal type for this port. For hardwired > # terminal lines, this will contain the type of terminal used. > # For virtual consoles, the correct type is cons25. Other > # common values include network for network connections on > # pseudo-terminals, dialup for incoming modem ports, and unknown > # when the terminal type cannot be predetermined. > # > # status Must be on or off. If on, init will run the getty program on > # the specified port. If the word "secure" appears, this tty > # allows root login. > # > # name getty type status comments > # > # If console is marked "insecure", then init will ask for the root password > # when going to single-user mode. > console none unknown off secure > # > ttyv0 "/usr/libexec/getty Pc" cons25 on secure > # Virtual terminals > ttyv1 "/usr/libexec/getty Pc" cons25 on secure > ttyv2 "/usr/libexec/getty Pc" cons25 on secure > ttyv3 "/usr/libexec/getty Pc" cons25 on secure > ttyv4 "/usr/libexec/getty Pc" cons25 on secure > ttyv5 "/usr/libexec/getty Pc" cons25 on secure > ttyv6 "/usr/libexec/getty Pc" cons25 on secure > ttyv7 "/usr/libexec/getty Pc" cons25 on secure > ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure > # Serial terminals > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. > ttyd0 "/usr/libexec/getty VH57600" dialup on > #ttyd0 "/usr/libexec/getty std.9600" dialup off secure > ttyd1 "/usr/libexec/getty std.9600" dialup off secure > ttyd2 "/usr/libexec/getty std.9600" dialup off secure > ttyd3 "/usr/libexec/getty std.9600" dialup off secure > # Pseudo terminals > ttyp0 none network [...etc.] Your ttyd0 and ttyd1 are set to different speeds. I think this would work if they were both set to speeds as fast as or faster than the modem carrier speed (56K), but I suspect that in this case one of the modems is becoming confused about what speed it should be using, i.e. sending data at one speed but expecting to receive it at another. Try setting both serial ports to the same speed and see what happens. I'd use 115200 to take advantage of whatever compression the modems can accomplish. If you are using ppp, you may also need to pay attention to the speed set in /etc/ppp/ppp.conf. - Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A43ADCE.10D08D7C>