DaynaPORT connectivity problem

[nybl]

Hey, firstly thanks for all the hard work on piscsi, it's much appreciated. I hope you might help with getting the DaynaPort interface working on an SE/30. I'm sure just missing something, so please bear with me, I'm not a network guy.

My setup is an SE/30 with 16MB running System 7.5.5. I have a fullspec RaSCSI with stock 25.12.01 PISCSI running on a Pi Zero W (wifi / no ethernet) with PiOS version 2025-12-04. All the normal piscsi mounting of drives etc is working fine through the web UI and I can ssh onto the Pi over wifi. The pi is getting its IP address from my router's DHCP server, but I've reserved 192.168.0.203, so effectively it's static.

I've tried for a couple of days to get the DaynaPORT networking running with various configurations. The nearest I've gotten is O/T 1.3 with the default configuration of easyinstall.sh.

The Mac TCP/IP control panel is configured "manually" with:

IP: 10.10.20.2
Subnet: 255.255.255.0
Router: 10.10.20.1
Name servers: 8.8.8.8
1.1.1.1
Search domains: none/empty

With this I can ping the gateway at 10.10.20.1 using AG NetTools, but nothing else. I've read numerous threads and the various network configuration output are reproduced, for example:

> sudo iptables -v -L -t nat
Chain PREROUTING (policy ACCEPT 175 packets, 35201 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 124 packets, 32525 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 1125 packets, 70669 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 1125 packets, 70669 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MASQUERADE  all  --  any    wlan0   10.10.20.0/24        anywhere            

> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:3a:dd:78:3c:c5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.203/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
       valid_lft 83235sec preferred_lft 83235sec
    inet6 fe80::da3a:ddff:fe78:3cc5/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
4: piscsi_bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 56:96:f5:23:9d:04 brd ff:ff:ff:ff:ff:ff
    inet 10.10.20.1/24 brd 10.10.20.255 scope global piscsi_bridge
       valid_lft forever preferred_lft forever
    inet6 fe80::b4f0:f7ff:fe1c:99b6/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
6: piscsi0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master piscsi_bridge state UNKNOWN group default qlen 1000
    link/ether 56:96:f5:23:9d:04 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5496:f5ff:fe23:9d04/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

> brctl show
bridge name	bridge id		STP enabled	interfaces
piscsi_bridge		8000.5696f5239d04	no		piscsi0

My guess is this is a routing problem somewhere, any ideas would be gratefully received.