A few serial related questions ...

1) Does anyone know of any sl(4) or slattach(8) behaviour changes in 1.6?
(I see some sl source looks to be changed.)

On one i386 system (1.5.3) I run:
 slattach -l -h -s 115200 /dev/tty00
 ifconfig sl0 192.168.0.111 192.168.0.110
 route add default 192.168.0.110

And then on the i386 router (1.6 was 1.5.x) I run:
  slattach -l -h -s 115200 /dev/tty00
  ifconfig sl0 192.168.0.110 192.168.0.111
  sysctl -w net.inet.ip.forwarding=1
  arp -s 192.168.0.111 00:00:c0:4d:76:db pub

This has worked for a couple years. But since I upgraded the second system
to 1.6, it doesn't work.

No errors, just no traffic. netstat tells me that it is receiving traffic
when I ping it, but nothing returns:

sl0*  296   <Link>                               57722          0

I know the serial (non-slip) connection works fine, because I can run a
getty on it and then login with cu just fine.

2) How can I talk back and forth with cu(1)?

I simply want to run cu on both sides and be able to chat back and forth.
I tried "cu -l /dev/tty00 -h" on both sides and various other options,
but all I see on receiving end is junk (high ascii) characters. Any
suggestions?

3) Is there any tool like pmad (port monitor) or ttyadm that can listen to
tty and then run the login(1) as needed? (A stand-alone getty?)

I tried running "/usr/libexec/getty std.9600 tty00", but once I connected
from remote side, the login(1) was then started in the console
(/dev/ttypc) that I was running the getty in instead of over the tty00.

Or is the only (or correct) way just to edit ttys and send HUP to init?

   Jeremy C. Reed
   http://bsd.reedmedia.net/