summaryrefslogtreecommitdiff
path: root/share
diff options
context:
space:
mode:
authorbrian <brian@cvs.openbsd.org>1999-05-12 10:03:57 +0000
committerbrian <brian@cvs.openbsd.org>1999-05-12 10:03:57 +0000
commit5e010b64474e3ab61413beae027f48be1609c1c7 (patch)
treee9550e9440915bdcfe059937a980326fc9dd8a96 /share
parentd1e4242b06e8535818a59bd49dc7c1387eb2dcd0 (diff)
Allow ``host:port/udp'' devices and support ``host:port/tcp'' as
being the same as the previous (still supported) ``host:port'' syntax for tcp socket devices. A udp device uses synchronous ppp rather than async, and avoids the double-retransmit overhead that comes with ppp over tcp (it's usually a bad idea to transport IP over a reliable transport that itself is using an unreliable transport). PPP over UDP provides througput of ** 1.5Mb per second ** with all compression disabled, maxing out a PPro/200 when running ppp twice, back-to-back. This proves that PPPoE is plausable in userland.... This change adds a few more handler functions to struct device and allows derivations of struct device (which may contain their own data etc) to pass themselves through the unix domain socket for MP. ** At last **, struct physical has lost all the tty crud ! iov2physical() is now smart enough to restore the correct stack of layers so that MP servers will work again. The version number has bumped as our MP link transfer contents have changed (they now may contain a `struct device'). Don't extract the protocol twice in MP mode (resulting in protocol rejects for every MP packet). This was broken with my original layering changes. Add ``Physical'' and ``Sync'' log levels for logging the relevent raw packets and add protocol-tracking LogDEBUG stuff in various LayerPush & LayerPull functions. Assign our physical device name for incoming tcp connections by calling getpeername(). Assign our physical device name for incoming udp connections from the address retrieved by the first recvfrom().
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions