| PISCSI-NETWORK-PROFILE(8) | System Manager's Manual | PISCSI-NETWORK-PROFILE(8) |
NAME
piscsi-network-profile —
manage PiSCSI network profiles on the Linux host
SYNOPSIS
piscsi-network-profile |
[--dry-run]
[--console-acknowledge] apply
bridge ethernet-interface |
piscsi-network-profile |
[--dry-run]
[--console-acknowledge] apply
proxyarp wifi-interface |
piscsi-network-profile |
[--dry-run]
[--console-acknowledge]
remove bridge |
proxyarp |
DESCRIPTION
piscsi-network-profile 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.
The bridge profile creates the named
“PiSCSI wired bridge” and “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 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.
The proxyarp profile records the selected
Wi-Fi uplink in /etc/piscsi/network.conf, reloads
the PiSCSI runtime configuration, and disables the generic
dhcp-helper.service to avoid a UDP/67 conflict with
PiSCSI's DHCP relay. It requires the separately installed
parprouted and 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.
SAFETY
--dry-run prints the complete plan without
changing the system. Applying or removing a profile requires root and
NetworkManager. If --console-acknowledge is omitted,
the command requires an interactive local terminal and an explicit
“APPLY” response. Passing
--console-acknowledge is explicit approval that
skips the prompt. Use a local console or another recovery path: changing a
network profile can interrupt connectivity.
Legacy PiSCSI NAT/firewall rules are never removed automatically. Remove them manually before selecting a supported profile.
EXAMPLES
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
SEE ALSO
| August 30, 2026 | PiSCSI |
