Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Feb 1998 08:29:36 +0100 (CET)
From:      Andrzej Bialecki <abial@nask.pl>
To:        freebsd-isp@FreeBSD.ORG
Subject:   Working examples of dialin server
Message-ID:  <Pine.NEB.3.95.980213080053.18283A-100000@korin.warman.org.pl>

next in thread | raw e-mail | index | archive | help
Hi!

As some of you know, I'm preparing the next release of PicoBSD (one floppy
version of FreeBSD). I am releasing also the tools that allow to build
your own version, with your own set of programs and utilities. Standard
distribution contains two basic types of the floppy: one is intended for
dialup access, the second is intended as simple router replacement. Each
type of floppy has editable configuration (editable /etc on the floppy),
but after initial startup is unmounted and can be removed. This is IMHO
important characteristic, as it makes the floppy almost read-only, while
still allowing to change its configuration without rebuilding.

I'd like to add the third pre-canned configuration: dialin server. I'd
like it to cover the most common case (which is...?), using the most
common solutions (which are...?), with hooks to add the less common but
important features (which are....?). :-))

Unfortunately, as you can see above, my experience in this particular area
is nil.

I am sure some of you have already gained this experience, and could
perhaps help me with the following:

* I need a couple of working examples of dialin server, including relevant
  pieces of various config files (I know, I could study man pages, and
  I will, but with my experience in this the risk of screwing something 
  would be too big)
* I need answers for the above questions: what is the most common case of
  a small, beginning ISP? What hardware and software configuration would
  be most appropriate here? (I know this is highly relative, but some
  opinions would help me to decide what configuration to support
  out-of-the-box)
* which way should I go: include ijppp or kernel PPP by default? Include
  support for SLIP?
* should I leave getty by default or use mgetty instead?
* should I include gated instead of routed by default?
* should I include support for multiport comm cards (which ones?), or
  leave it as optional?
* Hmmm.. suport for RADIUS and/or TACACS+ (is there any?)
* and many, many more issues, which I'm probably unaware of at the
  moment... :-))

For those of small faith :-)  - probably _all_ of the above I could fit on
the floppy together, but I'd rather make the best use of space on it and
not include things which are rarely used.

I'd be very grateful if someone can share his knowledge with me - I hope
it will benefit many others later. Thanks in advance.

Andrzej Bialecki

PS. This one thing withholds the release now. The rest of things is ready,
and it works MUCH better than the previous release.

---------------------+---------------------------------------------------------
abial@warman.org.pl  | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") }
Research & Academic  | "Be open-minded, but don't let your brains to fall out."
Network in Poland    | All of the above (and more) is just my personal opinion.
---------------------+---------------------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.980213080053.18283A-100000>