[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Netatalk inconsistencies wired vs. wireless.
On Jun 8, 1:23 am, A2Aviator <a2avia...@gmail.com> wrote:
> The bridge is a wireless router, WRT54GS, with DD-WRT.
>
> The router is connected to the cable modem, and then an 8 port gigabit
> switch is connected to the router.
>
> Everything is plugged into the gigabit switch.
>
> Server, Macs, IIgs. etc.
>
> The gigabit switch has been substituted with a 10 Base-T hub. Same
> effect.
Right. That would tend to rule out any differences in broadcast
traffic from the netatalk box...
> The IIgs and the server have had their own router. Although another DD-
> WRT, they have had their own. I have never had problems with Apple's
> AAUI transceivers and the "unable to link" issue with any hardware I
> have here, I have also used an EtherWave AAUI transceiver.
>
> Boiling down to, the IIgs sees and interacts just fine with a Mac/
> ShareWay setup, and just fine with the netatalk server if the netatalk
> server is connected via wireless to the LAN.
>
> The wireless is either adding something, or subtracting something.
Yeah :-S
When I last had a similar setup (but with a IIe instead of a IIgs) I
had many issues with 'hardware' bridges and a lot of success using a
Mac as a bridge. Even in that case though, I had to do something that
would correctly initialise the localtalk environment (like connect to
a share on the Mac) before it would work seamlessly to the Linux box.
Never having being able to get it running reliably without having a
localtalk equipped machine on the network is the reason I no longer
bother, so I'm keen to see it work.
It just occured to me you're probably using an Apple EtherTalk
Workstation card for this, too
Matt