Age | Commit message (Collapse) | Author |
|
we're about to send. Should a bug on big-endian LP64 archs reported by
James MacMahon (jwm at operand dot ca). ok millert@
|
|
|
|
Move address assignment to process context. This uses a workq at
present, conversion to taskq is on my todo list (discussed with dlg).
Instead of rummaging around in sockaddr_in6 structs, use the proper
netinet6 APIs to configure addresses.
Deal with IFID collisions instead of ignoring them. The whole point of
IPv6CP is to avoid IFID collisions. Use arc4random() during IFID generation.
Assign destination address to /128 point-to-point links.
tested by me and sthen with pppoe(4)
ok sthen
|
|
network to presentation format to inet_ntop().
The few remaining functions will be soon converted.
ok mikeb@, deraadt@ and moral support from henning@
|
|
ok sthen
|
|
global variables to in6.h.
ok deraadt@
|
|
- despite the name, ntohl returns uint32_t, not long
- also fix some %d into %u
|
|
This is another ABI break but no port rely on them as verified by naddy@.
ok claudio@, mikeb@, henning@
|
|
|
|
to only include what is really needed. In particular stop including
a "struct ifnet" and move kernel-only definition into the proper #if
dance.
While here remove the unused spppinfo() from ifconfig.
ok guenther@, sthen@, mikeb@
|
|
Reported by naddy@
|
|
structure rather than doing various M_WAITOK allocations during
the *attach() functions, we always rely on them anyway.
ok mikeb@, uebayasi@
|
|
unconditionally for SIOCSIFADDR.
ok bluhm@, henning@
|
|
.h files to pull it in, if needed
ok tedu
|
|
|
|
looks fine reyk@ ok mikeb@
|
|
|
|
LEVAI Daniel, diagnosed by matthew@, original diff from RD Thrush, cleaned
up by me with feedback from mikeb@. OK mikeb dcoppa deraadt
|
|
You should use the proper queues via pf instead. ok phessler@ henning@
|
|
compatible equipment provided that the physical interface and other layer 2
devices involved support and are configured to use jumbo frames.
Manpage to follow; typical use is to request 1500 MTU for pppoe, this
requires 1508+ MTU on the physical interface, e.g. "ifconfig em0 mtu 1508;
ifconfig pppoe0 mtu 1500". Known to be usable in the UK with some ISPs
(e.g. aaisp) using BT FTTC backhaul.
From Matt Dainty, originally based on support in NetBSD, changed to
decouple pppoe from physical interface MTU. Tested with UK FTTC by Matt,
no regressions on my standard UK ADSL setup or yasuoka@'s setup (in Japan,
NTT uses 1452 byte MTU for PPPoE and 1500 byte MTU for IPv6 on the same
network).
ok yasuoka@
|
|
this in my monster diff and wondered that i hadn't put that in already...
claudio ryan ok
|
|
the same, ok'd with IFQ_PURGE with happens to break on altq kernels by
claudio, ryan and bluhm
|
|
and not IFQ_IS_EMPTY, the former doesn't get overloaded with altq-specific
stuffz. original oks from claudio and ryan and bluhm, i take the liberty
to assume the oks for this fixed version
|
|
|
|
|
|
make sppp_flush use IFQ_PURGE instead of handrolling the same making
assumptions about ifqueue internals. ok ryan claudio
|
|
confirmed to fix paul stoeber's crash. ok deraadt sthen
|
|
spotted by clang, ok matthew@
|
|
essentially identical; the only difference being that m_pullup2 is
capable of handling mbuf clusters, but called m_pullup for shorter
lengths (!).
testing dlg@ ok claudio@
|
|
addresses from process context by scheduling a work queue.
Fixes an assertwaitok panic. ok henning
|
|
explicit_bzero() where required
ok markus mikeb
|
|
is new or an already existing one. for existing ones, call ifa_del first
tested by many as part of a larger diff, ok claudio dlg krw sthen
|
|
devices is a bad idea. The problem is that the default route per se works
but PMTU is unable to clone host routes because the gateway is unreachable.
Fix sppp(4) so that it walks the routing table and fixes the gateways.
This makes PMTU work again. Diff tested by weerd@ and markus@ (older version)
for a long time.
|
|
timingsafe_bcmp().
ok deraadt@; committed over WPA.
|
|
The ones found in gnu/ left out by intention.
ok jmc
|
|
Another thing found by Gleydson Soares.
|
|
tables on top of a rdomain) but until now our code was a crazy mix so that
it was impossible to correctly use rtables in that case. Additionally pf(4)
only knows about rtables and not about rdomains. This is especially bad when
tracking (possibly conflicting) states in various domains.
This diff fixes all or most of these issues. It adds a lookup function to
get the rdomain id based on a rtable id. Makes pf understand rdomains and
allows pf to move packets between rdomains (it is similar to NAT).
Because pf states now track the rdomain id as well it is necessary to modify
the pfsync wire format. So old and new systems will not sync up.
A lot of help by dlg@, tested by sthen@, jsg@ and probably more
OK dlg@, mpf@, deraadt@
|
|
ok claudio@
|
|
Encapsulated pppoe packets are moved into the rdomain of the physical interface
because it is possible that a pppoe(4) interface is in a different rdomain
then the physical interface.
OK reyk@
|
|
|
|
use M_CANWAIT throughout
ok sthen canacar claudio
|
|
Tested by many, thanks.
Put it in" deraadt@
|
|
and fix typo while here.
ok canacar@
|
|
can't be used with va_start. change it to u_int.
ok miod@
|
|
ok deraadt@
|
|
OK canacar@ some time ago
|
|
Prevents hangs as reported and tested by James Stark, PR:5795, ok henning@
|
|
From NetBSD
ok canacar@
|
|
they point to the same address, this is more readable. ok claudio@
|
|
must be able to handle as MRU but while testing pppoe(4) against a pppoe(8)
server I figured out that pppoe(8) insists on a MRU 1492. Because of this
we allow the offered MRU to be between PP_MIN_MRU and PP_MAX_MRU especially
because the MRU is not used at all as long as it is smaller then PP_MAX_MRU.
OK canacar@
|