• Hello, Guest! Welcome back, and be sure to check out this post for more info about the recent service interruption and migration.

RaSCSI Development Thread

slipperygrey

Well-known member
Does WLAN support mean you can use Pi’s wifi? Have you tried transferring AppleShare over AppleTalk? I had some issues with Scuznet AppleShare over AppleTalk over wifi but never went back to try to sort it out.

Yes, and yes. AppleShare over AppleTalk (DDP) works perfectly over as long as your kernel has the appletalk module loaded. See the wiki page that I linked in my previous post above.

The one thing that doesn't work great, is using Netatalk in parallel with RaSCSI on the same Pi Zero W over an emulated DaynaPort network adapter on a slow Mac. If you try to copy files on the AppleShare over the emulated network interface, it will stall indefinitely on my SE. I think it is a Pi Zero performance bottleneck. A faster Pi handles this perfectly fine.
 

superjer2000

Well-known member
Sorry, I should have been more clear. I had success downloading from an AppleShare server but uploading files (ie copying to a server) on Wifi had issues that I believe were timing related.
 

slipperygrey

Well-known member
Sorry, I should have been more clear. I had success downloading from an AppleShare server but uploading files (ie copying to a server) on Wifi had issues that I believe were timing related.
Sorry, just to be absolutely clear: Is it the AppleShare server itself that is connected over wifi, the Mac that's connecting to the AppleShare server, or both?
And BTW, this is getting off topic as far as RaSCSI is concerned so I'd suggest you start a new thread!
 

superjer2000

Well-known member
Sorry, just to be absolutely clear: Is it the AppleShare server itself that is connected over wifi, the Mac that's connecting to the AppleShare server, or both?
And BTW, this is getting off topic as far as RaSCSI is concerned so I'd suggest you start a new thread!
No, no reason to start a new thread. I’m just trying to first confirm what WLAN support for Daynaport means. I am assuming you can plug RaSCSI into a computer and access your network over wifi (ie no Ethernet cable). For better clarity, plug RaSCSI into a PowerBook at your kitchen table with nothing going into the pi other than power, can the PowerBook connect to the the internet and AppleShare servers on the rest of the network using the Daynaport emulation?

From the wiki you linked it seems like maybe this isn’t what was meant.

EDIT: found the part of the wiki that indicates it will do the above. The question then was whether there are any issues uploading to an AppleShare server on a network from the PowerBook connected over wifi in the above example. AppleTalk over wifi can be finicky.
 
Last edited:

slipperygrey

Well-known member
No, no reason to start a new thread. I’m just trying to first confirm what WLAN support for Daynaport means. I am assuming you can plug RaSCSI into a computer and access your network over wifi (ie no Ethernet cable). For better clarity, plug RaSCSI into a PowerBook at your kitchen table with nothing going into the pi other than power, can the PowerBook connect to the the internet and AppleShare servers on the rest of the network using the Daynaport emulation?

From the wiki you linked it seems like maybe this isn’t what was meant.

EDIT: found the part of the wiki that indicates it will do the above. The question then was whether there are any issues uploading to an AppleShare server on a network from the PowerBook connected over wifi in the above example. AppleTalk over wifi can be finicky.
There is one major limitation with how wifi over the RaSCSI Daynaport emulation works at the moment, in that it relies on NAT to translate network traffic between the emulated interface and the rest of the internet. Due to (deliberate for security reasons) limitations in the Linux networking stack, you're bound to a private network between the host Pi and the Mac, and will only be able to access AppleTalk resources running on the Pi itself. You will *not* have access to AppleTalk resources elsewhere on your local network. This is documented in the RaSCSI wiki page on this topic.

Now, there may be ways around this as there's nothing in RaSCSI code itself that's holding back wifi networking. Perhaps a Linux networking guru can help us find a way. :)
 

slipperygrey

Well-known member
Small addendum to the above: I was talking about AFP over DDP (AppleTalk) in particular. AFP over TCP most likely works fine over NAT, but I haven't tested it yet.
 

jcs

New member
Is it just mine or does the RaSCSI run exceptionally hot? Even when it's not passing any traffic, the row of chips on the top of the board is too hot to touch. The Raspberry Pi it's attached to runs fairly cool.
 

robin-fo

Well-known member
Is it just mine or does the RaSCSI run exceptionally hot? Even when it's not passing any traffic, the row of chips on the top of the board is too hot to touch. The Raspberry Pi it's attached to runs fairly cool.
It's the same on my RaSCSI...
 

landoGriffin

Well-known member
I've observed the same thing. Just sitting idle, the chips do get pretty warm. However, I've used them for long periods of time without having any issues. Have you guys measured the temperature of the chips?

The operating temperature in the data sheet is 0 to 70 degrees C. As long as they're staying under 70 C, they should be fine.

1637200195345.png
 

Tom2112

Well-known member
I think I'll put a row of those little Raspberry Pi heatsinks on the RaSCSI chips. That'll probably help with longevity.
 

Attachments

  • 1638365866786.png
    1638365866786.png
    331.1 KB · Views: 1

rollmastr

Active member
I am currently having trouble with AppleShare over AppleTalk (DDP) after going back and forth through the Wiki and reinstalling RaSCSI. Perhaps you can help me out.

I am using the December release of RaSCSI with a Raspberry Pi Zero 2 W.
The Machine is a Macintosh SE FDHD running System 7.1, NSI 1.5.1, MacTCP 2.1 and DaynaPort drivers 7.3.4.

The Pi is connected to my WiFi and the WiFi bridge was enabled via easyinstall.sh.
The Mac's IP address is set to 10.10.20.2 and it connects to my Router 10.10.20.1.
The network connection does not seem to be an issue since I can browse the web using MacWeb 2.0 with that setup.

The issue is that I cannot see my RaSCSI-Pi AFP server in chooser. I do see it on my modern mac though which should mean that zeroconfig is working.

What am I missing?
 

slipperygrey

Well-known member
@rollmastr You may need to force atalkd to use the rascsi_bridge interface. Try editing /etc/netatalk/atalkd.conf and put "rascsi_bridge" without quotation marks at the bottom of the file (or edit the existing line, if there is one) then restart the daemons. If it still doesn't work, try running the "nbplkup" command on the terminal and see if the AFPServer DDP service is being recognized.

If you need more help, I suggest you start a new thread, or DM me in private. This thread is strictly speaking about RaSCSI proper, rather than Netatalk!
 

rollmastr

Active member
Thanks. I did add rascsi_bridge to atalkd.conf and restart the Pi without success.
nbplkup returns "nbp_lookup: Cannot assign requested address" so I guess that's my problem.

/edit: I added "PAPD_RUN=yes" to /etc/default/netatalk and restarted netatalk.

Now nbplkup returns:
pi@raspberrypi:~ $ nbplkup


raspberrypi:netatalk 65280.139:4


raspberrypi:Workstation 65280.139:4

However the old Mac still doesn't display anything in chooser.
 
Last edited:

slipperygrey

Well-known member
@rollmastr We're planning a new RaSCSI software release due early next week, which will include a fix for the DaynaPort emulation when using wifi, as well as a much-improved version of Netatalk included. Upgrading the software might not fix your issue outright, but it'll be a better starting point for troubleshooting.
 

rollmastr

Active member
Oooh, this sounds great! I will for sure have a look and install it as soon as it's out. RaSCSI is definitely the most fun project I've played with for a while. Loving it a lot.
 
Top