Files
RASCSI/doc/piscsi-network-profile.8
Daniel Markstedt 485298ffe5 restore X68000 Host Bridge support
Restore the SCBR device as an X68000 Host Bridge, including the Human68k-compatible host file-system service and the bridge-specific SCSI message handlers. Back its Ethernet path with the TAP driver, derive a stable locally administered MAC address, preserve the driver minimum-frame/FCS expectations, and restrict received traffic to its own unicast frames and broadcasts.

Match the RASCTL/RASETHER/RASDRV bridge protocol that originated in the parent RaSCSI project: dispatch its non-standard message format on READ(10)/WRITE(10) (0x28/0x2a), with type, function, phase, and a three-byte byte count carried in the CDB. Advertise the legacy control channel required by RASCTL, translate its list and device-management commands to PiSCSI operations, and defer stop or system-shutdown requests until after the response is sent, while gating this insecure interface behind a new '-c disabled|media|full' runtime option. Preserve the type-1 Ethernet exchange used by RASETHER and the type-2, phased filesystem exchange used by RASDRV.

Register the device in the factory, protobuf API, controller transfer path, command-line tooling, device listings, and web UI. Share the explicit bridge and proxy-ARP topology workflow with DaynaPort so both adapters validate and use the same mode/interface pair.

Add build support for iconv where needed, extend unit coverage for device creation, RAS* protocol handling, CLI parsing, web attachment, and topology selection, and update the man pages and network-profile documentation for Host Bridge operation and its networking limits.
2026-09-01 00:52:00 +02:00

87 lines
2.7 KiB
Plaintext

.Dd August 30, 2026
.Dt PISCSI-NETWORK-PROFILE 8
.Os PiSCSI
.Sh NAME
.Nm piscsi-network-profile
.Nd manage PiSCSI network profiles on the Linux host
.Sh SYNOPSIS
.Nm
.Op Fl Fl dry-run
.Op Fl Fl console-acknowledge
.Cm apply bridge
.Ar ethernet-interface
.Nm
.Op Fl Fl dry-run
.Op Fl Fl console-acknowledge
.Cm apply proxyarp
.Ar wifi-interface
.Nm
.Op Fl Fl dry-run
.Op Fl Fl console-acknowledge
.Cm remove
.Cm bridge | proxyarp
.Sh DESCRIPTION
.Nm
creates or removes only the named NetworkManager connections and PiSCSI
configuration used by the DaynaPort and Host Bridge network adapters.
It is not a general installer and does not modify existing user connections,
routes, addresses, or firewall rules.
.Pp
The
.Cm bridge
profile creates the named
.Dq PiSCSI wired bridge
and
.Dq PiSCSI wired bridge port
NetworkManager connections, then activates the bridge.
It disables STP to avoid an unnecessary forwarding delay and pins the bridge
MAC address to the selected physical Ethernet interface, keeping it distinct
from the emulated client MAC address on the
.Pa piscsi0
TAP interface.
It is the protocol-complete host-side profile for a wired connection.
DaynaPort can use the complete Ethernet service it provides.
Host Bridge uses the same profile, but its native driver receives only its own
unicast frames and Ethernet broadcasts; it does not receive multicast traffic.
.Pp
The
.Cm proxyarp
profile records the selected Wi-Fi uplink in
.Pa /etc/piscsi/network.conf ,
reloads the PiSCSI runtime configuration, and disables the generic
.Pa dhcp-helper.service
to avoid a UDP/67 conflict with PiSCSI's DHCP relay.
It requires the separately installed
.Nm parprouted
and
.Nm dhcp-helper
programs.
Both adapters can use proxy ARP for IPv4 unicast and DHCP.
It is not an Ethernet bridge and does not support IPv6, AppleTalk, multicast,
mDNS, or other non-IP Ethernet traffic.
.Sh SAFETY
.Fl Fl dry-run
prints the complete plan without changing the system.
Applying or removing a profile requires root and NetworkManager. If
.Fl Fl console-acknowledge
is omitted, the command requires an interactive local terminal and an explicit
.Dq APPLY
response. Passing
.Fl Fl console-acknowledge
is explicit approval that skips the prompt.
Use a local console or another recovery path: changing a network profile can
interrupt connectivity.
.Pp
Legacy PiSCSI NAT/firewall rules are never removed automatically.
Remove them manually before selecting a supported profile.
.Sh EXAMPLES
.Bd -literal -offset indent
sudo piscsi-network-profile --dry-run apply bridge eth0
sudo piscsi-network-profile --console-acknowledge apply bridge eth0
sudo piscsi-network-profile --dry-run apply proxyarp wlan0
sudo piscsi-network-profile --console-acknowledge apply proxyarp wlan0
.Ed
.Sh SEE ALSO
.Xr piscsi 1 ,
.Xr scsictl 1