Changes in debugnet.h

95ee2897 - sys: Remove $FreeBSD$: two-line .h pattern

Wed, 16 Aug 2023 17:54:11 +0000

sys: Remove $FreeBSD$: two-line .h patternRemove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ List of files: /freebsd-14.2/sys/net/debugnet.h

b498331b - netgdb: Fix netgdb double ack, print proxy address

Sat, 27 May 2023 02:48:14 +0000

netgdb: Fix netgdb double ack, print proxy address- Fixes netgdb's double ack- Moving ack responsibility to debugnet, decision to ack made by netdump/netgdb.- Finish responsibility moved to debugnet, new finish handler.- netgdb now prints the address to connect to in case the user doesn't have access to the proxy machine.Sponsored by: Dell EMCReviewed By: markj, bdrewery (earlier version)Differential Revision: https://reviews.freebsd.org/D40064 List of files: /freebsd-14.2/sys/net/debugnet.h

4d846d26 - spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD

Wed, 10 May 2023 15:40:58 +0000

spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of BSD-2-Clause.Discussed with: pfgMFC After: 3 daysSponsored by: Netflix List of files: /freebsd-14.2/sys/net/debugnet.h

053a24d1 - debugnet: Add ifnet accessor to set debugnet methods

Fri, 13 Jan 2023 16:30:58 +0000

debugnet: Add ifnet accessor to set debugnet methodsAs part of the effort to hide the internals of the ifnet struct, convertthe DEBUGNET_SET() macro to use an accessor instead of directly touchingthe methods member.Reviewed by: glebius (older version)Sponsored by: Juniper Networks, Inc.Differential Revision: https://reviews.freebsd.org/D38105 List of files: /freebsd-14.2/sys/net/debugnet.h

b2b1bb04 - debugnet: Fix a typo in a source code comment

Sun, 07 Aug 2022 14:07:01 +0000

debugnet: Fix a typo in a source code comment- s/paramaters/parameters/MFC after: 3 days List of files: /freebsd-14.2/sys/net/debugnet.h

dda17b36 - Implement NetGDB(4)

Thu, 17 Oct 2019 21:33:01 +0000

Implement NetGDB(4)NetGDB(4) is a component of a system using a panic-time network stack toremotely debug crashed FreeBSD kernels over the network, instead oftraditional serial interfaces.There are three pieces in the complete NetGDB system.First, a dedicated proxy server must be running to accept connections fromboth NetGDB and gdb(1), and pass bidirectional traffic between the twoprotocols.Second, the NetGDB client is activated much like ordinary 'gdb' andsimilarly to 'netdump' in ddb(4) after a panic. Like other debugnet(4)clients (netdump(4)), the network interface on the route to the proxy servermust be online and support debugnet(4).Finally, the remote (k)gdb(1) uses 'target remote :' (like anyother TCP remote) to connect to the proxy server.The NetGDB v1 protocol speaks the literal GDB remote serial protocol, anduses a 1:1 relationship between GDB packets and sequences of debugnetpackets (fragmented by MTU). There is no encryption utilized to keepdebugging sessions private, so this is only appropriate for localsegments or trusted networks.Submitted by: John Reimer (earlier version)Discussed some with: emaste, markjRelnotes: sureDifferential Revision: https://reviews.freebsd.org/D21568 List of files: /freebsd-14.2/sys/net/debugnet.h

e9c69625 - debugnet(4): Add optional full-duplex mode

Thu, 17 Oct 2019 20:25:15 +0000

debugnet(4): Add optional full-duplex modeIt remains unattached to any client protocol. Netdump is unaffected(remaining half-duplex). The intended consumer is NetGDB.Submitted by: John Reimer (earlier version)Discussed with: markjDifferential Revision: https://reviews.freebsd.org/D21541 List of files: /freebsd-14.2/sys/net/debugnet.h

fde2cf65 - debugnet(4): Infer non-server connection parameters

Thu, 17 Oct 2019 20:10:32 +0000

debugnet(4): Infer non-server connection parametersLoosen requirements for connecting to debugnet-type servers. Only require adestination address; the rest can theoretically be inferred from the routingtable.Relax corresponding constraints in netdump(4) and move ifp validation todebugnet connection time.Submitted by: John Reimer (earlier version)Reviewed by: markjDifferential Revision: https://reviews.freebsd.org/D21482 List of files: /freebsd-14.2/sys/net/debugnet.h

8270d35e - Add ddb(4) 'netdump' command to netdump a core without preconfiguration

Thu, 17 Oct 2019 19:49:20 +0000

Add ddb(4) 'netdump' command to netdump a core without preconfigurationAdd a 'X -s -c [-g ] -i ' subroutineto the generic debugnet code. The imagined use is both netdump, shown here,and NetGDB (vaporware). It uses the ddb(4) lexer, with some new extensions,to parse out IPv4 addresses.'Netdump' uses the generic debugnet routine to load a configuration andstart a dump, without any netdump configuration prior to panic.Loosely derived from work by: John Reimer Reviewed by: markjDifferential Revision: https://reviews.freebsd.org/D21460 List of files: /freebsd-14.2/sys/net/debugnet.h

7790c8c1 - Split out a more generic debugnet(4) from netdump(4)

Thu, 17 Oct 2019 16:23:03 +0000

Split out a more generic debugnet(4) from netdump(4)Debugnet is a simplistic and specialized panic- or debug-time reliabledatagram transport. It can drive a single connection at a time and iscurrently unidirectional (debug/panic machine transmit to remote serveronly).It is mostly a verbatim code lift from netdump(4). Netdump(4) remainsthe only consumer (until the rest of this patch series lands).The INET-specific logic has been extracted somewhat more thoroughly thanpreviously in netdump(4), into debugnet_inet.c. UDP-layer logic and up, asmuch as possible as is protocol-independent, remains in debugnet.c. Theseparation is not perfect and future improvement is welcome. SupportingINET6 is a long-term goal.Much of the diff is "gratuitous" renaming from 'netdump_' or 'nd_' to'debugnet_' or 'dn_' -- sorry. I thought keeping the netdump name on thegeneric module would be more confusing than the refactoring.The only functional change here is the mbuf allocation / tracking. Insteadof initiating solely on netdump-configured interface(s) at dumpon(8)configuration time, we watch for any debugnet-enabled NIC for linkactivation and query it for mbuf parameters at that time. If they exceedthe existing high-water mark allocation, we re-allocate and track the newhigh-water mark. Otherwise, we leave the pre-panic mbuf allocation alone.In a future patch in this series, this will allow initiating netdump frompanic ddb(4) without pre-panic configuration.No other functional change intended.Reviewed by: markj (earlier version)Some discussion with: emaste, jhbObjection from: mariusDifferential Revision: https://reviews.freebsd.org/D21421 List of files: /freebsd-14.2/sys/net/debugnet.h