View Single Post
  #4   (View Single Post)  
Old 13th May 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,131
Default

The error message mentions /dev/ttyd0, which is a so-called call-in port. From http://www.freebsd.org/doc/en_US.ISO...ok/serial.html
Quote:
In FreeBSD, you access each serial port through an entry in the /dev directory. There are two different kinds of entries:
  • Call-in ports are named /dev/ttydN where N is the port number, starting from zero. Generally, you use the call-in port for terminals. Call-in ports require that the serial line assert the data carrier detect (DCD) signal to work correctly.

  • Call-out ports are named /dev/cuadN. You usually do not use the call-out port for terminals, just for modems. You may use the call-out port if the serial cable or the terminal does not support the carrier detect signal.

Note: Call-out ports are named /dev/cuaaN in FreeBSD 5.X and older.

If you have connected a terminal to the first serial port (COM1 in MS-DOSĀ®), then you will use /dev/ttyd0 to refer to the terminal. If the terminal is on the second serial port (also known as COM2), use /dev/ttyd1, and so forth.
Can you try another cable? Does the same problem occur when you use another FreeBSD box as terminal (using tip or cu?

Or try to use 3wire.9600 instead of std.9600 in the "/etc/ttys" file as recommended in the FreeBSD handbook (24.3.3 Troubleshooting Your Connection)
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote