-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathportshare-devices
37 lines (34 loc) · 1.46 KB
/
portshare-devices
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
#
# /etc/portshare-devices
#
# Entry Syntax:
#
# devname:cmtype:cmname:physport:type:options
#
# where :
# devname -> Device full pathname
# rastype -> Console Server type (cm4008 or CM4116 or CM4148)
# rasname -> Console Server host name or IP address
# physport -> Physical port number on Console Server
# type -> Server type : rfc2217 or socket (raw TCP)
# opts -> per-port interface options (optional)
#
# To connect via a secure ssh tunnel, use the '-P' parameter as part
# of "opts", and give the TCP port number used for the local end of
# the tunnel. e.g. "-P 22222" will attempt to connect to local TCP
# port 22222. Also set the rasname to "localhost". Note: The ssh tunnel
# must already be setup for this to work.
# Example 1: Connect to port 1 on a 48 port Console Server
# at IP address 10.111.254.1, using RFC2217
#/dev/otty01:cm4148:10.111.254.1:1:rfc2217
# Example 2: Connect to port 8 on a 8 port Console Server
# at IP address 10.111.254.2, using RFC2217
#/dev/otty02:cm4008:10.111.254.2:8:rfc2217
# Example 3: Create an ssh tunnel from localhost to an remote console
# server. This tunnel connects to serial port 3 on the console manager.
# and uses rfc2217. The rfc2217 TCP port base on the remote console server is set
# to 9000. The local TCP port used for the tunnel is 12345.
# ssh -L 12345:10.111.254.3:9003 <username>@10.111.254.3 -N
#
# Now use this tunnel to make the connection:
#/dev/otty03:cm4008:localhost:3:rfc2217:-P 12345