Skip to content

DaynaPort networking no longer working after latest build of 'develop' #1306

@benjamink

Description

@benjamink

Info

  • Which version of Pi are you using:

Raspberry Pi 4

  • Which github revision of software:

develop branch (built 2023-11-04 @ ~12pm UTC)

  • Which board version:

Current

  • Which computer is the PiSCSI connected to:

Macintosh Performa 475 w/ System 7.5.3

Describe the issue

Raspberry Pi connected via wired ethernet (eth0) but wireless interface (wlan0) is also active & gets an IP from DHCP.

PiSCSI is configured to bridge eth0:

root@piscsi-perf475:~# ip addr
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
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master piscsi_bridge state UP group default qlen 1000
    link/ether dc:a6:32:1f:8c:8b brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether dc:a6:32:1f:8c:8c brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.11/16 brd 192.168.255.255 scope global dynamic noprefixroute wlan0
       valid_lft 6257sec preferred_lft 5357sec
    inet6 fe80::3bfe:ab:8ed7:3cbc/64 scope link
       valid_lft forever preferred_lft forever
4: piscsi_bridge: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 7e:47:31:f0:27:b0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.14/16 brd 192.168.255.255 scope global dynamic piscsi_bridge
       valid_lft 6233sec preferred_lft 6233sec
    inet6 fe80::dea6:32ff:fe1f:8c8b/64 scope link
       valid_lft forever preferred_lft forever
6: piscsi0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master piscsi_bridge state DOWN group default qlen 1000
    link/ether 7e:47:31:f0:27:b0 brd ff:ff:ff:ff:ff:ff

Netatalk appears to be configured properly.

/etc/netatalk/atalkd.conf (tried in both configurations):

piscsi_bridge -phase 2 -net 0-65534 -addr 65280.76
eth0 -phase 2 -net 0-65534 -addr 65280.76
root@piscsi-perf475:~# systemctl status atalkd
● atalkd.service - Netatalk AppleTalk daemon
     Loaded: loaded (/lib/systemd/system/atalkd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-11-04 11:57:17 GMT; 2h 1min ago
      Tasks: 1 (limit: 472)
        CPU: 105ms
     CGroup: /system.slice/atalkd.service
             └─1728 /usr/local/sbin/atalkd

Nov 04 11:56:45 piscsi-perf475 systemd[1]: Starting Netatalk AppleTalk daemon...
Nov 04 11:56:45 piscsi-perf475 atalkd[1728]: Set syslog logging to level: LOG_DEBUG
Nov 04 11:56:45 piscsi-perf475 atalkd[1728]: restart (2.230302)
Nov 04 11:56:46 piscsi-perf475 atalkd[1728]: zip_getnetinfo for piscsi_bridge
Nov 04 11:56:56 piscsi-perf475 atalkd[1728]: zip_getnetinfo for piscsi_bridge
Nov 04 11:57:06 piscsi-perf475 atalkd[1728]: zip_getnetinfo for piscsi_bridge
Nov 04 11:57:16 piscsi-perf475 atalkd[1728]: config for no router
Nov 04 11:57:17 piscsi-perf475 atalkd[1728]: ready 0/0/0
Nov 04 11:57:17 piscsi-perf475 systemd[1]: Started Netatalk AppleTalk daemon.

/etc/netatalk/afpd.conf:

- -transall -uamlist uams_guest.so,uams_clrtxt.so,uams_dhx2.so -icon -setuplog "default log_maxdebug /var/log/afpd.log"
root@piscsi-perf475:~# systemctl status afpd
● afpd.service - Netatalk AFP fileserver for Macintosh clients
     Loaded: loaded (/lib/systemd/system/afpd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-11-04 11:57:22 GMT; 2h 2min ago
      Tasks: 2 (limit: 472)
        CPU: 450ms
     CGroup: /system.slice/afpd.service
             └─1761 /usr/local/sbin/afpd -c 20

Nov 04 11:57:22 piscsi-perf475 systemd[1]: Starting Netatalk AFP fileserver for Macintosh clients...
Nov 04 11:57:22 piscsi-perf475 systemd[1]: Started Netatalk AFP fileserver for Macintosh clients.
Nov 04 11:57:22 piscsi-perf475 afpd[1761]: Set syslog logging to level: LOG_INFO

Dyanaport networking was working on the Performa prior to rebuilding PiSCSI today but it hasn't been used for a couple months. Only new change is the domain used for my LAN but this is provided by DHCP as expected.

I'll provide additional details including screenshots later when I'm able to get back on the Macintosh.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions