linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* need to identify slip interface in a pool (not subscribed to lkml)
@ 2020-02-18  3:29 Kent Dorfman
  0 siblings, 0 replies; only message in thread
From: Kent Dorfman @ 2020-02-18  3:29 UTC (permalink / raw)
  To: linux-kernel

Hey gents.

As is usually the case, engineering decisions were made before I came
on-board, and now I'm stuck dealing with plans that I had no input
into.

Anyway, company advertised to external customers that they could
connect their widgets to our system using plain ole uncompressed SLIP
over RS422 serial (four wire, no flow control, 115200bps)

Problem, as you may have guessed, is that since the lines are
statically allocated I need to be able to assign static IPs based on
the tty port they are using.  I haven't used a SLIP dialup since
mid-90s and from what I remember, the sl# link is dynamically
allocated based on the "next available" when the slattach command
handshakes with the other end.  This leaves me without knowing what
sl# interface to assign the IP number to.  The common use case was
always a single sl link over a dialup line, not 16+ different
statically allocated slip connections on a single server (with no end
user authentication to define the IP on a per-port basis)

What is my work-around?  How can I know which sl interface to
configure based on a particular tty serial link?

I'm not a LKML subscriber, so please CC me directly.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-02-18  3:30 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-18  3:29 need to identify slip interface in a pool (not subscribed to lkml) Kent Dorfman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).