| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
by buffer overflow.
Submitted by: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
|
|
|
|
| |
Submitted by: Mike Haro
|
|
|
|
| |
Problem reported by: Amedeo Beck Peccoz <gea@gressoney.it>
|
| |
|
| |
|
|
|
|
|
| |
recursion by doing something like ``down'' or ``quit all''
in ppp.linkdown.
|
|
|
|
| |
Requested by: Michael Heitmeier <MICHAEL_HEITMEIER@HP-Germany-om12.om.hp.com>
|
|
|
|
|
|
|
|
|
| |
mode by padding out the ``struct device'' to the maximum
device size.
Bump the ppp version number to indicate the transfer format
change.
This should make MP over tty and udp devices functional again.
|
|
|
|
|
|
|
|
|
| |
sizeof(ifr->ifr_addr) for the variable length field ifr->ifr_addr.sa_len.
Otherwise the increment will be wrong in certain cases.
Obtained from: Whistle source tree
For the record: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> suggests
SIOCGIFCONF should be dropped in favor of a sysctl mechanism.
|
|
|
|
|
|
|
|
|
| |
sizeof(ifr->ifr_addr) for the variable length field ifr->ifr_addr.sa_len.
Otherwise the increment will be wrong in certain cases.
Obtained from: Whistle source tree
For the record: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> suggests
SIOCGIFCONF should be dropped in favor of a sysctl mechanism.
|
|
|
|
| |
OK'ed by: jkh,rnordier
|
|
|
|
|
| |
lines as the pseudo-device checking. Previously 'device xyz0' would have
been silently accepted without comment.
|
|
|
|
|
|
|
| |
having different speed links in a bundle. This would manifest itself
by having the link occasionally hang, but revive when a new connection
is made....
Make ``show mp'' a bit prettier.
|
|
|
|
| |
and that font files can be specified in /etc/rc.conf[.local].
|
|
|
|
|
| |
"ps/2" protocol types, and that serial mouse protocols shouldn't be
specified for these mice.
|
|
|
|
| |
for the sign bit for roller movement!
|
| |
|
|
|
|
| |
usage message.
|
|
|
|
|
|
|
|
| |
o Show more information about missing MP fragments in ``show mp''.
o Do away with mbuf_Log(). It was showing mbuf stats twice on
receipt of LCP/CCP/IPCP packets.... ???!!?
o Pre-allocate a bit extra when creating LQR packets to avoid having
to allocate another mbuf in mbuf_Prepend().
|
|
|
|
|
|
| |
page for details. This allows MP over non-tty devices where
the original ppp process must not exit (such as sshd-spawned
ppp sessions).
|
|
|
|
|
| |
Adjust the base physical device name correctly after a link
transfer (allowing correct multilink callbacks).
|
|
|
|
| |
characters at the end of the line in hexdump style.
|
|
|
|
|
| |
will result in the rules being updated any time MYADDR
or HISADDR change.
|
|
|
|
| |
filters any time either value changes.
|
|
|
|
| |
Submitted by: Philippe Charnier
|
|
|
|
|
| |
mp_Assemble().
Leak spotted by: louqi
|
|
|
|
| |
PR: docs/10378
|
|
|
|
| |
with an out-by-one-memcpy.
|
| |
|
|
|
|
| |
remove a few extraneous assignments.
|
|
|
|
|
| |
case ppp is abending and hasn't called physical_Offline()
already.
|
| |
|
|
|
|
|
|
| |
up with the correct device type.
Reassign the correct tcpdevice or execdevice after transfering
a link in MP server mode.
|
| |
|
| |
|
|
|
|
|
| |
PR: bin/10904
Submitted by: Ben Smithurst <ben@scientia.demon.co.uk>
|
| |
|
|
|
|
|
|
|
| |
- Mention that the 6Mbps turbo adapters are supported in HARDWARE.TXT
and RELNOTES.TXT and the wi.4 man page
- Mention turbo adapters in the wicontrol.8 man page and provide a
complete table of available transmit speed settings
|
| |
|
|
|
|
|
| |
machines. Negative pll offset values were printed as large positive
numbers.
|
| |
|
|
|
|
|
|
| |
time.
Submitted by: Rémy Card <Remy.Card@csi.uvsq.fr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ADMtek AL981 "Comet" chipset. The AL981 is yet another DEC tulip clone,
except with simpler receive filter options. The AL981 has a built-in
transceiver, power management support, wake on LAN and flow control.
This chip performs extremely well; it's on par with the ASIX chipset
in terms of speed, which is pretty good (it can do 11.5MB/sec with TCP
easily).
I would have committed this driver sooner, except I ran into one problem
with the AL981 that required a workaround. When the chip is transmitting
at full speed, it will sometimes wedge if you queue a series of packets
that wrap from the end of the transmit descriptor list back to the
beginning. I can't explain why this happens, and none of the other tulip
clones behave this way. The workaround this is to just watch for the end
of the transmit ring and make sure that al_start() breaks out of its
packet queuing loop and waiting until the current batch of transmissions
completes before wrapping back to the start of the ring. Fortunately, this
does not significantly impact transmit performance.
This is one of those things that takes weeks of analysis just to come
up with two or three lines of code changes.
|
| |
|
|
|
|
|
|
| |
for some.
Submitted by: Jack O'Neill <jack@germanium.xtalwind.net>
|
|
|
|
| |
Submitted by: Roger Hardiman <roger@cs.strath.ac.uk>
|
|
|
|
|
|
| |
that we lock the device *before* we open it.
We still open the device only once - and then ask all
our handlers if they know how to handle it.
|
| |
|
| |
|
| |
|