| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Add IFCAP_VLAN_HWOFFLOAD to signal hardware like vio(4) can handle
checksum or TSO offloading with inline VLAN tags.
tested by Mark Patruck, sf@ and bluhm@
ok sf@ and bluhm@
|
|
|
|
ok tb@
|
|
ok jmc@
|
|
this can be used to add static entries on interfaces like vxlan(4).
|
|
|
|
This makes is possible to build the base system with a C99 compiler.
OK deraadt@ mvs@
|
|
Large Receive Offload allows to receive aggregated packets larger
than the MTU. Receiving TCP streams becomes much faster. As the
network hardware is not aware whether a packet is received locally
or to be forwarded, everything is aggregated. In case of forwarding
it is split on output to packets not larger than the original
packets. So path MTU discovery should still work. If the outgoing
interface supports TSO, the packet is chopped in hardware by TCP
Segmentation Offload.
Currently only ix(4) and lo(4) devices support LRO, and ix(4) is
limited to IPv4 and hardware newer than the old 82598 model. If
the interface is added to a tpmr(4), bridge(4) or veb(4), LRO is
automatically disabled. All ix(4) devices support outgoing TSO for
IPv4 and IPv6. Enabling LRO on lo(4) automatically enables TSO and
TCP packets larger than the MTU pass the loopback interface.
LRO can be turned off per interface with ifconfig -tcplro.
OK jan@
|
|
Noticed by Bradley Latus
Diff from Jane Johansson
OK tb
|
|
more consistent.
discussed with jan@ mvs@ chris@ claudio@ dlg@
|
|
"wgdescr[iption] foo" to label one peer (amongst many) on a wg(4) interface,
"-wgdescr[iption]" or "wgdescr ''" to remove the label, completely analogous
to existing interface discriptions.
Idea/initial diff from Mikolaj Kucharski (OK sthen)
Tests/prodded by Hrvoje Popovski
Tweaks/manual bits from me
Feedback deraadt sthen mvs claudio
OK claudio
|
|
This diff introduces separate capabilities for TCP offloading. We split this
into LRO (large receive offloading) and TSO (TCP segmentation offloading).
LRO can be turned on/off via tcprecvoffload option of ifconfig and is not
inherited to sub interfaces.
TSO is inherited by sub interfaces to signal this hardware offloading capability
to the network stack.
With tweaks from bluhm, claudio and dlg
ok bluhm, claudio
|
|
Suggested by Hrvoje Popovski.
ok phessler@
|
|
ok david@
|
|
ok david@
|
|
ok deraadt@
|
|
ok miod@ millert@
|
|
with tweaks from claudio and deraadt
ok claudio, bluhm
|
|
|
|
These ifconfig commands are supported by veb(4) but were undocumented:
deladdr flushrule maxaddr rule rulefile static timeout up
As was done before, copy relevant prose from the BRIDGE section.
ok jmc@
|
|
Found by Mathias Koehler, thanks!
|
|
remove some redundant info regarding netstat -r from ipcomp/ipsec
feedback claudio sthen
ok claudio kn sthen
|
|
Two spots in ifconfig print the signal strength, one for the "ieee80211: "
line and one for each SSID in scan output.
Only the former checks nr_rssi, which is not needed as nr_max_rssi alone
indicates whether the driver reports signal strength in percentage or dBm.
Zap the nr_rssi check to simplify; "worst case" we display 0% or 0dBm
instead of nothing.
Feedback OK stsp
|
|
an ugly line split on narrower terminals
- in usage(), match the output
|
|
cloned (virtual) interfaces are skipped, and if the MAC is on more
than 1 interface, no answer either. The mac must be in same format
as the ifconfig lladdr output (complete lowercase with :)
idea from florian, ok afresh1
|
|
ifconfig(8) output can get too long when always printing `wgpeers' for all
wg(4) interfaces, so omit it output is requested and/or output is limited
to the interface group "wg" or a specific interface "wgX".
No install media size change as wireguard code is under #ifndef SMALL.
Diff from Mikolaj Kucharski <mikolaj AT kucharski DOT name>
makes Hrvoje Popovski happy
manual bits from jmc
OK sthen
|
|
|
|
|
|
disabled by default. Also add a tso option to ifconfig(8) to enable and
disable this feature.
ok deraadt
|
|
Input and OK dlg@ and jmc@
|
|
|
|
ioctls should use dedicated names for their structs, but SIOCG80211ALLCHANS
duplicated struct ieee80211_channel. We cannot make changes to the kernel's
version of ieee80211_channel while an ioctl is squatting on the struct name.
Helpful guidance from deraadt@
Tested in a ports bulk build by sthen@, and tested by Mikhail.
ok sthen@
|
|
interfaces like vxlan and nvgre have bridges inside them and respond
to bridge ioctls, but they are still interfaces that handle l3
traffic so the mtu means something on them. if we don't want bridge
to show an mtu, that can be done by bridge(4) instead of having
ifconfig make assumptions like this.
noticed by jason tubnor
ok deraadt@ claudio@
|
|
from caspar schutijser
|
|
Systems without RTC are likely to boot with wrong time, but pppoe(4) used
microtime(9) anyway to remember when a new session began.
(In)adequately, ifconfig(8) used gettimeofday(2) and calculated the
difference between two absoloute dates to infer the PPPoE session duration.
This goes off the rails if the wall clock jumps in between, e.g. due to NTP
kicking in.
Use getmicrouptime(9) and clock_gettime(2)/CLOCK_BOOTTIME instead to rely
on the monotonically increasing system uptime instead to fix this.
Reported and tested by Peter J. Philipp <pjp AT delphinusdns DOT org> on
some octeon box without RTC.
I've seen this on a Edgerouter 4 as well (2m uptime, 19d session).
OK claudio
|
|
Behaviour is similar to that of umb(4).
OK kn@
|
|
OK deraadt
|
|
OK deraadt@ patrick@
|
|
There since 1998, probably dead long before.
"I am sure swabips died before you were born." deraadt
|
|
|
|
Fail early and exit non-zero immediately instead of indicating success and
possibly carrying the next ifconfig command.
Found at install when wifi interfaces are reset with "-nwid -nwkey -wpa":
Which network interface do you wish to configure? (or 'done') [bse0] bwfm0
ifconfig: SIOCS80211NWKEY: Operation not supported by device
Access point? (ESSID, 'any', list# or '?') [any] 2
Security protocol? (O)pen, (W)EP, WPA-(P)SK [O]
bwfm(4) currently does not support WEP.
OK stsp
|
|
out of date: remove it (sthen) and add a pointer to -C (dlg);
ok sthen
|
|
ok benno@ dlg@
|
|
|
|
OK deraadt
|
|
ok deraadt@
|
|
|
|
fails to report the path that the failure occured on. Suggested by
deraadt@ after some tech discussion.
Work done and verified by Ashton Fagg <ashton@fagg.id.au>
ok deraadt@ semarie@ claudio@
|
|
Previously only the provider's display name was used. The text used depends
on how the SIM is configured and not just on the network in use (for example,
an MVNO SIM on another network will often display the MVNO's name rather
than that of the underlying network).
I have a SIM that roams to any network in my country - whichever network
it roams onto, the display name is the same, so you can't tell which
network you're really using. By printing the provider ID (in GSM-land this
is MCC+MNC) it's easy to lookup and check this.
As the provider was printed on the ifconfig line also showing subscriber-id
and ICCID it was already a bit long, and adding the provider-id there is
a bit too much, so move it to the output line showing APN, now looking like
: subscriber-id 2400xxxxxxxxxxx ICC-id 8946203xxxxxxxxxxxxx
: device EM7455 IMEI 01458xxxxxxxxxx firmware SWI9X30C_02.24.0
: APN key provider Tele2 IoT provider-id 23420
|
