Bugs surrounding serial access on 1.2.0 RCs


#1

So there are a number of bugs related to serial port access on the current RCs. I found this because I was trying to get something faster than 9600 rolling over a serial console.

First off, as stock configured:

vyos@vyos# show system console
 device ttyS0 {
     speed 9600
 }
[edit]
vyos@vyos# ps ax | grep agetty
 2296 ttyS0    Ss+    0:00 /sbin/agetty --keep-baud 9600 ttyS0 vt102

Bug #1. Changing the speed doesn’t kill and restart the process. After the change, the speed is still 9600.

 vyos@vyos# set system console device ttyS0 speed 115200
 [edit]
 vyos@vyos# commit
 [edit]
 vyos@vyos# ps ax | grep agetty
  3654 ttyS0    Ss+    0:00 /sbin/agetty --keep-baud 9600 ttyS0 vt102

This is fixed by a delete:

vyos@vyos# delete system console device ttyS0
[edit]
vyos@vyos# commit
[ system console device ttyS0 ]
Warning: Access to system console is unconfigured

And reconfigure:

[edit]
vyos@vyos# set system console device ttyS0 speed 115200
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# ps ax | grep agetty
 3937 ttyS0    Ss+    0:00 /sbin/agetty --keep-baud 115200 ttyS0 vt102

Bug #2. This actually doesn’t even matter. Until a reboot, the port is stuck at 9600 despite what agetty says. Took me forever to figure out what was going on (I figured I had a broken cable), until I tried reconnecting at the original 9600 speed, which worked.


#3

@kroy changing the speed only works on next reboot.
(should state that in help in cli)
If you restart getty it does a forced login promt, so if you commit your session is gone and the commit is not done.


#4

Oops. Reading is hard. Thanks :slight_smile:


#5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.