Re: Netatalk inconsistencies wired vs. wireless.

[A2Aviator <a2aviator@gmail.com>]

In the process of trying a wireless NIC on the server, and not
succeeding due to either Ubuntu actually not supporting a piece of
hardware, or it did but didn't call it an ethernet card, and netatalk
hated 'ra0' as an interface descriptor, or just plain out not working
as the machine would not POST with it in there. It's a dual Xeon PCI-X
Intel Server Board. It's also very picky.

So, I put that wireless game adapter on the IIgs instead, on the off
chance that a wireless bridge somewhere would do the same thing as the
test server via wireless is having happen.

It did. The IIgs can see both the real and test server.

user@palomino:/etc/netatalk$ nbplkup
  palomino:AFPServer   1.78:128
  palomino:netatalk   1.78:4
  palomino:Workstation   1.78:4
   ubuntu:AFPServer   65280.236:128
   ubuntu:netatalk   65280.236:4
   ubuntu:Workstation   65280.236:4
 10-00-E0-30-03-3A:DB.Tool   65514.32:32
  tdiaz:Apple IIgs   65514.32:191

http://17500mph.com/IMG_3266.JPG

However, the negative impact is .. this thing is slower than ever. A
Disk ][ Controller is faster.

If the test server is on via wireless and the IIgs is wired, it's
twice as fast as LocalTalk/Serial port.
The IIgs still sees the Macintosh, and even a Win2K with Services for
Macintosh.