# ser2net configuration file # # Each Serial port consists of a line in the following format: # # :::: # # TCP port: Can be a name (corresponding to /etc/services) or a number of the # TCP/IP port which accepts connections for this device. A port number # may be in the form [host,]port. If host is specified, the daemon # will bind the port only to the specified IP address. Otherwise it # will bind to all addresses on the machine. # # state: raw -> Enable the port and transfers all data as-is between the # port and the long. # rawlp -> Enable the port and transfer all input data to the device # where device is open without any termios settings. This # allows to use /dev/lpX devices and printers connected to # them. # telnet -> Enable the port and run the telnet protocol on it. # off -> Disable port from accepting connections (Use the control # Port to reenable it again). # # timeout: Time in seconds the daemon should wait before it disconnects the # connection to the port. If you set this to 0 then you will never # disconnect. # # device: The name of the device to connect to it in the form /dev/. # For your first serial port (COM1) use /dev/ttyS0 for your second # serial port (COM2) use /dev/ttyS1. # # options: Set operational parameters for the serial port. These parameters # could be: # 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 to set # the speed of the serial device. # EVEN, ODD, NONE to set the parity of the device. # 1STOPBIT, 2STOPBITS to set the number of stop bits. # 7DATABITS, 8DATABITS to set the number of data bits. # XONXOFF, -XONXOFF to turn on/off XON/XOFF support. # RTSCTS, -RTSCTS to turn on/off hardware flow control. # LOCAL, -LOCAL to turn on/off modem line monitoring. # HANGUP_WHEN_DONE, -HANGUP_WHEN_DONE to turn on/off modem control # line lowering when connection is done. # remctl to enable remote control of the serial port parameters via # RFC 2217. See the README for more info. # # You may also set a banner name as option if you wish a banner to # be printed when you log in to that port. If you ommit this option, # then no banner is printed. # # Note that the same device can be listed multiple times under different ports, # this allows the same serial port to have both telnet and raw protocols. # # A few examples: # # The most common way is to setup a port (e.g. 3001) waiting for telnet # connections which then connects to your first serial port (COM1). 3001:telnet:600:/dev/ttyS0:9600 8DATABITS NONE 1STOPBIT # Uncomment the following line to also enable a telnet connection to COM2. #3002:telnet:600:/dev/ttyS1:9600 8DATABITS NONE 1STOPBIT # Here an example by using a USB to Serial converter. #3003:telnet:35:/dev/ttyUSB0:9600 # The following example uses a banner which is shown when you log through # telnet. #3003:telnet:600:/dev/ttyS0:9600 mybanner # You can define one or more banners which then can be associated to any device. # Each banner is configured in one line but the banner text can span lines if # the last character on a line is '\'. The format of a banner is as follows: # BANNER::banner # # You can use the standard "C" \xxx characters like \n for newline or \t for # tab and so on, but you *must* use \r\n to start a new line. # # The following characters have a special meaning: # \d prints the device name # \p prints the TCP Port number # \s prints the serial parameters (eg. 9600N81 # # To use the banner you have to set it's name on the option field of the device. # Here a few banner examples: # #BANNER:mybanner:Welcome to ser2net TCP port \p\r\n # #BANNER:anotherbanner:This is ser2net TCP port \p device \d\r\n\ #Confucius said: \ #"In language, it is best to be clear \ #and say just enough to convey the meaning."\r\n