How to delete second network interface after removing network device?

[shirsch]

Yes, they work as they should and stay connected as long as the system is up. With localtalk or ethernet there is distinct network activity that appears early in the boot process (flickering arrows in the upper left). I assume that's where the Appletalk client does network discovery. With the Daynaport driver, there is zero activity until I log on in the chooser. That's why I'm thinking this is a dependency issue. I know a lot of folks are using the ZuluSCSI and BlueSCSI Dayna emulation, but I've seen no indication that anyone else is seeing the problem.

One other bit of oddness: Neither the Appletalk control panel nor chooser show any Appletalk zones, yet Tattletech network analysis does show them correctly.

 

[LaPorta]

How many zones do you have?

Also, I would think that part of the issue here is not the Dayna emulation, but maybe the actual WiFi itself isn’t connecting until after startup. That wouldn’t know how to rectify.

 

[shirsch]

There are two zones. From what I see in the log file, the wifi connection is made before any emulation starts. And, even if it was slow to init after power on, a reboot would see a connection that's already up (simply restarting the Mac does not reset the SCSI emulation). What I'd really like to know is if it's working correctly for others. If it's a global problem with the ZuluSCSI / BlueSCSI Daynaport code then I'll stop worrying .